CN115766663A

CN115766663A - In-band management connection method and device for switch, switch and storage medium

Info

Publication number: CN115766663A
Application number: CN202211374299.8A
Authority: CN
Inventors: 王倩
Original assignee: Beijing Armyfly Technology Co Ltd
Current assignee: Beijing Armyfly Technology Co Ltd
Priority date: 2022-11-03
Filing date: 2022-11-03
Publication date: 2023-03-07

Abstract

The invention discloses a method and a device for in-band management connection of a switch, the switch and a storage medium. The method is applied to an OpenFlow switch and comprises the following steps: sending a DHCP request message; receiving a DHCP reply message returned by a controller, acquiring an in-band management IP address, a controller IP address and an uplink port of a local machine according to the DHCP reply message, and configuring an OpenFlow flow table pointing to the controller on the basis of the controller IP address and the uplink port; and forwarding a first message which is initiated by the IP address of the controller and has a source IP address as the in-band management IP address of the local machine to the controller through the OpenFlow flow table, receiving a second message replied by the controller, and establishing an in-band communication channel between the local machine and the controller. According to the technical scheme of the embodiment of the invention, the OpenFlow flow table is initialized and configured according to the analysis result of the DHCP reply message fed back by the controller, and then the in-band communication channel between the OpenFlow flow table and the controller is opened according to the OpenFlow flow table, so that the resource consumed by network maintenance is reduced, and the difficulty in realizing in-band management of the OpenFlow switch is reduced.

Description

In-band management connection method and device for switch, switch and storage medium

Technical Field

The present invention relates to the field of ethernet communications technologies, and in particular, to a method and an apparatus for in-band management connection of a switch, and a storage medium.

Background

The connection channel between the OpenFlow switch and the controller may be an out-of-band communication channel or an in-band communication channel. As shown in fig. 1, when implementing in-band management of an OpenFlow switch at present, a Virtual Local Area Network (VLAN) for in-band communication configuration needs to be established between a controller and the OpenFlow switch, an in-band management IP address of the OpenFlow switch and an IP address of the controller need to be manually configured, and a corresponding three-layer data forwarding function is configured in the OpenFlow switch, so that the OpenFlow switch supports both conventional switching and OpenFlow switching, thereby determining whether a packet is subjected to conventional three-layer forwarding by identifying the VLAN or is matched through an OpenFlow table. However, this approach may increase the resources consumed for network maintenance and increase the complexity of the OpenFlow switch.

Disclosure of Invention

The invention provides a method and a device for switch in-band management connection, a switch and a storage medium, which are used for solving the problems of high complexity and high network maintenance cost of the conventional OpenFlow switch in-band management.

According to an aspect of the present invention, there is provided a method for in-band management connection of a switch, which is applied to an OpenFlow switch, and includes:

sending a DHCP (dynamic host configuration protocol) request message;

receiving a DHCP reply message returned by a controller, acquiring an internal management IP (Internet protocol) address, a controller IP address and an uplink port of a local machine according to the DHCP reply message, and configuring an OpenFlow flow table pointing to the controller based on the controller IP address and the uplink port;

and forwarding a first message which is initiated by the IP address of the controller and has a source IP address as the in-band management IP address of the local machine to the controller through the OpenFlow flow table, receiving a second message replied by the controller, and establishing an in-band communication channel between the local machine and the controller.

Optionally, the obtaining, according to the DHCP reply packet, an in-band management IP address of the local device, a controller IP address, and an uplink port, and configuring an OpenFlow flow table pointing to the controller based on the controller IP address and the uplink port includes:

sending the DHCP reply message to a CPU for processing through a Table-miss flow Table to obtain an IP address of a controller and an in-band management IP address of a local machine;

taking a port for receiving the DHCP reply message as an uplink port;

configuring a first flow table and a second flow table based on the controller IP address and the uplink port;

wherein, in the first flow table, the matching entry is: the destination IP address is an ARP (address resolution protocol) message of the controller IP address, and the action items are: designating the output port as an uplink port;

in the second flow table, the matching entry is: the target IP address is an IP message of the controller IP address, and the action items are as follows: the output port is designated as an add port.

Optionally, after the establishing an in-band communication channel between the local device and the controller, the method further includes:

if a DHCP request message sent by a downstream switch directly connected with the local machine is received, forwarding the DHCP request message to a controller through a second flow table;

and forwarding the DHCP reply message returned by the controller to the downstream switch through a port for receiving the DHCP request message of the downstream switch, so that the downstream switch configures an OpenFlow flow table pointing to the controller according to the DHCP reply message.

Optionally, if a DHCP request message sent by a downstream switch directly connected to the local computer is received, forwarding the DHCP request message to the controller through the second flow table includes:

if a DHCP request message sent by a downstream switch directly connected with the local machine is received, the DHCP request message is uploaded to a CPU through a Table-miss flow Table and encapsulated into a third message; the third message includes: the local machine receives a port of a DHCP request message of the downstream switch;

