JP2015104070A - Network management system, management apparatus, controller, management method, control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network management system in which a path on a virtual network can be confirmed.SOLUTION: A network management system has: a plurality of controllers each of which controls a part of a plurality of switches for transferring a packet on a virtual network; and a management device which manages the plurality of controllers. The management device has: a request acquisition section which acquires a request of confirmation for a path on the virtual network; and a notification destination determining section which determines a controller as a notification destination of the request which controls a switch of a transmission source of a path among the plurality of switches.

Description

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

In a network configured with an L2 switch, packet transfer is performed using a MAC address. In a network configured with a router, packet transfer is performed using an IP address, and different transfer methods are mixed in the same device. There was nothing to do.
Further, for example, in a network (IP network) constituted by routers, since it is transferred only by a destination IP address, its upper protocol (ICMP (Internet Control Message Protocol, Non-Patent Document 1), TCP (Transmission Control Protocol) Even if UDP (User Datagram Protocol) and the like are different, packet transfer processing is performed for all of them using the same rule.

  That is, in a conventional network (for example, an IP network), if arrival of a packet can be confirmed by an ICMP packet, it is guaranteed that a TCP or UDP packet addressed to the same IP address will also arrive. For this reason, it is possible to confirm the communication of an arbitrary IP packet by confirming the arrival of any packet. One specific method is ping using an ICMP packet.

Currently, there is OpenFlow (Non-Patent Document 2) as one of the methods for realizing SDN (Software Defined Network), and the specification is being developed by ONF (Open Network Foundation). A network using OpenFlow is a network configured by an OpenFlow controller (hereinafter referred to as OFC) and an OpenFlow switch (hereinafter referred to as OFS), in which packet transfer rules can be freely set from OFC to OFS. This is a technology that can construct a virtual network based on transfer rules.
That is, in a network composed of OFS, a plurality of virtual networks having various packet transfer methods can be freely configured.

RFC792, INTERNET CONTROL MESSAGE PROTOCOL, [online], [2013/02/12 search], Internet, <URL: http: //www.rfcsearch.org/rfcview? Lookup_type = RFC & lookup_num = 792> OpenFlow Switch Specification, [online], [2013/02/13 search], Internet, <URL: https: //www.opennetworking.org/images/stories/downloads/specification/ openflow-spec-v1.3.1.pdf>

  However, in a network in which a plurality of virtual networks can be configured, such as a network composed of OFS, there is a problem that ping cannot be used to confirm a route such as communication confirmation on the virtual network.

  The present invention has been made in view of such circumstances, and provides a network management system, a management device, a controller, a management method, a control method, and a program capable of confirming a route on a virtual network.

(1) The present invention has been made to solve the above-described problems, and one aspect of the present invention provides a plurality of switches each controlling a part of a plurality of switches that transfer packets on a virtual network. A network management system including a controller and a management device that manages the plurality of controllers, wherein the management device acquires a request for confirmation regarding one route in the virtual network, and the plurality of switches A notification destination determination unit that determines the controller that controls the transmission source switch of the one path as the notification destination of the request.

(2) According to another aspect of the present invention, in the network management system according to (1), the confirmation regarding the one route is a communication confirmation of the one route, and the notification destination determining unit The controller that controls the destination switch of the one path among the plurality of switches is determined as an arrival confirmation destination of the test packet by the request.

(3) According to another aspect of the present invention, there is provided the network management system according to (1), wherein the controller is notified when a request for confirmation regarding the one route is notified from the management device. A test packet designating the maximum number of hops is generated, and the generated test packet is transmitted to the head switch of the one route, and the number of hops of the test packet reaches the maximum from any of the plurality of switches. When notified of this, the management device is notified.

(4) According to another aspect of the present invention, there is provided the network management system according to (3), in which the controller transmits the test packet from a switch at an end point of the one path among the plurality of switches. When notified that the number of hops has reached the maximum, the management device is notified, and among the plurality of switches, the number of hops of the test packet has reached the maximum from switches other than the end point of the one route Is notified, a test packet designating a predetermined maximum number of hops is generated, and the generated test packet is transmitted to the switch that has notified that the maximum number of hops has been reached.

(5) Further, another aspect of the present invention is the network management system according to (4), wherein the confirmation regarding the one route is route confirmation of the one route, and the controller When the switch other than the end point of the one path is notified that the number of hops of the test packet has reached the maximum, the test packet specifies a predetermined maximum number of hops, and the number of hops is Generates a test packet having payload data as data in which information indicating a switch that has notified that the maximum number of hops of the test packet has been reached is added to the payload data of the test packet that has reached the maximum, and the generated test packet To the switch that has notified that the number of hops of the test packet has reached the maximum, and of the end points of the one route among the plurality of switches When the number of hops of the test packet from the switch is notified that reached a maximum, the payload data of the test packet hop count has reached the maximum, and notifies the management apparatus.

(6) Further, another aspect of the present invention is the network management system according to (1), in which the controller includes a switch that can be controlled by the own device and another controller that can control the switch. Transfer destination determination that refers to the adjacent information storage unit that stores the association and the other controller capable of switch control of the transmission source of the one path as the transfer destination of the process according to the request with reference to the adjacent information storage unit It comprises the part.

(7) According to another aspect of the present invention, a plurality of controllers each controlling a part of a plurality of switches that transfer packets on a virtual network, and a management device that manages the plurality of controllers, A management device in a network management system comprising: a request acquisition unit configured to acquire a confirmation request regarding one route in the virtual network; and a source switch of the one route among the plurality of switches And a notification destination determination unit that determines the controller as a notification destination of the request.

(8) Another aspect of the present invention is a controller that controls a part of a plurality of switches that transfer packets on a virtual network, and is required to confirm a route in the virtual network. A test packet designating a predetermined maximum number of hops, and transmitting the generated test packet to a head switch of the one route, wherein the number of hops of the test packet is maximum from any of the plurality of switches. The controller is characterized by notifying other devices when notified of reaching the above.

(9) Another aspect of the present invention is a controller that controls a part of a plurality of switches that transfer packets on a virtual network, and is required to confirm a route in the virtual network. A test processing unit that performs processing according to the request, a switch that can be controlled by the device, an adjacent information storage unit that stores associations with other controllers that can control the switch, and the adjacent information storage unit. The controller includes a transfer destination determination unit that determines another controller capable of switch control of the transmission source of the one path as a transfer destination of the process according to the request.

(10) According to another aspect of the present invention, a plurality of controllers each controlling a part of a plurality of switches that transfer packets on a virtual network, and a management device that manages the plurality of controllers, A management method in a network management system comprising: a first process in which the management device acquires a request for confirmation regarding one path in the virtual network; and the management device includes the switch among the plurality of switches. And a second step of determining the controller that controls the switch of the transmission source of one route as the notification destination of the request.

(11) According to another aspect of the present invention, there is provided a control method in a plurality of controllers, each of which controls a part of a plurality of switches that transfer packets on a virtual network. When the first controller is requested to confirm the one route in the virtual network, the first controller generates a test packet designating a predetermined maximum number of hops, and the generated test packet is sent to the head of the one route. When the second controller among the plurality of controllers is notified that the number of hops of the test packet has reached the maximum, from among the plurality of controllers, And a second process of notifying the apparatus.

(12) According to another aspect of the present invention, there is provided a control method in a controller that controls a part of a plurality of switches that transfer packets on a virtual network. When confirmation about a route is requested, the controller stores a correspondence between a first process for processing according to the request and a switch that can be controlled by the controller and another controller that can control the switch. A second step of referring to the adjacent information storage unit and determining another controller capable of switch control of the transmission source of the one route as a transfer destination of the processing according to the request. is there.

(13) According to another aspect of the present invention, a plurality of controllers each controlling a part of a plurality of switches that transfer a packet on a virtual network, and the plurality of controllers are managed. A program for causing a management apparatus to function as a management apparatus in a network management system comprising a management apparatus, wherein the management apparatus includes a request acquisition unit that acquires a request for confirmation regarding one route in the virtual network, and a plurality of switches Among them, the apparatus includes a notification destination determination unit that determines the controller that controls the switch of the transmission source of the one route as the notification destination of the request.

(14) Moreover, the other aspect of this invention is a program for functioning a computer as a controller as described in (8) or (9).

  According to the present invention, confirmation regarding a route on a virtual network can be performed.

1 is a schematic block diagram showing a configuration of a network management system 10 according to an embodiment of the present invention. It is a schematic block diagram which shows the structure of the OFC management apparatus 102 by the embodiment. It is a schematic block diagram which shows the structure of OFC104a by the embodiment. It is a schematic block diagram which shows the structural example of the test process part 401 by the embodiment. It is a schematic block diagram which shows the structure of the transfer process part 405 by the embodiment. It is a table which shows the example of the content of the request | requirement of communication confirmation by the embodiment. It is a table which shows the example of the content of the request | requirement of the path | route confirmation by the same embodiment. It is a table which shows the example of the memory content of the test management information storage part 205 by the embodiment. It is a table which shows the example of a memory content of OFC management information storage part 206 by the embodiment. It is a table which shows the example of the memory content of the test result information storage part 207 by the embodiment. It is a table which shows the example of the memory content of the adjacent information storage part 406 by the embodiment. It is a table which shows the example of the memory content of the test management information storage part 403 by the embodiment. It is a table which shows the example of the memory content of the test result information storage part 404 by the embodiment. It is a table which shows the default value of the test packet for the communication confirmation by the embodiment. It is a table which shows the default value of the test packet for the route confirmation by the same embodiment. It is a sequence diagram explaining the process of communication confirmation by the embodiment. It is a sequence diagram explaining the process of route confirmation by the embodiment. It is another sequence diagram explaining the process of route confirmation by the same embodiment. It is a sequence diagram explaining the process of transfer by the embodiment.

  Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a schematic block diagram showing a configuration of a network management system 10 according to an embodiment of the present invention. The network management system 10 includes a topology management device 101, an OFC (OpenFlow Controller) management device 102 (management device), a management network 103, and OFCs 104a, 104b, and 104c (controller).

  The network management system 10 manages a network composed of OFSs 100a, 100b, 100c, 100d, 100e, and 100f. OFSs 100a, 100b, 100c, 100d, 100e, and 100f are network switches that comply with the OpenFlow standard. A network N1 is connected to the OFS 100b, a network N2 is connected to the OFS 100e, and a network N3 is connected to the OFS 100f. The OFSs 100a, 100b, 100c, 100d, 100e, and 100f constitute a plurality of virtual networks. When packets are transmitted between the networks N1, N2, and N3, the packets are transmitted on any one of the virtual networks. Is done. For this reason, for example, even if the packet is transmitted from the network N1 to the network N2, the transmission path is different if the virtual network used for transmission is different.

  The network management system 10 can perform communication check and route check for an arbitrary route in each of these virtual networks. Moreover, the network management system 10 can always check the soundness of the network by periodically checking the communication. At that time, by transferring the processing among the OFCs 104a, 104b, and 104c, it is possible to avoid the load from being concentrated on a specific OFC.

  Each device included in the network management system 10 will be described. The topology management apparatus 101 manages the physical connection relationships of the OFSs 100a to 100f and the transfer rules and connection relationships of the virtual networks constructed by the OFSs 100a to 100f. The virtual network transfer rule is a condition for a packet transmitted in the virtual network. Examples of the transfer rule include conditions based on a source IP address, a source port number, a destination IP address, a destination port number, a protocol used, and the like. As the transfer rule, other conditions that can be set in OpenFlow are used. May be. Further, the topology management apparatus 101 notifies the OFC management apparatus 102 of a request for confirmation (for example, communication confirmation or path confirmation) regarding a route in the virtual network in accordance with an instruction input from the operator.

  The OFC management apparatus 102 manages the OFCs 104a, 104b, and 104c. When the OFC management apparatus 102 receives a confirmation request regarding the route in the virtual network from the topology management apparatus 101, the OFC management apparatus 102 notifies the OFC that controls the OFS that is the transmission source of the route. If the request is a communication confirmation request, the OFC management apparatus 102 requests the OFC that controls the OFS of the route destination to wait for reception of a test packet for communication confirmation.

  The management network 103 connects the topology management apparatus 101, the OFC management apparatus 102, and the OFCs 104a, 104b, and 104c so that they can communicate with each other. Note that the network connecting the topology management apparatus 101 and the OFC management apparatus 102 may be different from the network connecting the OFC management apparatus 102 and the OFCs 104a, 104b, and 104c.

  The OFCs 104a, 104b, and 104c control some of the OFSs 100a to 100f, respectively. For example, the OFC 104a controls the OFSs 100a, 100b, and 100e that are connected by solid lines in FIG. When each of the OFCs 104a, 104b, and 104c receives a request for confirmation (for example, communication confirmation or path confirmation) regarding a route in the virtual network from the OFC management apparatus 102, the OFC 104a, 104b, or 104c generates a test packet for performing the confirmation It transmits to OFS of the transmission source of the route.

  Further, when each of the OFCs 104a, 104b, and 104c is requested by the OFC management apparatus 102 to wait for reception of a test packet for communication confirmation, each of the OFCs 104a, 104b, and 104c receives the test packet from the OFS that is the destination of the communication confirmation path. The OFC management apparatus 102 is notified that the communication confirmation has been successful. If the OFCs 104a, 104b, and 104c time out without receiving the test packet, the OFCs 104a, 104b, and 104c notify the OFC management apparatus 102 that the communication confirmation has timed out.

  The communication confirmation request may include a cycle. If the cycle is included, each of the OFCs 104a, 104b, and 104c periodically performs communication confirmation. Each of the OFCs 104a, 104b, and 104c transfers the communication check periodically performed to another OFC when the load is excessive or when the own apparatus stops.

  FIG. 2 is a schematic block diagram showing the configuration of the OFC management apparatus 102. The OFC management apparatus 102 includes a request reception unit 201, a notification destination determination unit 202, an OFC linkage unit 203, a result notification unit 204, a test management information storage unit 205, an OFC management information storage unit 206, a test result information storage unit 207, and a transfer result. A receiving unit 208 is included.

  The request reception unit 201 receives a request for confirmation regarding a route in the virtual network (for example, communication confirmation or route confirmation) from the topology management apparatus 101. The notification destination determination unit 202 refers to the association between the OFC stored in the OFC management information storage unit 206 and the OFS, and controls the OFC that controls the OFS of the transmission source of the route to be confirmed as the OFC that notifies the request. To do.

  When the request is a communication confirmation request, the notification destination determination unit 202 refers to the correspondence between the OFC stored in the OFC management information storage unit 206 and the OFS, and the destination of the path for which the communication is confirmed. The OFC that controls the OFS is an OFC that notifies reception waiting for a test packet for communication confirmation. Further, when the request is a periodic communication confirmation request, the notification destination determination unit 202 registers at least an OFC that notifies the request in the test management information storage unit 205.

  The OFC linkage unit 203 notifies the request to the OFC determined by the notification destination determination unit 202. Further, the OFC cooperation unit 203 notifies the OFC determined by the notification destination determination unit 202 of the reception waiting for the test packet. Further, the OFC linkage unit 203 receives the result of confirmation by the request from the OFC. When the OFC cooperation unit 203 receives the confirmation result, the result notification unit 204 notifies the topology management apparatus 101 of the confirmation result. In addition, the result notification unit 204 stores the result of the confirmation in the test result information storage unit 207.

  The test management information storage unit 205 stores the OFC for which periodic communication confirmation is performed. The OFC management information storage unit 206 stores an association between each OFS and the OFC that controls the OFS. The test result information storage unit 207 stores a result of confirmation regarding a route in the virtual network. When the OFC of the transfer destination of periodic communication confirmation is notified from any of the OFCs, the transfer result receiving unit 208 changes the storage contents of the test management information storage unit 205 according to the notification.

  FIG. 3 is a schematic block diagram showing the configuration of the OFC 104a. Note that the configuration of the OFC 104b and OFC 104c is the same as the configuration of the OFC 104a, and thus the description thereof is omitted. The OFC 104a includes a test processing unit 401, a switch control unit 402, a test management information storage unit 403, a test result information storage unit 404, a transfer processing unit 405, and an adjacent information storage unit 406.

  The test processing unit 401 performs processing related to confirmation regarding a route in the virtual network, stores the result in the test result information storage unit 404, and notifies the OFC management apparatus 102 of the result. The test processing unit 401 controls the OFSs 100a, 100b, and 100e via the switch control unit 402 when performing the processing. In addition, when the confirmation regarding the route in the virtual network is periodic communication confirmation, the test processing unit 401 stores information regarding the communication confirmation in the test management information storage unit 403. Details of the test processing unit 401 will be described later.

  Based on an instruction from the test processing unit 401, the switch control unit 402 generates an OpenFlow command for controlling the OFS, and transmits the command to the OFS. For example, when the test processing unit 401 is instructed to transmit a test packet, the test packet is transmitted to the OFS by PacketOut. Further, when the switch control unit 402 receives notification of an abnormal packet such as a packet having the maximum number of hops from the OFS by PacketIn, the switch control unit 402 notifies the test processing unit 401 of the notification. The test management information storage unit 403 stores information regarding periodic communication confirmation performed by the own device. The test result information storage unit 404 stores the test results (communication confirmation result and route confirmation result) determined by the own apparatus.

  The transfer processing unit 405 refers to the test management information storage unit 403 to check the periodic communication performed by the OFC when the OFC stops or when the processing load of the OFC is excessive. Process to transfer to other OFC. When transferring the communication confirmation, the transfer processing unit 405 refers to the adjacent information storage unit 406 and selects a transfer destination OFC candidate. Also, the transfer processing unit 405 performs an acceptance process when transfer of communication confirmation is requested from another OFC. The transfer processing unit 405 updates the information related to the communication confirmation stored in the test management information storage unit 403 according to the result when the communication confirmation is transferred and when the communication confirmation is accepted. Then, the processing result is notified to the OFC management apparatus 102. Details of the transfer processing unit 405 will be described later.

  The adjacent information storage unit 406 stores an OFS that can control the OFC and an OFC that can control the OFS.

  FIG. 4 is a schematic block diagram illustrating a configuration example of the test processing unit 401. The test processing unit 401 illustrated in FIG. 4 performs communication confirmation and route confirmation. The test processing unit 401 includes a confirmation request reception unit 411, a test call generation unit 412, a test result determination unit 413, a test result transmission unit 414, a reception standby request reception unit 415, a test call reception notification transmission unit 416, and a test call reception notification reception. A part 417 is included. The confirmation request receiving unit 411 receives a communication confirmation request and a route confirmation request from the OFC management apparatus 102. The confirmation request receiving unit 411 instructs the test call generating unit 412 to generate a test packet in response to these requests. When the confirmation request receiving unit 411 is instructed to perform periodic communication confirmation in the communication confirmation request, the confirmation request reception unit 411 stores the communication confirmation request in the test management information storage unit 403.

  The test call generation unit 412 generates a test packet for communication confirmation and a test packet for route confirmation, and transmits the generated test packet to the OFS. Instruct. Note that the number of hops is set so that the test packet for communication confirmation is transferred to the OFC by PacketIn for the reason of TTL Invalid at the end point (destination OFS) of the path for which communication is confirmed. The number of hops is set so that the test packet for route confirmation is transferred from the OFS adjacent to the OFS transmitted by the OFC to the OFC using PacketIn for the reason of TTL Invalid. The OFS that has received the test packet for route confirmation notifies the OFC of the test packet by PacketIn, and the OFC that has received the notification generates a test packet for confirming the subsequent route.

  The test call generation unit 412 generates a test packet for confirming communication when the confirmation request receiving unit 411 is instructed to perform communication confirmation and when the communication request is stored in the test management information storage unit 403. This is when the period arrives. Note that the test packet for communication confirmation is a packet in accordance with the transfer rule included in the communication confirmation request, and the number of hops included in the communication confirmation request is expressed as TTL (Time in the IP (Internet Protocol) header). to live) field. When the packet is an IPv6 IP packet, it is set in the hop limit field instead of the TTL field.

  The test call generating unit 412 generates a test packet for route confirmation when the confirmation request receiving unit 411 is instructed to perform route confirmation and when the test result determining unit 413 confirms the subsequent route. This is when an instruction to generate a test packet to perform is given. Note that the test packet for route confirmation is a packet in accordance with the transfer rule included in the route confirmation request, is a packet in which “2” is set in the TTL field in the IP header, and the OFC Information (for example, DataPathID) for identifying an OFS that transmits a test packet by PacketOut is a packet in which the payload is stored.

  When the test packet for route confirmation is a test packet for confirming the subsequent route, the information obtained by adding information identifying the OFS to be transmitted to the payload of the previous test packet is added to the test packet. The payload of the packet. Since the information for identifying the OFS added so far is stored in the payload of the test packet so far, the payload of the test packet follows the path so far as information indicating the path so far. In this order, information for identifying the OFS is stored. Further, when the route end point (destination OFS) is specified in the route confirmation request, information for identifying the OFS is stored in the payload of the test packet for route confirmation. If the packet is an IPv6 IP packet, it is set in the hop limit field instead of the TTL field.

  The test result determination unit 413 performs determination of the result of communication confirmation, determination of the result of path confirmation, and generation of a test packet for confirming a subsequent path. The test result determination unit 413 determines the result of the communication confirmation as follows. When the reception standby request reception unit 415 receives the reception standby request, the test result determination unit 413 waits for reception of a test packet for confirming communication specified by the request until a predetermined timeout time elapses.

  When the test result determination unit 413 is notified from the switch control unit 402 that the corresponding test packet has been received by PacketIn from the OFS specified in the request before the timeout time elapses, the communication check is performed. Is determined to be successful. If the switch control unit 402 does not receive a notification that the corresponding test packet has been received from the OFS specified in the request even after the timeout period has elapsed, the test result determination unit 413 It is determined that the communication confirmation has timed out. The test result determination unit 413 stores the determination result in the test result information storage unit 404.

  The test result determination unit 413 determines the result of the route confirmation and the generation determination of the test packet for confirming the subsequent route as follows. When the test result determination unit 413 is notified from the OFS that the test packet for route confirmation is received from the OFS by PacketIn, whether the OFS that has received the test packet is the end point of the route. Confirm whether or not. Specifically, the test result determination unit 413 stores information for identifying the end point (destination OFS) of the path in the payload of the test packet, and the OFS indicated by the information and the OFS that has received the test packet. If the two match, the OFS is determined to be the end point of the route. When the OFS is the end point of the route, the test result determination unit 413 adds information for identifying the OFS to the information indicating the previous route stored in the payload of the test packet. Is the result of the route confirmation.

  If the OFS is not determined to be the end point of the route, the test result determination unit 413 determines that it is necessary to generate a test packet for confirming the subsequent route. Then, the test result determination unit 413 instructs the test call generation unit 412 to generate a test packet for confirming the subsequent route, and the test call reception notification reception unit until a predetermined timeout period elapses. Wait for reception of a test call reception notification by 417. If a predetermined timeout period has passed without receiving the test call reception notification, it is determined that the OFS that has received the previous test packet is the end point of the route. Then, the test result determination unit 413 adds the information for identifying the OFS to the information indicating the path so far stored in the payload of the test packet as the result of the path check.

The test result transmission unit 414 transmits the communication confirmation result and the route confirmation result determined by the test result determination unit 413 to the OFC management apparatus 102.
The reception standby request reception unit 415 receives the reception standby request transmitted from the OFC management apparatus 102.
When the test result determination unit 413 is notified from the switch control unit 402 that the test packet reception notification transmission unit 416 has received the test packet for route confirmation from the OFS by PacketIn, the test packet for route confirmation Is transmitted to the OFC that is the transmission source of the test packet. In the test packet header, the source MAC stores the MAC address of the source OFC, and the source address stores the IP address of the source OFC. The reception notification transmission unit 416 refers to any of these to determine the OFC of the transmission source.

In addition, information for identifying the OFC of the transmission source may be stored in the payload of the test packet, and the test call reception notification transmission unit 416 may determine the OFC of the transmission source with reference to the information. By doing in this way, even if the value designated by the virtual NW transfer rule is set for both the transmission source MAC and the transmission source address, the OFC of the transmission source can be determined.
The test call reception notification receiving unit 417 receives a test call reception notification from another OFC.

  FIG. 5 is a schematic block diagram showing the configuration of the transfer processing unit 405. The transfer processing unit 405 includes a transfer determination unit 451, a transfer destination determination unit 452, a process reduction unit 453, a transfer result notification unit 454, a processing margin amount notification unit 455, and a process addition unit 456. When the transfer determination unit 451 detects that the processing load of the own device is excessive, the transfer determination unit 451 instructs the transfer destination determination unit 452 to perform transfer. This instruction also specifies the amount of processing to be transferred so that the processing load of the own device is less than or equal to a predetermined amount. Further, when the transfer determination unit 451 detects that the stop process of the own device has been started, the transfer determination unit 451 instructs the transfer destination determination unit 452 to transfer all the communication confirmations.

  When the transfer destination determination unit 452 is instructed to perform transfer from the transfer determination unit 451, the transfer destination determination unit 452 acquires the processing load margin amount of the OFC from the other OFC processing margin amount notification unit 455. The transfer destination determination unit 452 includes information related to periodic communication confirmation stored in the test management information storage unit 403, a surplus amount of processing load of other OFCs, and an OFS stored in the adjacent information storage unit 406. The communication confirmation to be transferred and the OFC of the transfer destination of the communication confirmation are determined from the association with the OFC capable of controlling the OFS and the processing amount to be transferred instructed by the transfer determination unit 451.

  The transfer destination determination unit 452 makes this determination as follows, for example. First, the transfer destination determination unit 452 determines the communication confirmation stored in the test management information storage unit 403 that has an OFC that can control the starting point (OFS of the transmission source) of the route, and the adjacent information storage unit 406. To select. Next, the transfer destination determination unit 452 determines whether or not the margin of the processing load of the OFC that can control the starting point of the selected communication confirmation route is equal to or less than the selected communication confirmation processing amount. When the amount is less than the processing amount, the communication confirmation and the OFC are set as the communication confirmation to be transferred and the OFC of the transfer destination of the communication confirmation. The transfer destination determination unit 452 repeats these until the communication confirmation to be transferred is equal to or greater than the instructed processing amount.

  The processing reduction unit 453 deletes the information related to the communication confirmation to be transferred, which is determined by the transfer destination determination unit 452, from the test management information storage unit 403. This deletion is performed in synchronization with the processing in the processing addition unit 456 of the transfer destination OFC.

  The transfer result notification unit 454 notifies the OFC management apparatus 102 of the transferred communication confirmation and the transfer destination of the communication confirmation. The processing margin amount notification unit 455 notifies the processing load margin amount of the own device in accordance with a request from the other OFC transfer destination determination unit 452. The process addition unit 456 adds information related to the communication confirmation to the test management information storage unit 403 of the own device in synchronization with the deletion of the information related to the communication confirmation in the transfer source OFC. As a result, the OFC confirms communication from the next cycle of the last transmission time included in the information regarding communication confirmation. The last transmission time is the time at which a test packet for confirming communication is last transmitted.

  FIG. 6 is a table showing a content example of a communication confirmation request. The communication confirmation request includes, as items, a request ID, a virtual network (NW) transfer rule, a transmission source switch, a destination switch, the number of hops, and a test cycle. In the example of the communication confirmation request in FIG. 6, “C100” is set as the request ID. In the virtual network transfer rule, “DstIP = 192.168.10.0 / 24 protocol = udp” is set. “DstIP = 192.168.10.0 / 24” is that the destination address of the IP header is an IP address included in the network address represented by “192.168.10.0/24”. “Protocol = udp” indicates that the protocol is UDP (User Datagram Protocol), that is, a UDP packet.

  In addition, “OFS1” is set in the transmission source switch that is the OFS of the starting point of the route for which communication is confirmed. “OFS2” is set in the destination switch which is the OFS at the end point of the path for which communication is confirmed. “OFS1” and “OFS2” are information for identifying the OFS, and the name of the OFS, DataPathID, and the like can be used. Further, “3” is set as the number of hops, and “30 sec” is set as the test cycle.

  FIG. 7 is a table showing an example of the contents of a route confirmation request. The request for route confirmation includes, as items, a request ID, a virtual network (NW) transfer rule, a transmission source switch, and a destination switch. In the example of the route confirmation request in FIG. 7, “R100” is set in the request ID. In the virtual network transfer rule, “SrcIP = 192.168.11.5 protocol = udp” is set. “SrcIP = 192.168.11.5” indicates that the source address of the IP header is “192.168.11.5”. Further, “OFS1” is set for the transmission source switch, and “−” is set for the destination switch. That is, nothing is set in the destination switch.

  FIG. 8 is a table showing an example of stored contents of the test management information storage unit 205. The test management information storage unit 205 of the OFC management apparatus 102 stores a periodic communication confirmation request ID, a transmission source OFC, a transmission source OFS, a destination OFC, and a destination OFS. The source OFC is an OFC that generates a communication confirmation test packet and transmits the test packet to the source OFS. The transmission source OFS is an OFS that is a starting point of a route for which communication is confirmed. The destination OFC is an OFC that waits for reception of a communication confirmation test packet until a timeout occurs. The destination OFS is the OFS at the end point of the path for which communication is confirmed.

  In the example shown in FIG. 8, “C028, C035, C036,..., C118” is stored as the request ID. Further, “OFC2, OFC2, OFC1,... OFC1” is stored as the transmission source OFC corresponding to each of these request IDs. Similarly, “OFS3, OFS3, OFS2,... OFS1” is stored as the source OFS corresponding to each of these request IDs. Similarly, “OFC3, OFC3, OFC3,... OFC2” is stored as the destination OFC corresponding to each of these request IDs. Similarly, “OFS5, OFS5, OFS4,..., OFS3” is stored as the destination OFS corresponding to each of these request IDs.

  FIG. 9 is a table showing an example of stored contents of the OFC management information storage unit 206. The OFC management information storage unit 206 of the OFC management apparatus 102 stores information for identifying each OFS (OFS), information for identifying an OFC that mainly controls the OFS (main OFC), and other OFCs that can control the OFS. The identification information (sub OFC) is stored.

  In the example shown in FIG. 9, “OFS1, OFS2, OFS3, OFS4,...” Is stored as the OFS. “OFC1, OFC2, OFC2, OFC3,...” Is stored as the main OFC corresponding to each of these OFS. Further, “OFC2, OFC1,-, OFC2,...” Is stored as a sub OFC corresponding to each of these OFS. Note that “-” indicates that there is no sub OFC corresponding to “OFS3”. Further, a plurality of sub OFCs may be stored for one OFS.

  FIG. 10 is a table showing an example of stored contents of the test result information storage unit 207. The test result information storage unit 207 of the OFC management apparatus 102 stores a communication confirmation, route confirmation request ID, a determination time when the test result of the request ID is determined, and a test result of the request ID.

  In the example shown in FIG. 10, “C028, C029, C030, R134,...” Is stored as the request ID. As the determination time corresponding to each of these request IDs, "2013/11/1, 10:11:54, 2013/11/1, 10:11:55, 2013/11/1, 10:12:01, 2013 / 11/1, 10:12:04, ... "is stored. Further, “OK, timeout, OK, OFS3: OFS2: OFS5: OFS6,...” Is stored as a test result corresponding to each of these request IDs.

  The test result “OK” indicates that the communication confirmation test packet has been detected by the OFS at the end point by the timeout time. The test result “timeout” indicates that the communication confirmation test packet has not been detected by the OFS at the end point until the timeout time. The test result “OFS3: OFS2: OFS5: OFS6” indicates the order of OFS followed by the route confirmed by the route confirmation.

  FIG. 11 is a table showing an example of stored contents of the adjacent information storage unit 406. The adjacent information storage unit 406 includes an OFS that can control the OFC, whether the OFC is a main OFC or a sub OFC of the OFS (main / sub), and other OFCs that can control the OFS ( Neighboring OFC) is stored. In the example illustrated in FIG. 11, “OFS1, OFS2” is stored as the OFS. “Main, sub” is stored as the main / sub corresponding to each of these OFS. Further, “OFC2, OFC2” is stored as the adjacent OFC corresponding to each of these OFS. A plurality of OFCs may be stored as adjacent OFCs corresponding to the OFS.

  FIG. 12 is a table showing an example of stored contents of the test management information storage unit 403. The test management information storage unit 403 stores a communication confirmation request ID processed by the OFC, a communication confirmation request content of the request ID, and a final transmission time. In the example shown in FIG. 12, “C100, C102,...” Is stored as the request ID. “Virtual NW transfer rule 1, source switch 1, destination switch 1, hop number 1, test period 1” is stored as the request content of the communication confirmation of the request ID “C100”. In addition, “virtual NW transfer rule 2, transmission source switch 2, destination switch 2, hop number 2, test period 2” is stored as a request for confirmation of communication of request ID “C102”. Further, “2013/11/2, 22:13:11, 2013/11/2, 22:13:03” is stored as the final transmission time corresponding to each of these request IDs. The last transmission time is the time when the test packet for confirming communication of the request ID is last transmitted.

  FIG. 13 is a table showing an example of stored contents of the test result information storage unit 404. The OFC test result information storage unit 404 is similar to the test result information storage unit 207 of the OFC management apparatus 102, but stores only the test results determined by the own apparatus. In the example illustrated in FIG. 13, among the stored content examples of the test result information storage unit 207 illustrated in FIG. 10, the request ID “C028, C029, R134”, the determination time corresponding to the request ID, and the test result are stored. Yes.

  FIG. 14 is a table showing default values of test packets for communication confirmation. When the test call generation unit 412 generates a test packet for confirming communication, the test call generation unit 412 generates a test packet in accordance with the specified virtual network transfer rule. For items not specified in the virtual network transfer rule, The values shown in FIG. 14 are set. Even if values are shown in FIG. 14, the virtual network transfer rule is given priority for items specified in the virtual network transfer rule.

  When the protocol is specified in the virtual network transfer rule, the header item of the specified protocol and the payload are used among the header types shown in FIG. For example, when TCP is specified as a protocol, an Ethernet header, an IP header, a TCP header, and a payload are used. In FIG. 14, items that are not specified in the virtual network transfer rule may be arbitrary values. For example, a predetermined value is used. If no protocol is specified in the virtual network transfer rule, the protocol is UDP. In addition, an invalid value is set in the CRC (Cyclic Redundancy Check) of the test packet so that the test packet is discarded when it passes to another device.

  FIG. 15 is a table showing default values of test packets for route confirmation. For the test packet for route confirmation, the setting rule for each item including CRC is the same as that for the test packet for communication confirmation, but in addition to the request ID, information identifying the destination switch, The difference is that information indicating the route up to is set.

  FIG. 16 is a sequence diagram for explaining the communication confirmation process. The OFC management apparatus 102 receives a communication confirmation request from the topology management apparatus 101 (Sa1). Next, the OFC management apparatus 102 transmits a reception standby request to the OFC 104b that controls the OFS at the end point of the path whose communication is confirmed by the received request (Sa2). The OFC 104b receives the reception standby request and waits for reception of a test packet (Sa3).

  Next, the OFC management apparatus 102 transmits the communication confirmation request received from the topology management apparatus 101 to the OFC 104a that controls the OFS at the starting point of the path for which communication is confirmed (Sa4). The OFC 104a receives the communication confirmation request (Sa5). The OFC 104a that has received the communication confirmation request generates a test packet (Sa6) and transmits it to the OFS at the starting point of the path for which communication is confirmed (Sa7).

  After that, the OFC 104b that has been waiting for reception of the test packet receives the transfer of the test packet transmitted by the OFC 104a from the OFS that is controlled by its own device using PacketIn, or after receiving a reception standby request. When the timeout time elapses, the result of the communication confirmation is determined (Sa8).