and inquiring the second flow table, and forwarding the third message to a controller through the uplink port.

Optionally, forwarding, through a port that receives the DHCP request packet of the downstream switch, the DHCP reply packet returned by the controller to the downstream switch, so that the downstream switch configures an OpenFlow flow table that points to the controller according to the DHCP reply packet, including:

receiving a fourth message returned by the controller;

sending the fourth message to a CPU (central processing unit) for decapsulation through a Table-miss flow Table to obtain a DHCP reply message, and determining an output port of the DHCP reply message as a port for receiving a DHCP request message of the downstream switch;

and forwarding the DHCP reply message to the downstream switch through a port for receiving the DHCP request message of the downstream switch, so that the downstream switch configures an OpenFlow flow table pointing to a controller according to the DHCP reply message.

Optionally, after forwarding, through the port that receives the DHCP request message of the downstream switch, the DHCP reply message returned by the controller to the downstream switch, so that the downstream switch configures an OpenFlow flow table that points to the controller according to the DHCP reply message, the method further includes:

receiving a third flow table and a fourth flow table issued by the controller;

wherein, in the third flow table, the matching entry is: the target IP address is an ARP message of an in-band management IP address of a downstream switch directly connected with the local machine, and the action items are as follows: appointing an output port as a port for receiving the DHCP request message of the downstream switch;

in the fourth flow table, the matching entry is: the target IP address is an IP message of an in-band management IP address of a downstream switch directly connected with the local machine, and the action items are as follows: and designating an output port as a port for receiving the DHCP request message of the downstream switch.

Optionally, after receiving the third flow table and the fourth flow table issued by the controller, the method further includes:

if an ARP request message sent by a downstream switch directly connected with the local computer is received, forwarding the ARP request message to a controller by inquiring the first flow table, and forwarding an ARP reply message returned by the controller to the downstream switch by inquiring a third flow table;

and if an IP message sent by a downstream switch directly connected with the local machine is received, forwarding the IP message to the controller by inquiring the second flow table, and forwarding an IP reply message returned by the controller to the downstream switch by inquiring a fourth flow table so as to establish an in-band communication channel between the downstream switch and the controller.

According to another aspect of the present invention, there is provided a switch in-band management connection apparatus, applied to an OpenFlow switch, including:

the sending module is used for sending a Dynamic Host Configuration Protocol (DHCP) request message;

the receiving configuration module is used for receiving a DHCP reply message returned by the controller, acquiring an in-band management IP address, a controller IP address and an uplink port of the local machine according to the DHCP reply message, and configuring an OpenFlow flow table pointing to the controller based on the controller IP address and the uplink port;

the establishing module is used for forwarding a first message which is initiated by the IP address of the controller and has a source IP address as the in-band management IP address of the local machine to the controller through the OpenFlow flow table, receiving a second message replied by the controller and establishing an in-band communication channel between the local machine and the controller.

According to another aspect of the present invention, there is provided an OpenFlow switch including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the switch inband management connection method of any embodiment of the invention.

According to another aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement the method for managing connections in-band of a switch according to any one of the embodiments of the present invention when the computer instructions are executed.

The technical scheme of the embodiment of the invention is applied to an OpenFlow switch, and is characterized in that a DHCP reply message returned by a controller aiming at a local DHCP request message is received, an in-band management IP address configured for the local by the controller, an IP address of the controller and an uplink port are obtained according to the DHCP reply message, and an OpenFlow flow table pointing to the controller is initialized and configured based on the controller IP address and the uplink port; the method comprises the steps of forwarding a first message which is initiated by an IP address aiming at a controller and has a source IP address as the local in-band management IP address to the controller through inquiring an OpenFlow flow table, receiving a second message replied by the controller, and establishing an in-band communication channel between the local and the controller, so that the problems of high complexity and high network maintenance cost of realizing in-band management of the conventional OpenFlow switch are solved, the OpenFlow flow table is initialized and configured according to an analysis result of a DHCP reply message fed back to the controller, the in-band communication channel between the local and the controller is opened according to the OpenFlow flow table, resources consumed by network maintenance are reduced, and the realization difficulty of in-band management of the OpenFlow switch is reduced.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic diagram of an OpenFlow switch in-band management in the prior art;

fig. 2 is a flowchart of a method for managing a connection in-band for a switch according to an embodiment of the present invention;

fig. 3 is a schematic diagram of an OpenFlow switch in-band connection to which an embodiment of the present invention is applied;

fig. 4 is a flowchart of a method for in-band management connection of a switch according to a second embodiment of the present invention;

FIG. 5 is a flow chart illustrating the execution of a Table-miss flow Table to which embodiments of the present invention are applicable;

fig. 6 is a timing interaction diagram of an inband management connection of a switch according to a third embodiment of the present invention;