The OFC 104b transmits the confirmation result obtained by the determination to the OFC management apparatus 102 (Sa9). The OFC management apparatus 102 receives the confirmation result (Sa10), and transmits the received confirmation result to the topology management apparatus 101 (Sa11). If the cycle is included in the communication confirmation request, the OFC 104a generates a test packet after transmitting the test packet in step Sa6 and then transmits the test packet (Sa12). (Sa13). Thereby, communication check is periodically performed.
FIG. 16 shows the case where the OFC 104a controls the OFS at the starting point of the path for which communication is confirmed, and the OFC 104b controls the OFS at the end of the path. However, there is a case where the same OFC controls both the OFS at the start point and the OFS at the end point of the route for which communication is confirmed. In that case, the OFC 104a and the OFC 104b in FIG. 16 are the same OFC.

  FIG. 17 is a sequence diagram for explaining route confirmation processing. The example of FIG. 17 is an example of a sequence when the destination switch is not specified in the route confirmation request. The OFC management apparatus 102 receives a route confirmation request from the topology management apparatus 101 (Sb1). Next, the OFC management apparatus 101 transmits the route confirmation request to the OFC 104a that controls the OFS at the starting point of the route to be routed (Sb2). The OFC 104a receives the request for route confirmation (Sb3). The OFC 104a that has received the request for route confirmation generates a test packet (Sb4) and transmits it to the OFS at the starting point of the route to be route confirmed (Sb5).

  The OFC 104b receives the packet to which the test packet transmitted from the OFC 104a has been transferred from the OFS that is controlled by the own device using PacketIn (Sb6). The OFC 104b transmits a test packet reception notification to the OFC 104a (Sb7). The OFC 104a receives the reception notification (Sb8). On the other hand, the OFC 104b that transmitted the reception notification generates a test packet in which information identifying the OFS that has PacketIn the test packet is added to the payload of the test packet received in step Sb6 in order to confirm the subsequent path. (Sb9) and transmit to the OFS (Sb10).

  The OFC 104b detects a time-out if no OFC is notified of reception even after a predetermined time-out period has elapsed since the test packet was transmitted (Sb11). The OFC 104b transmits information indicating the path stored in the payload of the test packet generated in step Sb9 to the OFC management apparatus 102 as a confirmation result (Sb12). The OFC management apparatus 102 receives the confirmation result (Sb13), and transmits the confirmation result to the topology management apparatus 101 (Sb14).

  FIG. 18 is another sequence diagram illustrating the route confirmation process. The example of FIG. 18 is an example of a sequence when a destination switch is specified in a route confirmation request. 18, parts corresponding to those in FIG. 17 are given the same reference numerals, and descriptions thereof are omitted. The sequence in FIG. 18 differs from that in FIG. 17 in that only Step Sc9 is provided instead of Steps Sb9 and Sb10. In step Sc9, the OFC 104b compares the destination switch described in the payload of the test packet received by PacketIn from the OFS with the OFS that has PacketIn. Then, since they match, the OFC 104b adds the PacketIn OFS to the information indicating the route described in the payload of the test packet, and uses it as a confirmation result.

  FIGS. 17 and 18 show the case where the OFC 104a controls the OFS at the starting point of the route to be confirmed, and the OFC 104b controls the OFS at the end of the route. However, the same OFC may control both the starting point OFS and the end point OFS of the route to be confirmed. In that case, the OFC 104a and the OFC 104b in FIGS. 17 and 18 are the same OFC. 17 and 18, when there is an OFS between the starting point and the ending point of the route to be confirmed, the OFC controlling the OFS performs the same processing as steps Sb6, Sb7, Sb9, and Sb10. After performing the test packet transmission, the reception notification is received in the same manner as in step Sb8. When there are a plurality of OFS between the start point and the end point, each OFC that controls each OFS performs the same processing as steps Sb6, Sb7, Sb9, Sb10, and Sb8 as described above.

  FIG. 19 is a sequence diagram illustrating transfer processing. The OFC 104a detects that the processing load is excessive, and determines that transfer to another OFC is necessary (Sd1). The OFC 104a requests each of the processing margins from other OFCs (Sd2). The OFCs 104b and 104c receive the request (Sd3 and Sd4), and transmit their processing margin amounts (Sd5 and Sd6), respectively. The OFC 104a receives these processing margins (Sd7).

  The OFC 104a determines the transfer destination as the OFC 104b (Sd8). Then, the OFC 104a reduces the processing (Sd9) in synchronization with the addition of the processing of the transfer destination OFC 104b (Sd10). The OFC 104a transmits the transfer result to the OFC management apparatus 102.

In the present embodiment, OFS is a network switch that complies with the OpenFlow standard, but any network switch that can set a transfer rule and can configure a plurality of virtual networks may be used.
Further, the management network 103 may be included in a network configured by the OFSs 100a to 100f.
Further, in this embodiment, there are three OFCs and six OFSs, but both may be fewer or more.

  In addition, when the notification destination determination unit 202 determines the OFC that is the request notification destination, that is, the OFC that generates the test packet, an OFC with a large processing margin may be given priority.

As described above, in this embodiment, even in a network management system that controls a network in which a plurality of virtual networks can be configured by a plurality of OFCs, it is related to a route such as a communication check or a route check on each virtual network. Confirmation can be made.
Furthermore, even if the OFSs 101a to 101f are managed by the plurality of OFCs 104a to 104c, the processing is not concentrated on the OFC management apparatus 102. Therefore, the number of OFCs can be increased to manage a large-scale network.
Furthermore, since processing is transferred from one OFC to another OFC, the OFC management apparatus 102 is not burdened with processing, so the number of OFCs can be increased to manage a large-scale network. Can do.

  Also, a program for realizing the functions of the OFC management apparatus 102 and OFCs 104a to 104c in FIG. 1 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed. Thus, these devices may be realized. Here, the “computer system” includes an OS and hardware such as peripheral devices.

  The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case, and a program that holds a program for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like within a scope not departing from the gist of the present invention.