fig. 7 is a schematic structural diagram of an inband management connection device of a switch according to a fourth embodiment of the present invention;

fig. 8 is a schematic structural diagram of an OpenFlow switch implementing the in-band switch connection management method according to the embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Moreover, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example one

Fig. 2 is a flowchart of a method for in-band management connection of a switch according to an embodiment of the present invention, where the method is applicable to a situation where an OpenFlow switch establishes an in-band communication channel with a controller according to a DHCP reply message of the controller, and the method may be executed by a device for in-band management connection of a switch, where the device may be implemented in a form of hardware and/or software, and the device may be configured in an OpenFlow switch and used in cooperation with the controller. As shown in fig. 1, the method is applied to an OpenFlow switch, and includes:

s110, sending a DHCP request message.

In this embodiment, the OpenFlow switch serves as a DHCP client, and sends a DHCP request message through all available in-band communication ports, so that a controller serving as a DHCP server can receive the DHCP request message of the local computer and configure an in-band management IP address for the local computer.

The OpenFlow switch may be a switch directly connected to the controller, for example, openFlow switch a in fig. 3, or may be a switch indirectly connected to the controller, for example, openFlow switch b in fig. 3. If the local machine is a switch directly connected with the controller, the local machine can directly perform DHCP interaction with the controller, and the controller can directly receive a DHCP request message of the local machine; if the local machine is a switch indirectly connected with the controller, the DHCP request message of the local machine needs to be forwarded by the intermediate switch to reach the controller. The intermediate switch is a native directly connected upstream OpenFlow switch.

The DHCP is a network protocol of a local area network, which means that a server controls a segment of IP address range, and a client can automatically obtain an IP address and a subnet mask allocated to the server when logging in the server. The DHCP protocol uses a client/server model, with the task of dynamic allocation of host addresses driven by the network host. When the DHCP server receives the information of applying address from the network host, it will send the relevant address configuration information to the network host to realize the dynamic configuration of the network host address information.

S120, receiving a DHCP reply message returned by the controller, acquiring a local in-band management IP address, a controller IP address and an uplink port according to the DHCP reply message, and configuring an OpenFlow flow table pointing to the controller based on the controller IP address and the uplink port.

In this embodiment, after receiving the DHCP request message of the local machine, the controller, as a DHCP server, returns a DHCP reply message to the local machine to notify the local machine of the IP address of the controller and the in-band management IP address allocated to the local machine by the controller. If the local machine is a switch directly connected with the controller, the local machine can directly receive a DHCP reply message replied by the controller; if the local machine is a switch indirectly connected with the controller, the local machine needs to receive the DHCP reply message forwarded by the intermediate switch.

Optionally, the acquiring an in-band management IP address, a controller IP address, and an uplink port of a local device according to the DHCP reply packet, and configuring an OpenFlow flow table pointing to a controller based on the controller IP address and the uplink port specifically includes: sending the DHCP reply message to a CPU for processing through a Table-miss flow Table to obtain an IP address of a controller and an in-band management IP address of a local machine; taking a port for receiving the DHCP reply message as an uplink port; configuring a first flow table and a second flow table based on the controller IP address and the uplink port;

wherein, in the first flow table, a matching entry is: the target IP address is an ARP message of the controller IP address, and the action items are as follows: designating the output port as an uplink port; in the second flow table, the matching entry is: the target IP address is an IP message of the controller IP address, and the action items are as follows: the output port is designated as an add port.

In this embodiment, after the local machine receives the DHCP reply message returned by the controller, because the flow Table matching the DHCP reply message is not found locally, the DHCP reply message can be sent to the CPU through the Table-miss flow Table, and is processed by the protocol stack, the source IP address in the DHCP reply message is obtained as the controller IP address, the destination IP address is obtained as the local in-band management IP address, the port through which the local machine receives the DHCP reply message returned by the controller is used as the uplink port, and the uplink port can be understood as the port through which the local machine sends the message to the controller, that is, the port through which the local machine receives the DHCP reply message returned by the controller and the port through which the local machine sends the message to the controller are the same port. Illustratively, if the native is openflowswitch a in fig. 3, the uplink port is port1, and if the native is openflowswitch b in fig. 3, the uplink port is port3. And then generating a first flow table used for sending an ARP message to the controller and a second flow table used for sending the IP message to the controller according to the IP address of the controller and the uplink port, and sending the first flow table and the second flow table to the local computer for storage, so that the messages can be conveniently forwarded to the controller through table lookup in the follow-up process.

The first flow table is used for indicating and sending an ARP message with a target IP address as a controller IP address to the controller through the uplink port. And the second flow table is used for indicating and sending the IP message with the destination IP address as the IP address of the controller to the controller through the uplink port. And the uplink port appointed in the first flow table and the second flow table is a port for receiving the DHCP reply message returned by the controller by the local machine.

The Table-miss flow Table is issued when the OpenFlow switch is initialized, and is used for uploading to a CPU for processing when the message is not matched with any flow Table.

In this embodiment, the controller is used as a DHCP server to complete the allocation of the in-band management IP address of the Openflow switch, so that the Openflow switch can obtain the controller IP address and the in-band management IP address of the local machine by analyzing the DHCP reply message returned by the controller. The OpenFlow switch can initiate flow table configuration by acquiring a physical port for receiving a DHCP reply message and combining with a controller IP address, an in-band management IP and a controller IP address of the OpenFlow switch do not need to be manually configured, and a corresponding three-layer data forwarding function does not need to be configured in the OpenFlow switch, so that resources consumed by network maintenance are reduced, and the difficulty in realizing in-band management of the OpenFlow switch is reduced.

S130, forwarding a first message which is initiated by the IP address of the controller and has a source IP address as the in-band management IP address of the local machine to the controller through the OpenFlow flow table, receiving a second message replied by the controller, and establishing an in-band communication channel between the local machine and the controller.

In this embodiment, after the first flow table and the second flow table are generated, for a first packet, such as an ARP request packet or a TCP connection packet, where a source IP address to be sent by a local computer is an in-band management IP address of the local computer, and a destination IP address is an IP address of a controller, the ARP request packet may be forwarded to the controller by querying the first flow table, and the TCP connection packet may be forwarded to the controller by querying the second flow table. After receiving the ARP message or TCP connection message returned by the controller, sending the message to a CPU through a Table-miss flow Table of the local machine, and performing message analysis processing by a protocol stack until an in-band communication channel between the local machine and the controller is established, namely TCP connection is established between the local machine and the controller according to an in-band management IP address of the local machine and an IP address of the controller.

The technical scheme of the embodiment of the invention is applied to an OpenFlow switch, and comprises the steps of receiving a DHCP reply message returned by a controller aiming at a DHCP request message of a local machine, obtaining an in-band management IP address, an IP address and an uplink port of the controller configured for the local machine by the controller according to the DHCP reply message, and initializing and configuring an OpenFlow flow table pointing to the controller based on the controller IP address and the uplink port; the method comprises the steps of forwarding a first message which is initiated by an IP address aiming at a controller and has a source IP address as the local in-band management IP address to the controller through inquiring an OpenFlow flow table, receiving a second message replied by the controller, and establishing an in-band communication channel between the local and the controller, so that the problems of high complexity and high network maintenance cost of realizing in-band management of the conventional OpenFlow switch are solved, the OpenFlow flow table is initialized and configured according to an analysis result of a DHCP reply message fed back to the controller, the in-band communication channel between the local and the controller is opened according to the OpenFlow flow table, resources consumed by network maintenance are reduced, and the realization difficulty of in-band management of the OpenFlow switch is reduced.

Example two

Fig. 4 is a flowchart of a method for managing a connection in band by a switch according to a second embodiment of the present invention. In this embodiment, after the in-band communication channel between the local device and the controller is established, a specific step of assisting a downstream switch directly connected to the local device to configure an OpenFlow flow table pointing to the controller according to the OpenFlow table pointing to the controller configured by the local device, and then establishing the in-band communication channel between the downstream switch and the controller is added. As shown in fig. 4, the method is applied to an OpenFlow switch, and includes:

s210, sending a DHCP request message.

S220, receiving a DHCP reply message returned by the controller, acquiring an in-band management IP address, a controller IP address and an uplink port of the local machine according to the DHCP reply message, and configuring a first flow table and a second flow table pointing to the controller based on the controller IP address and the uplink port.

Wherein, in the first flow table, the matching entry is: the destination IP address is an ARP message of the IP address of the controller, and the action items are as follows: designating the output port as an uplink port;

in the second flow table, the matching entry is: the target IP address is an IP message of the controller IP address, and the action items are as follows: the output port is designated as an uplink port.

S230, forwarding a first message which is initiated by the IP address of the controller and has the source IP address as the in-band management IP address of the local machine to the controller through the first flow table or the second flow table, receiving a second message replied by the controller, and establishing an in-band communication channel between the local machine and the controller.

And S240, if a DHCP request message sent by a downstream switch directly connected with the local machine is received, forwarding the DHCP request message to the controller through the second flow table.

In this embodiment, for an OpenFlow switch, an in-band communication channel is established first with an upstream switch directly connected to the OpenFlow switch, so that the local machine can establish the in-band communication channel between the local machine and the controller by using the in-band communication channel of the directly connected upstream switch, and then the local machine can serve as the upstream switch to assist the directly connected downstream switch to establish an in-band connection with the controller.