10 ... Network management system 100a-100f ... OFS
DESCRIPTION OF SYMBOLS 101 ... Topology management apparatus 102 ... OFC management apparatus 103 ... Management network 104a-104c ... OFC
DESCRIPTION OF SYMBOLS 201 ... Request reception part 202 ... Notification destination determination part 203 ... OFC cooperation part 204 ... Result notification part 205 ... Test management information storage part 206 ... OFC management information storage part 207 ... Test result information storage part 208 ... Transfer result reception part 401 ... Test processing unit 402 ... Switch control unit 403 ... Test management information storage unit 404 ... Test result information storage unit 405 ... Transfer processing unit 406 ... Adjacent information storage unit 411 ... Confirmation request reception unit 412 ... Test call generation unit 413 ... Test result determination Unit 414 ... test result transmission unit 415 ... reception standby request reception unit 416 ... test call reception notification transmission unit 417 ... test call reception notification reception unit 451 ... transfer determination unit 452 ... transfer destination determination unit 453 ... processing reduction unit 454 ... transfer result Notification unit 455 ... processing margin amount notification unit 456 ... processing addition unit

Claims (14)

A network management system comprising a plurality of controllers each controlling a part of a plurality of switches that transfer packets on a virtual network, and a management device that manages the plurality of controllers,
The management device
A request acquisition unit for acquiring a confirmation request regarding one path in the virtual network;
A notification destination determination unit that determines, as the notification destination of the request, the controller that controls the switch of the transmission source of the one path among the plurality of switches;
A network management system comprising: The confirmation regarding the one route is a communication confirmation of the one route,
The said notification destination determination part determines the said controller which controls the switch of the destination of the said one path | route among these switches as an arrival confirmation destination of the test packet by the said request | requirement. The network management system described. The controller is
When a request for confirmation regarding the one route is notified from the management device, a test packet specifying a predetermined maximum number of hops is generated, and the generated test packet is transmitted to the head switch of the one route. And
When notified from any of the plurality of switches that the number of hops of the test packet has reached the maximum, notifying the management device;
The network management system according to claim 1. The controller is
When notified from the end switch of the one path among the plurality of switches that the hop number of the test packet has reached the maximum, the management apparatus is notified,
When notified from the switches other than the end point of the one path among the plurality of switches that the number of hops of the test packet has reached the maximum, a test packet specifying a predetermined maximum number of hops is generated and generated The network management system according to claim 3, wherein the test packet is transmitted to the switch that has notified that the maximum number of hops has been reached. The confirmation regarding the one route is a route confirmation of the one route,
The controller is
When it is notified from the switches other than the end point of the one path among the plurality of switches that the hop number of the test packet has reached the maximum, the test packet specifies a predetermined maximum hop number, Generate a test packet with payload data as data in which information indicating a switch that has notified that the maximum number of hops of the test packet has been reached is added to the payload data of the test packet whose number has reached the maximum, and the generated Sending a test packet to the switch that has notified that the test packet has reached the maximum number of hops;
When notified from the end switch of the one path among the plurality of switches that the number of hops of the test packet has reached the maximum, the payload data of the test packet having the maximum number of hops is managed by the management The network management system according to claim 4, wherein the network management system notifies the device. The controller is
An adjacent information storage unit that stores correspondence between the switch that can be controlled by the device and another controller that can control the switch;
A transfer destination determination unit that refers to the adjacent information storage unit and determines another controller capable of switch control of a transmission source of the one path as a transfer destination of processing according to the request. Item 4. The network management system according to Item 1. A management device in a network management system comprising a plurality of controllers each controlling a part of a plurality of switches that transfer packets on a virtual network, and a management device that manages the plurality of controllers,
A request acquisition unit for acquiring a confirmation request regarding one path in the virtual network;
A notification destination determination unit that determines, as the notification destination of the request, the controller that controls the switch of the transmission source of the one path among the plurality of switches;
A management apparatus comprising: A controller that controls a part of a plurality of switches that transfer packets over a virtual network,
When confirmation about one route in the virtual network is requested, a test packet designating a predetermined maximum hop number is generated, and the generated test packet is transmitted to the first switch of the one route,
When notified from any of the plurality of switches that the number of hops of the test packet has reached the maximum, notifying other devices;
A controller characterized by. A controller that controls a part of a plurality of switches that transfer packets over a virtual network,
When confirmation regarding one route in the virtual network is requested, a test processing unit that performs processing according to the request;
An adjacent information storage unit that stores correspondence between the switch that can be controlled by the device and another controller that can control the switch;
A transfer destination determining unit that refers to the adjacent information storage unit and determines another controller capable of switch control of the transmission source of the one path as a transfer destination of processing according to the request. . A management method in a network management system comprising a plurality of controllers each controlling a part of a plurality of switches that transfer packets on a virtual network, and a management device that manages the plurality of controllers,
A first process in which the management device obtains a confirmation request for one path in the virtual network;
A second step in which the management device determines the controller that controls the switch of the transmission source of the one path among the plurality of switches as a notification destination of the request;
The management method characterized by having. A control method in a plurality of controllers, each of which controls a part of a plurality of switches that transfer packets on a virtual network,
When the first controller among the plurality of controllers is requested to confirm the one route in the virtual network, the first controller generates a test packet specifying a predetermined maximum number of hops, and the generated test packet is A first process of transmitting to the head switch of a path;
Of the plurality of controllers, when a second controller is notified from any of the plurality of switches that the number of hops of the test packet has reached the maximum, a second process of notifying other devices;
A control method characterized by comprising: A control method in a controller for controlling a part of a plurality of switches that transfer packets on a virtual network,
When the controller is requested to confirm a route in the virtual network, a first process for performing processing according to the request;
The controller refers to an adjacent information storage unit that stores a correspondence between a switch that can be controlled by the device and another controller that can control the switch, and can control the switch of the transmission source of the one route. And a second step of determining as a transfer destination of the processing according to the request. Computer
For causing a part of a plurality of switches that transfer packets on a virtual network to function as a management device in a network management system, each of which includes a plurality of controllers to be controlled and a management device that manages the plurality of controllers. A program,
The management device
A request acquisition unit for acquiring a confirmation request regarding one path in the virtual network;
A notification destination determination unit that determines, as the notification destination of the request, the controller that controls the switch of the transmission source of the one path among the plurality of switches;
The program characterized by comprising.   The program for functioning a computer as a controller of Claim 8 or Claim 9.

Images