For example, assuming that the in-band communication channel between the local machine and the controller is already established, and the local machine is the openflowswitch a directly connected to the controller in fig. 3, when the local machine receives a DHCP request message sent by the openflowswitch b, the local machine may forward the DHCP request message to the controller by querying a second flow table of the local machine, so as to assist the openflowswitch b in establishing the in-band communication channel with the controller. Or, assuming that the local machine is the openflowswitch b in fig. 3 and the in-band communication channel between the local machine and the controller has been established, when the local machine receives a DHCP request message sent by the openflowswitch c, the local machine may forward the DHCP request message to the controller by querying a second flow table of the local machine.

Optionally, if a DHCP request message sent by a downstream switch directly connected to the local computer is received, the DHCP request message is forwarded to the controller through the second flow table, including: if a DHCP request message sent by a downstream switch directly connected with the local machine is received, uploading the DHCP request message to a CPU through a Table-miss flow Table and packaging the DHCP request message into a third message; the third packet includes: the local machine receives a port of the DHCP request message of the downstream switch; and inquiring the second flow table, and forwarding the third message to a controller through the uplink port.

In this embodiment, after receiving a DHCP request message sent by a downstream switch directly connected to the local machine, because the local machine does not find a flow Table matching the DHCP request message, and a destination IP address of the DHCP request message is not an in-band management IP address of the local machine, the DHCP request message may be uploaded to a CPU through a Table-miss flow Table and encapsulated as a third message, that is, the DHCP request message is encapsulated as a Packet _ in message carrying a port of the local machine receiving the DHCP request message of the downstream switch according to an OpenFlow protocol. And then forwarding the Packet _ in message to the controller through the uplink port by inquiring a second flow table of the local machine.

The OpenFlow switch initially issues a Table-miss flow Table, and the Table-miss flow Table is used for uploading to a CPU for processing when a message is not matched with any flow Table. As shown in fig. 5, before uploading a message to a CPU, determining a message type according to a destination IP address in the message, and if the message belongs to a local management message whose destination IP address is a local in-band management IP address, processing the message uploaded to the CPU by a local protocol stack to establish an in-band communication channel with a controller, or performing OpenFlow protocol interaction by the in-band communication channel of the local and the controller; if the message belongs to a service message with the destination IP address as the IP address of the controller, when judging that the in-band communication channel of the local machine is normally connected, the message is sent to the CPU to be packaged into a Packet _ in message and sent to the controller. When the controller is connected with the controller, a protocol packet with a target IP as the controller IP needs to be replied to the controller after a message replied by the controller is received.

And S250, forwarding the DHCP reply message returned by the controller to the downstream switch through a port for receiving the DHCP request message of the downstream switch, so that the downstream switch configures an OpenFlow flow table pointing to the controller according to the DHCP reply message.

In this embodiment, after forwarding the DHCP request message of the directly connected downstream switch to the controller according to the second flow table of the local machine, the controller encapsulates the DHCP reply message into a Packet _ out message and returns the Packet _ out message to the local machine, and the local machine forwards the DHCP reply message to the downstream switch through a port that receives the DHCP request message of the downstream switch.

In an optional embodiment, forwarding, by a port that receives a DHCP request message of the downstream switch, a DHCP reply message returned by the controller to the downstream switch, so that the downstream switch configures an OpenFlow flow table pointing to the controller according to the DHCP reply message, may include: receiving a fourth message returned by the controller; sending the fourth message to a CPU (central processing unit) for decapsulation through a Table-miss flow Table to obtain a DHCP reply message, and determining an output port of the DHCP reply message as a port for receiving a DHCP request message of the downstream switch; and forwarding the DHCP reply message to the downstream switch through a port for receiving the DHCP request message of the downstream switch, so that the downstream switch configures an OpenFlow flow table pointing to a controller according to the DHCP reply message.

The fourth message is a Packet _ out message, and because the local computer does not have a flow table matched with the Packet _ out message, when encapsulating a DHCP reply message with a destination IP address being an IP address of a downstream switch directly connected to the local computer into the Packet _ out message, the controller specifies an output port of the DHCP reply message in the Packet _ out message, and provides an interface for the local computer to receive a DHCP request message directly connected to the downstream switch, so that the local computer can conveniently forward the DHCP reply message.

Optionally, after forwarding, by the port that receives the DHCP request message of the downstream switch, the DHCP reply message returned by the controller to the downstream switch, so that the downstream switch configures an OpenFlow flow table pointing to the controller according to the DHCP reply message, the method further includes: receiving a third flow table and a fourth flow table issued by the controller;

wherein, in the third flow table, a matching entry is: the target IP address is an ARP message of an in-band management IP address of a downstream switch directly connected with the local machine, and the action items are as follows: the appointed output port is a port for receiving the DHCP request message of the downstream switch; in the fourth flow table, the matching entry is: the target IP address is an IP message of an in-band management IP address of a downstream switch directly connected with the local machine, and the action items are as follows: and designating an output port as a port for receiving the DHCP request message of the downstream switch.

It should be noted that, in order to facilitate interaction between the subsequent local computer and the directly connected downstream switch, the controller, while returning the Packet _ out message, also generates a third flow table for sending an ARP message to the downstream switch directly connected to the local computer, and a fourth flow table for sending an IP message to the downstream switch directly connected to the local computer, and sends the third flow table and the fourth flow table to the local computer.

And the third flow table is used for indicating, and sending an ARP message with a target IP address being an in-band management IP address of a downstream switch directly connected with the local machine to the controller through a port of the local machine for receiving a DHCP request message of the downstream switch. And the fourth flow table is used for indicating that the IP message with the destination IP address as the in-band management IP address of the downstream switch directly connected with the local machine is sent to the controller through a port of the local machine for receiving the DHCP request message of the downstream switch. The message output ports specified in the third flow table and the fourth flow table are the same as the output port of the DHCP reply message specified by the controller in the Packet _ out message.

In an optional implementation manner, after the receiving the third flow table and the fourth flow table sent by the controller, the method further includes: if an ARP request message sent by a downstream switch directly connected with the local computer is received, forwarding the ARP request message to a controller by inquiring the first flow table, and forwarding an ARP reply message returned by the controller to the downstream switch by inquiring a third flow table; and if an IP message sent by a downstream switch directly connected with the local machine is received, forwarding the IP message to the controller by inquiring the second flow table, and forwarding an IP reply message returned by the controller to the downstream switch by inquiring a fourth flow table so as to establish an in-band communication channel between the downstream switch and the controller.

According to the technical scheme of the embodiment of the invention, the OpenFlow switch obtains an in-band management IP address configured by the controller for the local machine, an IP address and an uplink port of the controller according to a DHCP reply message returned by the controller, and initializes and configures an OpenFlow flow table pointing to the controller based on the controller IP address and the uplink port, so that an in-band communication channel between the local machine and the controller is established according to the OpenFlow flow table, and then the in-band communication channel of the local machine is utilized to help a downstream switch directly connected with the local machine to open the in-band communication channel between the local machine and the controller, so that the problems of high complexity and high network maintenance cost of realizing in-band management of the existing OpenFlow switch are solved, resources consumed by network maintenance are reduced, and the difficulty in realizing in-band management of the OpenFlow switch is reduced.

EXAMPLE III

Fig. 6 is a timing interaction diagram of an inband management connection of a switch according to a third embodiment of the present invention. An OpenFlow switch directly connected to the controller is referred to as a first switch, and an OpenFlow switch not directly connected to the controller is referred to as a second switch, and then, with reference to the in-band connection diagram of fig. 3, taking a first switch OpenFlow switch a and a second switch OpenFlow switch b as an example, an in-band management connection method of the OpenFlow switch of fig. 6 is described, which includes the following steps:

the first switch and the second switch are used as DHCP clients and send DHCP request messages through all available in-band communication ports of the local machine.

The controller can receive a DHCP request message of the first switch OpenFlowSwitchA, and the controller is used as a DHCP server to reply the DHCP reply message to the first switch.

The first switch sends the DHCP reply message to a CPU through a Table-miss flow Table, obtains a source IP address in the DHCP reply message as a controller IP address, obtains a destination IP address as a local in-band management IP address, uses a port of the local machine for receiving the DHCP reply message as an uplink port, and configures a first flow Table based on the controller IP address and the uplink port: the matching items are: the target IP address is an ARP message of the controller IP address, and the action items are as follows: designating the output port as an uplink port; configuring a second flow table based on the controller IP address and the uplink port: the matching items are: the target IP address is an IP message of the controller IP address, and the action items are as follows: the output port is designated as an add port.

The first switch can respectively transmit an ARP request message and a TCP connection message initiated by the IP address of the controller to the controller by inquiring the first flow Table and the second flow Table, and after receiving the ARP message or the TCP connection message replied by the controller, the first switch transmits the ARP request message and the TCP connection message to a CPU (central processing unit) through a Table-miss flow Table of the first switch, and a protocol stack analyzes and processes the messages until an in-band communication channel between the first switch and the controller is established.

After the in-band communication channel of the first switch openflowswitch a is established, the second switch openflowswitch b is used as a downstream switch directly connected with the first switch, and the DHCP request message of the openflowswitch b is received by port2 of the openflowswitch a.

And the OpenFlowSwitchA uploads the DHCP request message of the OpenFlowSwitchB to the CPU through a Table-miss flow Table to be encapsulated into a Packet _ in message, and forwards the Packet _ in message to the controller through a second flow Table of the OpenFlowSwitchA.

And after receiving the Packet _ in message, the controller encapsulates the DHCP reply message into a Packet _ out message and returns the Packet _ out message to the OpenFlowSwitchA, and designates port2 of the OpenFlowSwitchA to send the Packet _ in message out. Meanwhile, the controller issues a third flow table to openflowswitch a: the IP address with the matching item as the target is an ARP message of an OpenflowSwitchB in-band management IP, and the action items are as follows: designating the output port as port2; issuing a fourth flow table: the IP address with the matching item as the target is an IP message of an OpenflowSwitchB in-band management IP, and the action items are as follows: the output port is designated port2.

After receiving the Packet _ out message, the OpenFlowSwitchA sends the Packet _ out message to a CPU (Central processing Unit) through a Table-miss flow Table for decapsulation to obtain a DHCP reply message, and determines that an output port is port2. And forwarding the DHCP reply message to the OpenflowSwitchB through the port2.

After receiving the DHCP reply message, the OpenflowSwitchB acquires the controller IP address and the in-band management IP address of the local machine from the DHCP reply message, takes a port for receiving the DHCP reply message as an uplink port, and configures a first flow table and a second flow table based on the controller IP address and the uplink port.

The OpenflowSwitchB forwards an ARP request message and a TCP connection message initiated by the IP address of the controller to the OpenflowSwitchA through the first flow table and the second flow table of the OpenflowSwitchB respectively, and forwards the ARP request message and the TCP connection message to the controller through the first flow table and the second flow table of the OpenflowSwitchA.

The ARP message and the TCP connection message returned by the controller are sent to the openflowswitch a, and are forwarded to the openflowswitch b through the third flow table and the fourth flow table of the openflowswitch a, respectively.

The OpenflowSwitchB sends the ARP message and the TCP connection message returned by the controller to the CPU through a Table-miss flow Table to be processed by a protocol stack, and an in-band communication channel between the OpenflowSwitchB and the controller is established.

Example four

Fig. 7 is a schematic structural diagram of an inband management connection apparatus for a switch according to a fourth embodiment of the present invention. As shown in fig. 7, the apparatus is applied to an OpenFlow switch, and includes:

a sending module 710, configured to send a DHCP request message;

the receiving configuration module 720 is configured to receive a DHCP reply message returned by the controller, acquire a local in-band management IP address, a controller IP address, and an uplink port according to the DHCP reply message, and configure an OpenFlow flow table pointing to the controller based on the controller IP address and the uplink port;

the establishing module 730 is configured to forward a first packet initiated by an IP address of the controller and having a source IP address as the in-band management IP address of the local machine to the controller through the OpenFlow flow table, receive a second packet replied by the controller, and establish an in-band communication channel between the local machine and the controller.

The technical scheme of the embodiment of the invention is applied to an OpenFlow switch, and is characterized in that a DHCP reply message returned by a controller aiming at a DHCP request message of the local machine is received, an in-band management IP address configured for the local machine by the controller, an IP address of the controller and an uplink port are obtained according to the DHCP reply message, and an OpenFlow flow table pointing to the controller is initialized and configured based on the IP address of the controller and the uplink port; the method comprises the steps of forwarding a first message which is initiated by an IP address aiming at a controller and has a source IP address as the local in-band management IP address to the controller through inquiring an OpenFlow flow table, receiving a second message replied by the controller, and establishing an in-band communication channel between the local and the controller, so that the problems of high complexity and high network maintenance cost of realizing in-band management of the conventional OpenFlow switch are solved, the OpenFlow flow table is initialized and configured according to an analysis result of a DHCP reply message fed back to the controller, the in-band communication channel between the local and the controller is opened according to the OpenFlow flow table, resources consumed by network maintenance are reduced, and the realization difficulty of in-band management of the OpenFlow switch is reduced.

Optionally, the receiving configuration module 720 is configured to:

taking the port receiving the DHCP reply message as an uplink port;

wherein, in the first flow table, the matching entry is: the target IP address is an ARP message of the controller IP address, and the action items are as follows: designating the output port as an uplink port;

Optionally, the method further includes: an indirect connection establishing module comprising:

the first forwarding unit is used for forwarding a DHCP request message to the controller through a second flow table if the DHCP request message sent by a downstream switch directly connected with the local machine is received after the in-band communication channel between the local machine and the controller is established;

and the second forwarding unit is configured to forward the DHCP reply message returned by the controller to the downstream switch through a port that receives the DHCP request message of the downstream switch, so that the downstream switch configures an OpenFlow flow table pointing to the controller according to the DHCP reply message.

Optionally, the first forwarding unit is configured to:

if a DHCP request message sent by a downstream switch directly connected with the local machine is received, uploading the DHCP request message to a CPU through a Table-miss flow Table and packaging the DHCP request message into a third message; the third packet includes: the local machine receives a port of a DHCP request message of the downstream switch;

Optionally, the second forwarding unit is configured to:

receiving a fourth message returned by the controller;

Optionally, the indirect connection establishing module is further configured to: after the port receiving the DHCP request message of the downstream switch forwards the DHCP reply message returned by the controller to the downstream switch so that the downstream switch configures an OpenFlow flow table pointing to the controller according to the DHCP reply message,

receiving a third flow table and a fourth flow table issued by the controller;

wherein, in the third flow table, the matching entry is: the target IP address is an ARP message of an in-band management IP address of a downstream switch directly connected with the local machine, and the action items are as follows: the appointed output port is a port for receiving the DHCP request message of the downstream switch;

in the fourth flow table, the matching entry is: the target IP address is an IP message of an in-band management IP address of a downstream switch directly connected with the local machine, and the action items are as follows: and the appointed output port is a port for receiving the DHCP request message of the downstream switch.

Optionally, the indirect connection establishing module is further configured to: after the third flow table and the fourth flow table issued by the controller are received,

The switch in-band management connection device provided by the embodiment of the invention can execute the switch in-band management connection method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

EXAMPLE five

Fig. 8 shows a schematic structural diagram of an electronic device 10, that is, a schematic structural diagram of an OpenFlow switch, which can be used to implement an embodiment of the present invention. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 8, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM13, various programs and data necessary for the operation of the electronic apparatus 10 may also be stored. The processor 11, the ROM12, and the RAM13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to the bus 14.

A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. Processor 11 performs the various methods and processes described above, such as the switch inband management connection method.

In some embodiments, the switch in-band management connection method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM12 and/or the communication unit 19. When the computer program is loaded into RAM13 and executed by processor 11, one or more steps of the switch in-band management connection method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the switch in-band management connection method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user may provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the Internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.

It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired result of the technical solution of the present invention can be achieved.

The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for managing and connecting in a switch band is applied to an OpenFlow switch and comprises the following steps:

sending a Dynamic Host Configuration Protocol (DHCP) request message;

receiving a DHCP reply message returned by a controller, acquiring an in-band management IP address, a controller IP address and an uplink port of a local machine according to the DHCP reply message, and configuring an OpenFlow flow table pointing to the controller on the basis of the controller IP address and the uplink port;

2. The method of claim 1, wherein the obtaining a local in-band management IP address, a controller IP address, and an uplink port according to the DHCP reply packet, and configuring an OpenFlow flow table pointing to a controller based on the controller IP address and the uplink port comprises:

sending the DHCP reply message to a CPU for processing through a Table-miss flow Table to obtain a controller IP address and a local in-band management IP address;

taking a port for receiving the DHCP reply message as an uplink port;

wherein, in the first flow table, a matching entry is: the destination IP address is an ARP message of the IP address of the controller, and the action items are as follows: designating the output port as an uplink port;

3. The method of claim 2, after said establishing an in-band communication channel between the local machine and the controller, further comprising:

4. The method according to claim 3, wherein if a DHCP request message sent by a downstream switch directly connected to the local computer is received, forwarding the DHCP request message to a controller through a second flow table, comprising:

if a DHCP request message sent by a downstream switch directly connected with the local machine is received, the DHCP request message is uploaded to a CPU through a Table-miss flow Table and encapsulated into a third message; the third packet includes: the local machine receives a port of the DHCP request message of the downstream switch;

and querying the second flow table, and forwarding the third message to a controller through the uplink port.

5. The method according to claim 3, wherein forwarding, to the downstream switch, a DHCP reply message returned by the controller through a port that receives the DHCP request message of the downstream switch, so that the downstream switch configures an OpenFlow flow table that points to a controller according to the DHCP reply message, includes:

receiving a fourth message returned by the controller;

6. The method according to claim 3, wherein after forwarding, by the port that receives the DHCP request message from the downstream switch, the DHCP reply message returned by the controller to the downstream switch, so that the downstream switch configures an OpenFlow flow table that points to the controller according to the DHCP reply message, the method further includes:

receiving a third flow table and a fourth flow table issued by the controller;

7. The method of claim 6, further comprising, after said receiving the third flow table and the fourth flow table sent by the controller:

and if an IP message sent by a downstream switch directly connected with the local machine is received, forwarding the IP message to the controller by inquiring the second flow table, and forwarding an IP reply message returned by the controller to the downstream switch by inquiring the fourth flow table so as to establish an in-band communication channel between the downstream switch and the controller.

8. An in-band management connection device for a switch, which is applied to an OpenFlow switch, includes:

the sending module is used for sending a DHCP request message;

the system comprises a receiving configuration module, a control module and a control module, wherein the receiving configuration module is used for receiving a DHCP reply message returned by a controller, acquiring an in-band management IP address, a controller IP address and an uplink port of a local machine according to the DHCP reply message, and configuring an OpenFlow flow table pointing to the controller based on the controller IP address and the uplink port;

9. An OpenFlow switch, wherein the OpenFlow switch comprises:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the switch inband management connection method of any of claims 1-7.

10. A computer-readable storage medium storing computer instructions for causing a processor to perform the method for managing connections in-band to a switch as claimed in any one of claims 1 to 7 when executed.