WO2018103019A1 - Method for managing route in software-defined networking and switch - Google Patents

Abstract

Disclosed by the embodiments of the present invention is a method for managing route in software-defined networking, comprising: a top-of-rack (TOR) switch of a rack in a data center acquires route management information of all switches in a managed rack, creates a logical switch according to the acquired route management information, maps the acquired route management information of the switch in the rack to route management information of the logical switch, and sends the route management information of the logical switch to a controller so that the controller manages route according to the route management information of the logical switch. Since the TOR switch maps all switches in a rack into one logical switch, the complexity and scale of network topology visible at a controller level are reduced, and the controller makes a route decision for the logical switch, which accelerates the controller in calculating the speed of a data flow forwarding path, thereby improving communication performance of an entire system.

Description

Method and switch for route management in software defined network Technical field

Embodiments of the present invention relate to the field of communications, and in particular, to a method and a switch for routing management in a software-defined network.

Background technique

The basic idea of Software-Defined Networking (SDN) is to achieve separation of the data forwarding layer and the control layer. The data forwarding layer is responsible for data forwarding, and the control layer implements control functions for data forwarding.

The OpenFlow (OpenFlow) network is a software-defined network proposed by Stanford University in 2007. It supports users to control network processing behavior through an open flow table. The OpenFlow switch (Switch) is one of the core components of the entire OpenFlow network and is responsible for data forwarding. After receiving the data packet, the OpenFlow switch first searches the local flow table (FlowTable) for matching the existing flow entry (FlowEntry). If there is no match, the packet is forwarded to the controller (Controller). The device determines the forwarding rule, and delivers the forwarding rule for the data packet. The switch adds a new flow entry to the flow table according to the forwarding rule. The Controller is also one of the core components of the entire OpenFlow network, and is primarily responsible for data forwarding decisions. The Controller controls (adds, deletes, modifies, etc.) the flow table in the OpenFlow switch through the standard interface of the OpenFlow protocol, thereby implementing centralized control of the entire network. The controller determines that the forwarding path of the data stream needs to acquire topology information of the entire SDN network, and the topology information is formed by the switches being connected to each other.

More and more SDN networks are used in the data center computer room. In the actual application of the data center, each server generally installs virtualization software and runs multiple virtual machines (VMs). This virtualization software includes not only host virtualization software but also network virtualization software. The server forms a virtual switch through virtualization software and connects the virtual machine to the virtual switch.

With the expansion of the entire data center and the application of virtual switch technology, the network scale of the data center is increasing, the topology complexity is greatly increased, and the controller calculates according to the complex network topology. The forwarding path of the communication data flow between the hosts is slowed down, and the increase of the decision time of the forwarding path by the controller causes the speed of the data flow forwarding process to be reduced, thereby greatly reducing the communication efficiency of the entire network. In severe cases, if a large number of new data streams need to be forwarded, the decision speed of the controller is slow due to the complicated network topology, which may lead to communication failure.

Summary of the invention

In view of this, the embodiment of the present invention provides a method and a switch for routing management in an SDN network, which reduces the complexity of the network topology obtained by the controller, improves the speed of the controller to determine the forwarding path of the data stream, and greatly improves the communication of the network. effectiveness.

In a first aspect, the present application provides a method for routing management in a software-defined network, which is applied to a data center, including: a rack TOR switch in a data center collects routing management information of all switches in a managed rack, and performs route management. The information includes the device identification information, the port information, and the topology information of the connection between the devices. The TOR switch creates a logical switch according to the collected routing management information, and maps the collected routing management information of the intra-rack switch to the routing management information of the logical switch. The TOR switch sends the routing management information of the logical switch to the controller, so that the controller performs route management according to the routing management information of the logical switch.

It can be understood that all the switches in the rack include the TOR switch itself. Generally, the switches other than the TOR switch are virtual switches in the data center, which are often large. With the above method, the TOR switch maps all the switches in the rack into one logical switch, and the controller makes routing decisions for the logical switch, which reduces the complexity and scale of the network topology visible at the controller level, thereby speeding up the controller. Calculate the speed of the data stream forwarding path and improve the communication performance of the entire system.

Further, the TOR switch serves as a communication message conversion device between the switch and the controller in the rack, and the TOR switch sends a message including the switch itself information to the switch in the rack according to the correspondence between the switch in the rack and the logical switch. A message converted to include logical switch information is sent to the controller, and a message sent by the controller to convert the message including the logical switch into the information of the corresponding intra-rack switch is sent to the corresponding switch.

In a possible implementation, the TOR switch receives the first transmission sent by the first switch in the rack. Reporting, the first report message is a message sent by the first switch to the controller; the TOR switch converts the information of the first switch in the first report message into the information according to the mapping relationship between the first switch and the logical switch The corresponding information of the logical switch is generated, and a second report message is generated and sent to the controller. The TOR switch implements the conversion and forwarding of messages sent by the switches in the rack to messages submitted to the controller.

In another possible implementation, the TOR switch receives a first sent message sent by the controller, where the first sent message is a message sent by the controller to the logical switch; the TOR switch is based on an intra-rack switch and The mapping of the logical switch converts the information of the logical switch in the first sent message to the corresponding information of the destination switch, and generates a second sent message to be sent to the destination switch. The TOR switch implements the conversion and forwarding of messages sent by the controller to the logical switch to the switches in the rack.

In another possible implementation, the TOR switch receives the first sent message sent by the controller, where the first sent message is a message sent by the controller to the logical switch; and the TOR switch is mapped according to the switch and the logical switch in the rack. The relationship and the topology information of the connection between the switches in the rack convert the information of the logical switch in the first sent message into the corresponding information of the destination switch, and generate a second sent message to be sent to the destination switch. The TOR switch implements the conversion and forwarding of messages sent by the controller to the logical switch to the switches in the rack.

It can be understood that the first issued message sent by the controller, the TOR switch may generate multiple pieces of the first issued message according to the mapping relationship between the switch and the logical switch in the rack and the topology information of the connection between the switches in the rack. And sending, by the second sending message, the generated second sending message to the corresponding destination switch, so that the destination switches cooperate with the processing of the data stream according to the indication of the second sending message.

In another possible implementation, the TOR switch further receives a first data flow forwarding rule request message sent by the second switch in the rack, where the first data flow forwarding rule request message is used to request the second switch from the controller. The forwarding rule of the received new data stream; the TOR switch converts the port of the second switch in the first data flow forwarding rule request message into the corresponding port of the logical switch according to the mapping relationship between the switch and the logical switch in the rack, and will be the first The buffer identifier in the second switch in the data flow forwarding rule request message is converted into a buffer identifier in the corresponding logical switch, and a second data flow forwarding rule request message is generated and sent to the controller; the TOR switch receives the controller The first flow table processing message is sent, the first flow table processing message includes a processing rule of the logical switch for the new data flow, and is a response to the first data flow forwarding rule request message; the TOR switch processes the message according to the first flow table, and is in the rack The mapping between the switch and the logical switch, and the topology information of the connection between the switches in the rack, generate a second flow table processing message and send the message to the switch corresponding to the second flow table processing message, so that the corresponding switch processes according to the second flow table. The message processes the new data stream.

It can be understood that, in the foregoing implementation, the TOR switch converts the data flow forwarding rule request message sent by the switch in the rack into a message for the logical switch, and the controller performs routing planning and issuance for the logical switch. The flow table processes the message, and the TOR switch converts the flow table processing message for the logical switch into a message for the intra-rack switch, and reduces the complexity and scale of the network topology visible at the controller level, and targets the new data in the SDN network. The process of streaming request forwarding routing rules speeds up the calculation of the data flow forwarding path by the controller and improves the communication performance of the entire system.

In another possible implementation, the TOR switch also collects routing capability information of all switches in the managed rack, the routing capability information includes information about matching domains, commands, and actions supported by the flow table; The routing capability information determines the flow table configured by the logical switch and the routing capability information; the TOR switch sends the flow table configured by the logical switch and the routing capability information to the controller, so that the controller performs route management according to the routing management information of the logical switch.

It can be understood that the TOR switch determines the flow table configured by the logical switch and the routing capability information according to the routing capability information of all the switches in the rack, so that the controller performs route management according to the routing management information of the logical switch. In general, the routing information of the virtual switch in the cabinet in the data center is the same. In this case, the TOR switch can directly determine the routing capability information of the logical switch according to the routing capability information of the TOR and the common routing capability information of the virtual switch.

In a second aspect, the embodiment of the present invention provides a rack TOR switch, which is applied to a data center, and includes: a collecting unit, configured to collect routing management information of all switches in a rack managed by the TOR switch, and the routing management information The device includes: device identification information, port information, and topology information of the connection between the devices; the information mapping unit is configured to create a logical switch according to the collected routing management information, and map the collected routing management information of the intra-rack switch to the routing of the logical switch. The management unit sends a routing management information of the logical switch to the controller, so that the controller performs route management according to the routing management information of the logical switch.

The TOR switch collection unit collects the routing management information of the switches in the rack, and maps all the switches in the rack into one logical switch. The controller makes routing decisions for the logical switch, thereby mapping multiple switches connected in the rack to An overall logical switch approach is presented to the controller, reducing the complexity and scale of the network topology at the controller level, thereby speeding up the controller to calculate the data flow forwarding path and improving the communication performance of the entire system.

In a possible implementation, the TOR switch further includes: a receiving unit, configured to receive a first report message sent by the first switch in the rack, where the first report message is a message sent by the first switch to the controller; The unit is configured to convert the information of the first switch in the first report message to the corresponding information of the logical switch according to the mapping relationship between the first switch and the logical switch, to generate a second report message, where the sending unit is further configured to send the second report A message is sent to the controller. The TOR switch implements the conversion and forwarding of messages sent by the switches in the rack to messages submitted to the controller.

In another possible implementation, the receiving unit is further configured to receive, by the controller, a first sent message, where the first sent message is a message sent by the controller to the logical switch; and the message converting unit is further configured to be used according to the machine The mapping between the in-rack switch and the logical switch converts the information of the logical switch in the first sent message into the corresponding information of the destination switch to generate a second sent message; the sending unit is further configured to send the second sent message to the destination switch. The TOR switch implements the conversion and forwarding of messages sent by the controller to the logical switch to the switches in the rack.

In another possible implementation, the receiving unit is further configured to receive, by the controller, a first sent message, where the first sent message is a message sent by the controller to the logical switch, and the message converting unit is further configured to be used according to the machine The mapping relationship between the in-rack switch and the logical switch and the topology information of the inter-switch connection in the rack, converting the information of the logical switch in the first sent message into the corresponding information of the destination switch, generating a second sending message; It is used to send a second sent message to the destination switch. The TOR switch implements the conversion and forwarding of messages sent by the controller to the logical switch to the switches in the rack.

It can be understood that, for the first issued message sent by the controller, the message conversion unit may generate a first sent message according to the mapping relationship between the switch and the logical switch in the rack and the topology information of the connection between the switches in the rack. The plurality of second sending messages are sent, so that the destination switch corresponding to the second sending message cooperates with the processing of the data flow according to the indication of the second sending message.

In another possible implementation, the receiving unit is further configured to receive the second switch in the rack. Sending a first data flow forwarding rule request message, the first data flow forwarding rule request message is used to request a forwarding rule for the new data flow received by the second switch from the controller, and the first flow table processing message sent by the receiving controller The first flow table processing message includes a processing rule of the logical switch to the new data flow; the message conversion unit is further configured to: according to the mapping relationship between the switch and the logical switch in the rack, forward the first data flow to the second switch in the rule request message The port is converted into a corresponding port of the logical switch, and the buffer identifier in the second switch in the first data flow forwarding rule request message is converted into a buffer identifier in the corresponding logical switch, and a second data flow forwarding rule request message is generated, and The second flow table processing message is generated according to the first flow table processing message, the mapping relationship between the switch and the logical switch in the rack, and the topology information of the connection between the switches in the rack; the sending unit is further configured to send the second data flow forwarding rule request Sending a message to the controller, and sending a second flow table processing message to the second flow table The switch corresponding to the message is processed, so that the corresponding switch processes the message to process the new data stream according to the second flow table.

It can be understood that, in the foregoing implementation, the TOR switch converts the data flow forwarding rule request message sent by the switch in the rack into a message for the logical switch, and the controller performs routing planning and issuance for the logical switch. The flow table processes the message, and the TOR switch converts the flow table processing message for the logical switch into a message for the intra-rack switch, and reduces the complexity and scale of the network topology visible at the controller level, and targets the new data in the SDN network. The process of streaming request forwarding routing rules speeds up the calculation of the data flow forwarding path by the controller and improves the communication performance of the entire system.

In another possible implementation, the collecting unit is further configured to collect routing capability information of all switches in the managed rack, and the routing capability information includes information about matching fields, commands, and actions supported by the flow table; and the message mapping unit. And the method further includes: determining, according to the collected routing capability information, a flow table configured by the logical switch and routing capability information; the sending unit is further configured to send the flow table configured by the logical switch and the routing capability information to the controller, so that the controller is configured according to the Route management information of the logical switch is used for route management.

It can be understood that the TOR switch determines the flow table configured by the logical switch and the routing capability information according to the routing capability information of all the switches in the rack, so that the controller performs route management according to the routing management information of the logical switch. In general, the routing information of the virtual switch in the cabinet in the data center is the same. In this case, the TOR switch can also directly use the routing information of the TOR itself. The common routing capability information of the force information and the virtual switch determines the routing capability information of the logical switch.

In a third aspect, an embodiment of the present invention provides a TOR switch, including: a processor, a memory, a bus, and a communication port; a memory for storing a computer to execute an instruction, a processor and a memory connected by a bus, and a communication port for using the controller The computer is in communication with the switch in the rack managed by the TOR switch, and the processor executes the memory stored computer to execute the instructions to perform the method of the first aspect above.

In a fourth aspect, an embodiment of the present invention provides a program product, the program product comprising instructions, when the program product is executed by a computer, causing the computer to perform the method of the first aspect.

Through the above solution, the method for routing management in a software-defined network provided by the embodiment of the present invention, the rack switch maps all switches in the rack into a logical switch and presents the controller to the controller, and the controller performs routing decision for the logical switch. The switch completes the message mapping between the intra-rack switch and the logical switch, which reduces the complexity and scale of the network topology visible at the controller level, thereby speeding up the controller to calculate the data flow forwarding path and improving the overall system. Communication performance.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

1 is a schematic diagram of deployment of a data center network in a ToR mode according to an embodiment of the present invention;

2 is a network topology diagram corresponding to FIG. 1 acquired by a controller;

3 is a network topology diagram of the virtual switch including FIG. 1 acquired by the controller;

4 is a schematic diagram of a network configuration of a cabinet in a data center according to an embodiment of the present invention;

5 is a schematic diagram of a logical switch configuration of a data center according to an embodiment of the present invention;

6 is a flow chart of a method for routing management in an SDN network;

7 is a flow chart of a method for requesting forwarding routing rules in an SDN network;

8 is a schematic structural diagram of a TOR switch;

FIG. 9 is a schematic structural diagram of another TOR switch.

detailed description

The technical solutions in the embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention.

In the switching network design of the data center, according to the different placement positions of the switch, there are generally several network architecture design methods: Top of Rack (TOR) mode, End Of Rack (EOR) mode, and column. (Middle of Row, MoR) way. The traditional network architecture of the equipment room is mainly based on EoR and MoR (the difference between the two is mainly due to the location of the network cabinet), and similar centralized wiring is adopted. The EoR mode refers to all the server ports in the server cabinet, which are connected to the distribution frame on the cabinet through jumpers, and then extend the cables on the distribution frame to the network cabinets located at the rear of the group of cabinets. On the switch. The MoR mode is similar to the EoR mode. The network cabinet is deployed in the middle of the server cabinet, which reduces the cable distance from the server cabinet to the network cabinet to a certain extent. The emergence of the ToR method has brought about new changes to the architecture of the computer room: this method places the access switch on the top of each server cabinet or unit, and the server in the cabinet is directly connected to the top switch through a short jumper. Connected to the core switch from the uplink port of the switch via fiber optics. Roughly speaking, the ToR and EoR/MoR methods only change the location of the access switch, but actually change the network structure of the entire computer room. The integrated cabling system has changed from the centralized cabling to the point-to-point cabling, which simplifies cable management and is highly scalable. When new cabinets and service servers are added, the server can be directly connected to the ToR. The new data center is increasingly adopting the ToR approach, and under the tide of cloud computing, this distributed architecture has strong business scalability and requires more and more servers. The sheer volume of servers requires that data center cabinet space be fully utilized, while massive amounts of business data also need to pass data to the core of the network through faster, more direct, high-performance links. Under such a trend, it is obvious that ToR is more applicable. Under the pressure of rapid business expansion, the ToR approach can better realize the faster expansion of the network. Figure 1 is a schematic diagram of a typical ToR-based data center network deployment.

The SDN network is mainly divided into two parts, a controller that is at the control level and that is the forwarding control core, and a switch that forwards data according to the control instructions issued by the controller on the data plane. The controller calculates the forwarding path of the data stream and needs to obtain the topology information of the entire SDN network, for the number shown in FIG. According to the network deployment diagram of the center, the controller can obtain the topology diagram of FIG. 2 by using a certain method.

In general, in the actual application of the data center, it is impossible for each server to run only one instance. Generally, virtualization software is installed on the physical device, and multiple virtual machine instances are run. This virtualization software includes not only host virtualization software, but also network virtualization software (forming a virtual switch that connects virtual machine instances to virtual switches). After the virtualization software is installed, the topology corresponding to the data center network environment shown in Figure 1 is further expanded, as shown in Figure 3. From the changes in Figure 2 to Figure 3, when the network size of one cabinet in the data center becomes larger, it means that the topology seen by the controller will increase, and the complexity of the topology also increases, and the direct impact is The complexity of the controller for data stream forwarding path calculation is improved, and the controller decision time becomes longer. It is foreseeable that as the size of the entire data center expands, the network scale is also increasing. The controller calculates the forwarding path of the communication data flow between hosts to be slower and slower, which directly leads to the speed of the data flow forwarding process. It will also reduce, and the communication efficiency of the entire network is greatly reduced. Even if a large number of new data streams with a sudden increase in the need to decide the forwarding path, the controller may be slower due to the complexity of the topology, and eventually the communication establishment fails.

The embodiment of the invention provides a method for routing management in an SDN network, which reduces the network topology presented on the controller by hiding the local detailed network topology of the data center, thereby reducing the controller decision pressure and improving the network forwarding performance. . For convenience of description, the SDN in the embodiment of the present invention is described by using an OpenFlow network as an example. In the embodiment, the virtual switch connected to the TOR switch uses only a small number of virtual switches as an example, and does not affect the protection scope of the present invention. FIG. 4 is a schematic diagram showing the network configuration of the data center in the cabinet shown in Embodiment 1 of the present invention. The TOR switch 102 serves as an aggregation switch of the virtual switches 103 and 104 connected below, and the virtual switch 1 and the virtual switch 2 are both associated with The TOR switch establishes an OpenFlow connection and connects to the host and the data port 1-4 of the TOR switch through its own data port 1-4. The data port 1-4 here is the virtual port created by the virtual switch. A host is a virtual host. The virtual port is directly connected to the network port corresponding to the virtual host. The data port 2 of the virtual switch 1 is connected to the host A, the data port 3 is connected to the data port 2 of the TOR switch, the data port 4 of the virtual switch 2 is connected to the host B, and the data port 3 is connected to the data port 4 of the TOR switch. Of course, the TOR switch and the controller are not directly connected to each other, and other switches are also used in the middle. For the sake of simplicity, the switch between the two is not shown in the embodiment of the present invention. In addition, TOR switches and virtual switching Both the machine 1 and the virtual switch 2 establish an OpenFlow connection with the controller 101 through the management port 5 for OpenFlow management. As with the conventional network, the management ports 5 of the three switches are generally connected to a switch on a control plane to establish a connection with the controller 101. Since there is little relationship with the present invention, there is no switch indicating the control plane. According to the prior art, the controller 101 acquires a network topology diagram including the TOR switch 102 and each virtual switch 103. Obviously, if a large number of virtual switches 103 are included in the rack, if the virtual switch 103 is directly controlled by the controller 101 according to the existing manner, the obtained network topology map includes a large number of virtual switch information and Complex port connection relationships result in higher computational data flow forwarding paths and longer routing decisions. Even when a large number of new data streams with a sudden increase require a decision forwarding path, the controller 101 may be slow in decision-making due to the complexity of the topology, and eventually the communication establishment failure may occur.

If the TOR switch acts as a proxy for all other SDN switches in the rack, the TOR switch establishes an OpenFlow connection with the controller, and all other OpenFlow virtual switches in the rack establish an OpenFlow connection with the TOR switch instead of establishing an OpenFlow connection directly with the controller. In this way, the TOR switch itself and all other virtual switches in the rack with which OpenFlow is connected constitute an administrative domain. For all other OpenFlow switches in the rack that are connected to the TOR switch, the TOR switches appear as their controllers, providing the controller's functionality. For the controller, the TOR switch itself and all other virtual switches in the rack form a logical switch.

First, the control program of the TOR switch collects its own identification information, port information, and interconnected topology information of itself and all other virtual switches in the rack, and obtains the information shown in Table 1 below:

Equipment Identity Original port TOR switch 0000000000000001 1, 2, 3, 4 Virtual switch 1 0000000000000002 1, 2, 3, 4 Virtual switch 2 0000000000000003 1, 2, 3, 4

Table 1

The control program of the TOR switch creates a new logical switch, which is not a real switch. The TOR switch will collect the port information of all other virtual switches and its own port information, and exclude the port information for the topology connection in the management domain as the new logic. The port of the switch uniformly allocates the port number and saves the mapping table between the original switch port information and the new logical switch port information. For example, the port number 1-4 of each of the TOR switch, the virtual switch 1, and the virtual switch 2 is mapped to the port number 1-8 of the logical switch (the table is identified by a logical port number for easy distinction). As follows:

Table 2

Secondly, the TOR switch collects flow table, instruction (Action), action (Action) information of each virtual switch in the management domain, and analyzes the flow table information of all switches (including itself) in the management domain to obtain management. The common information that can be used by all switches in the domain to serve as the flow table, command, and action information of the logical switch. For example, suppose the matching domain supported by flow table 0 of virtual switch 1 is: input port (In_Port), virtual local area network identifier (VLAN ID), destination media access control address (Dst Mac), source media access control address (Src Mac) ), the destination IP address (Dst IP), and the flow table 0 of the TOR switch only supports the following matching fields: input port (In_Port), virtual local area network identifier (VLAN ID), destination media access control address (Dst Mac), then TOR After the switch is analyzed, the common matching domain supported by the flow table 0 of the two switches is selected as the matching domain information supported by the logical switch flow table, that is, the input port (In_Port), the virtual local area network identifier (VLAN ID), and the destination media access. Control address (Dst Mac). For command information, action information, etc., the TOR switch will analyze and take public information as a logical exchange. Information about the machine. Of course, in general, the virtual switches in the cabinet use all-matched matching domain flow tables (that is, each flow table contains all matching domains), and the supported command information and action information are also identical. At this time, the TOR switch can determine the flow table, the command, and the action information of the logical switch according to its own information and the common information supported by all the virtual switches in the management domain. In general, the matching fields, commands, and actions supported by each OpenFlow switch are the same. However, the sequence of the flow table may be different and the matching fields supported by the flow table in different order are inconsistent. Flow table, instructions, and action information.

When the controller sends a query command to the TOR switch for querying port information, flow table information, command information, and action information, the TOR switch collects and converts the corresponding information representing the unified logical switch and returns it to the controller. At this point, as shown in FIG. 5, the network information in the entire cabinet is mapped to a logical switch by the TOR switch, and the port 2 of the original virtual switch 1 is connected to the host A, and the port 4 of the logical switch is connected to the host A. The port 4 of the original virtual switch 2 is connected to the host B. The port 8 of the logical switch is connected to the host B. The port 3 of the original virtual switch 1 is connected to the port 2 of the TOR switch, and the port 7 of the logical switch is connected to the port 2.

According to the provisions of the OpenFlow protocol, when a new data flow arrives at a virtual switch, such as virtual switch A, it needs to be forwarded. After the virtual switch A parses the data packet, it queries the forwarding flow table stored by itself. If there is no matching forwarding flow entry. Then, the data flow forwarding rule request message (here, Packet_in) message specified by the OpenFlow protocol is sent to the controller through the control management channel to request a forwarding rule for the data flow. At this time, the TOR switch acts as a controller agent. After receiving the data flow forwarding rule request message Packet_in message reported by a virtual switch, the TOR switch needs to send this message because the controller actually makes the forwarding decision. Reported to the controller, it needs to be converted before the report, convert the information of the actual switch in the message to the information about the logical switch it represents, and save the original data stream forwarding rule request message and the converted data stream forwarding rule request message. The mapping relationship between related information. If the new data stream is forwarded from the host A to the host B, the virtual switch 1 does not match the forwarding flow entry, and the data flow forwarding rule request message is reported to the TOR switch according to the protocol standard. Assume that the parameters carried in the Packet_in message are: a buffer identifier (Buffer id indicating the identifier of the buffer space of the data stream on the switch 1), and matching domain information of the data stream. Here Suppose the Buffer id is 2 and the matching field is In Port, which is port 2. According to the mapping relationship between the original switch and the logical switch, port 2 of the virtual switch should be converted to port 4 of the logical switch, and the Buffer ID on the logical switch is allocated by the proxy control program of the TOR switch, and the Buffer ID is on the logical switch. Globally unique. Some key information in the Packet_in message converted by the TOR switch is shown in the following table:

Original value Newly assigned value Buffer ID 2 10 In Port 2 4

table 3

The proxy control program of the TOR switch reports the modified data flow forwarding rule request message Packet_in message to the controller.

After receiving the data flow forwarding rule request message Packet_in message reported by the TOR switch, the controller calculates the forwarding path, and sends a flow table processing message (here, Flow_Mod) of the forwarding data flow to the logical switch represented by the TOR switch according to the protocol. . The Flow_mod message sent by the controller mainly contains the following key information: Buffer ID, matching field, flow table identifier (Table ID), Instruction, or Action. Because the proxy control program of the TOR switch converts the Packet in message reported by the actual virtual switch into the Packet in message reported by the logical switch, the Flow_mod message responded by the controller is also for the logical switch, and the proxy control program of the TOR switch receives the control from the control. After the Flow_mod message of the device, the Flow_mod message for the logical switch is converted into a series of Flow_mod messages for the actual switch and delivered to the actual multiple switches according to the mapping relationship between the virtual switch and the logical switch. Assume that the controller returns the Flow_mod message for the previous Packet_in message, as shown in the following table s:

Table 4

That is, the Buffer ID issued by the logical switch represented by the previously received TOR switch is 10 Packet_in message is added in the flow table of Table 1d of the logical switch: the matching domain is 4 for the ingress port, the source Mac address is equal to the Mac address of the host A, the destination Mac address is equal to the Mac address of the host B, and the command is the port. 8 The flow entry to be sent, so that the logical switch processes the newly received data flow according to the flow table.

After receiving the Flow_mod message sent by the controller for the logical switch, the proxy control program of the TOR switch will follow the mapping relationship between the actual switch and the logical switch recorded locally and the collected network topology information in the management domain. The flow entry of the logical switch is translated to the actual switch and sent to the actual switch. The conversion method is not the focus of this aspect and will not be described here.

After the TOR switch is converted, the information about the Flow_mod message sent to the virtual switch 1 is:

table 5

That is, the virtual switch 1 needs to send the Packet_in message with the BufferID of 2 sent by the virtual switch 1 received by the front TOR switch to the flow table of Table Id 01: the matching domain is the ingress port 2, and the source Mac address is equal to the host A. The Mac address and the destination Mac address are equal to the MAC address of the host B, and the command is a flow entry sent by the port 3, so that the virtual switch 1 processes the newly received data stream sent by the host A according to the flow table, and sends the data stream sent by the port A. Give the TOR switch. The Buffer ID is determined by the mapping relationship of the Buffer ID recorded by the TOR switch. The information of the port is determined by the mapping relationship between the actual switch and the logical switch maintained by the TOR switch and the topology information.

The information of the Flow_mod message sent to the TOR switch itself is:

Table 6

That is, the TOR switch needs to be added in the flow table with Table Id 01: the matching domain is the ingress port 2, the source Mac address is equal to the Mac address of the host A, the destination Mac address is equal to the Mac address of the host B, and the command is performed by the port 4. The flow entry to be sent, so that the TOR switch processes the data stream sent by the port 2 of the virtual switch 1 received from the port 2 according to the flow table, and sends it to the virtual switch 2 via the port 4.

The information of the Flow_mod message sent to the virtual switch 2 is:

Table 7

That is, the virtual switch 2 needs to be added in the flow table with Table Id 01: the matching domain is the ingress port is 3, the source Mac address is equal to the Mac address of the host A, the destination Mac address is equal to the Mac address of the host B, and the command is the port 4 The flow entry to be sent is sent, so that the virtual switch 2 processes the data flow from the host A received by the port 4 of the TOR switch and is sent to the host B via the port 4 according to the flow table.

With the above technical solution, in the method for routing management in the SDN provided by the embodiment of the present invention, the TOR switch maps all the switches in the rack to a logical switch and presents the controller to the controller, and the controller makes routing decisions for the logical switch. The switch completes the route mapping between the intra-rack switch and the logical switch, which reduces the complexity and scale of the network topology visible at the controller level, thereby speeding up the controller to calculate the data flow forwarding path and improving the communication of the entire system. performance.

With reference to the ToR mode data center network described in FIG. 1, the embodiment of the present invention provides a method for routing management in an SDN network, as shown in FIG. 6, the specific process includes:

201. The rack TOR switch in the data center collects routing management information of all switches in the managed rack. The route management information includes device identification information, port information, and topology information of connections between devices. It can be understood that the switches in the rack here can include a switch of a real physical entity, a virtual switch formed by network virtualization software, and of course, the TOR switch itself.

In the SDN network, the controller sends a query command to the managed switch to query the routing management information of the switch. In the embodiment of the present invention, optionally, the TOR switch can also adopt the Ways to collect routing management information for switches other than the ones in the racks it manages, the TOR switch sends controller query commands to the switches in the managed racks, and is similar to the one shown in Table 1 above. Information about each switch.

202. The TOR switch creates a logical switch according to the collected routing management information of each switch in the rack, and establishes a correspondence between the logical switch and the switch in the rack.

The TOR switch creates a virtual logical switch and determines the routing management information of the created logical switch based on the port information of all other switches collected, its own port information, and the connection topology relationship between the switches. In the logical switch, the switch number is assigned to each switch in the rack, and the port number of the original switch is mapped to the port number of the logical switch. The connection relationship between the ports of the logical switch is determined according to the connection topology relationship between the switches. Record the mapping relationship between the switch and the logical switch. Optionally, for a port that has no connection relationship with other devices in the original switch, you can create a port on the logical switch without mapping to reduce the number of ports on the logical switch. The mapping relationship recorded here is mainly the port number corresponding information of the two, and of course, the connection relationship of the port and the corresponding information of the device identifier can also be recorded.

203. The TOR switch sends the routing management information of the logical switch to the controller, so that the controller performs route management according to the routing management information of the logical switch.

The TOR switch sends the routing management information of the created logical switch to the controller. The TOR switch can actively report various types of information about the created logical switch. The routing management information of the logical switch corresponding to the query command is reported to the controller when the query command of the controller is received. After receiving the routing management information of the logical switch sent by the TOR switch, the controller can know the port information and the topology connection relationship of the switch in the rack through the routing management information of the logical switch, perform route management, and determine the forwarding path of the data flow through calculation. .

In the foregoing method embodiment, the TOR switch maps all the switches in the rack into one logical switch, and maps the routing management information between the intra-rack switch and the logical switch, and the controller makes routing decisions for the logical switch. . This method of mapping multiple switches connected in a rack into one overall logical switch can hide part of the local detail network, reducing the complexity and scale of the network topology visible at the controller level, thereby accelerating the controller computing data. The speed of the flow forwarding path improves the communication performance of the entire system.

Further, when the controller performs the calculation of the routing and forwarding rules, in addition to considering the path of the switch In addition to the management information, the routing capability information of the switch, that is, the matching fields, commands, actions, and the like supported by the flow table of the switch are also considered. Therefore, when calculating the routing and forwarding rules for the logical switch, the controller should also consider the routing capability information of the logical switch. Optionally, the TOR switch collects the routing capability information of all the switches in the managed rack, determines the flow table configured by the logical switch, and the routing capability information according to the collected routing capability information; then, the TOR switch configures the logical switch. The flow table and the routing capability information are sent to the controller, so that the controller performs route management according to the routing management information of the logical switch.

In the SDN network, the controller sends a query command to the managed switch for querying the routing capability information of the switch. In the embodiment of the present invention, the TOR switch may also collect the managed device in this manner. The TOR switch sends the query command used by the controller to the switch in the managed rack and obtains the routing capability information reported by each switch. The TOR switch analyzes the routing capability information of all the collected switches (including itself) to determine the flow table and routing capability information configured by the logical switch. Optionally, the TOR switch uses the common information that all switches can use as the flow table, instructions, and action information of the logical switch. For example, the common matching domain supported by the flow table of each switch is selected as the matching domain information supported by the logical switch flow table, and the instruction information and action information supported by the flow table of each switch are selected as the instruction information and actions supported by the logical switch flow table. information.

Generally, in the data center, except for the TOR switch, other switches in the cabinet are virtual switches, and the virtual switch generally adopts a full-match matching domain flow table (that is, each flow table contains all the Matching fields) and the instructions and actions supported by each flow table are also the same. At this time, the TOR switch can determine the flow table, command, and action information of the logical switch according to its own information and the common information supported by other switches in the rack. In general, the matching fields, commands, and actions supported by the OpenFlow switches are the same. The flow table is different in each switch. The matching fields configured in the flow table may be inconsistent. The TOR switch collects the routing capabilities of each switch. After the information is analyzed, the flow table, instructions, and action information of the logical switch can be obtained.

The TOR switch sends the flow table and the routing capability information of the logical switch to the controller. The method can be reported to the controller when the controller receives the query command. After receiving the flow table and route management information of the logical switch sent by the TOR switch, the controller can perform route management based on the information.

The TOR switch maps the switches in the rack to logical switches, establishes the correspondence between the switches in the rack and the logical switches, and reports the related information of the logical switches to the controller. Further, the controller can receive the information according to the The information of the logical switch sent by the TOR switch is routed. The communication between the switch and the controller in the rack is transferred by the TOR switch. The TOR switch converts the message containing the information sent by the switch in the rack into a message according to the correspondence between the switch in the rack and the logical switch. A message containing the logical switch information is sent to the controller, and a message that the controller sends the message including the logical switch to the information of the corresponding intra-rack switch is sent to the corresponding switch.

When the TOR switch receives the first report message of the first switch in the rack, the first report message here is a message sent by the first switch to the controller, and the TOR switch is based on the mapping relationship between the switch and the logical switch in the rack. The information of the first switch in the first report message is converted into the corresponding information of the logical switch, and the second report message is generated and sent to the controller. The second report message is the same type of message as the first report message, and the TOR switch is only information related to the first switch included in the first report message, for example, related information in route management information and routing capability information, such as a port. No. According to the mapping relationship, change the port number of the first switch to the port number corresponding to the logical switch. Other information such as the Buffer id as shown in Table 3 in the previous embodiment may also be included, and the information is included in the mapping relationship between the in-rack switch and the logical switch.

When the TOR switch receives the first sending message of the controller, the first sending message is a message sent by the controller to the logical switch. Because the controller side only knows the information of the logical switch, it does not know the switch in the rack. Specific information, so it only sends messages to the logical switch to implement route management. The TOR switch converts the information of the logical switch in the first sent message into the corresponding information of the destination switch according to the mapping relationship between the switch and the logical switch in the rack, and generates a second sent message to be sent to the destination switch, where the destination switch is followed. Mapping relationship, the real switch in the rack corresponding to the information of the logical switch included in the first delivered message. Of course, although the first outgoing message is a message for the logical switch, since the logical switch is actually a switch mapped by multiple intra-rack switches that the TOR switch is connected and managed, actually the controller is in the rack. The first delivery message, when mapping to the actual destination switch, may require more than one switch to complete the data stream processing function specified by the first delivery message. The TOR switch needs to send a first delivery message. According to the mapping between switches and logical switches in the rack And the topology information of the connection between the switches in the rack, generating more than one second sending message, and sending the generated multiple second sending messages to the corresponding destination switch, so that the destination switches follow the second sending message. Indicates that the processing of the data stream is completed. For example, in a piece of the outgoing message (here, the Flow_mod message) shown in Table 4 in the previous embodiment, the logical switch instructs the logical switch to forward the data stream of the input port 4 out of the outbound port 8, as shown in Table 5, Table 6, and Table 7. As shown, the TOR switch generates three second outgoing messages (also Flow_mod messages) to the virtual switch 1, virtual switch 2, and TOR switch according to the mapping relationship between the switches in the rack and the logical switches. The first delivery message sent by the device to the logical switch is converted and delivered to the second delivery message for the intra-rack switch, and the corresponding route management function is implemented.

As shown in FIG. 7, an embodiment of the present invention provides a method for requesting forwarding of a routing rule in an SDN network. In this embodiment, it is assumed that the controller has acquired the related information of the logical switch, including the routing management information and the routing capability information, and the mapping relationship between the intra-rack switch and the created logical switch has also been established on the TOR switch. The method comprises the following steps:

Step 301: The TOR switch receives a first data flow forwarding rule request message sent by a second switch in the rack, where the first data flow forwarding rule request message is used to request, for forwarding, a new data flow received by the second switch from the controller. rule.

When a new data flow arrives at the second switch, and the second switch does not match the applicable forwarding flow entry in the forwarding flow table or the matching flow entry in the forwarding flow entry is the reporting control The device requests the forwarding rule, and the second switch sends a data stream forwarding rule request message (in the embodiment, generally using Packet_in as an example) message to the controller to request a forwarding rule for the data stream, where the data stream is forwarded for differentiation. The rule request message is defined as the first data flow forwarding rule request message. The “first” and “second” in this document are only used to distinguish different switches or messages, and do not limit the scope of application of the present patent embodiment. As the aggregation switch in the rack, the TOR switch receives the first data flow forwarding rule request message sent by the second switch.

Step 302: The TOR switch converts the port of the second switch in the first data flow forwarding rule request message into a corresponding port of the logical switch according to the mapping relationship between the switch and the logical switch in the rack, and forwards the first data flow to the rule request message. The buffer identifier in the second switch is converted into a buffer identifier in the corresponding logical switch, and a second data flow forwarding rule request message is generated and sent to the controller. Assume that the parameters carried in the Packet_in message have a Buffer id, a port number, and the like. In the conversion, the Buffer ID is allocated by the TOR switch. The Buffer ID is globally unique on the logical switch, and is also recorded in the mapping relationship between the switch and the logical switch in the rack.

Step 303: The TOR switch receives the first flow table processing message of the controller, where the first flow table processing message includes a processing rule of the logical switch for the new data flow. After receiving the second data flow forwarding rule request message reported by the TOR switch, the controller calculates the forwarding path, and sends the flow table processing message (here, the Flow_Mod message is taken as an example) to the logical switch to the TOR switch. Since the proxy control program of the TOR switch converts the first Packet in message reported by the actual second switch into the second Packet in message for the logical switch, the first Flow_mod message responded by the controller is also for the logical switch because the logic The switch is connected to the controller through the TOR switch, so the first flow table processing message is also sent by the controller to the TOR switch.

Step 304: The TOR switch processes the message according to the first flow table, the mapping relationship between the switch and the logical switch in the rack, and the topology information of the connection between the switches in the rack, and generates a second flow table processing message to be sent to the second flow table processing message. The switch, so that the corresponding switch processes the message to process the new data stream according to the second flow table.

The flow table processing message that the controller responds to is for the logical switch. After receiving the first flow table processing message, the TOR switch needs to map the first switch to the logical switch according to the previously recorded mapping relationship between the intra-rack switch and the logical switch. The flow_mod message is converted into a second Flow_mod message for the actual switch, and the information of the Buffer ID and the port number in the first Flow_mod message is modified, and the generated second flow table processing message is sent to the corresponding switch. Since the logical switch is actually a switch mapped by multiple intra-rack switches that are connected and managed by the TOR switch, the data flow processing rule for the logical switch in the first flow table processing message given by the controller is mapped to the actual one. When a switch is used, more than one switch may need to complete the processing of the data stream. In this case, the TOR switch needs to convert the first flow table processing message according to the mapping relationship between the switch and the logical switch in the rack and the topology information of the connection between the switches in the rack. The plurality of second flow tables process the message, and send the generated multiple second flow table processing messages to the corresponding switches, so that the switches process the processing of the new data stream according to the indication of the second flow table processing message. . For example, a Flow_mod message as shown in Table 4 in the previous embodiment indicates that the logical switch will input The new data stream of port 4 is forwarded out to the destination host by the outbound port 8. The TOR switch generates the following table 5 and Table 6 according to the mapping relationship between the switch and the logical switch in the rack and the topology information of the connection between the switches in the rack. The three second Flow_mods shown in Table 7 are sent to the virtual switch 1, the virtual switch 2, and the TOR switch itself, respectively, and the new data stream is received by the virtual switch 1 and sent to the TOR switch, and then sent to the virtual switch by the TOR switch. 2. Finally, the virtual switch 2 forwards the function of the destination host.

In the foregoing method embodiment, the TOR switch converts the data flow forwarding rule request message sent by the switch in the rack into a message for the logical switch, and the controller performs routing planning on the logical switch and delivers the flow table processing. The TOR switch converts the flow table processing message for the logical switch into a message for the intra-rack switch, and requests the forwarding routing rule in the SDN network because the complexity and scale of the network topology visible at the controller level are reduced. In the process, the speed of the controller to calculate the data flow forwarding path is accelerated, and the communication performance of the entire system is improved.

The method provided by the embodiment of the present invention is described in detail above with reference to FIGS. 1 to 7. FIG. 8 shows a possible structural diagram of a TOR switch involved in the present application. The TOR switch can implement the functions of the TOR switch in the foregoing method embodiments in FIG. 6 and FIG. 7. The terms and implementation details not defined in this embodiment can refer to the method embodiments of FIG. 6 and FIG. 7 above. As shown in FIG. 8, the TOR switch 40 may include a collecting unit 41, an information mapping unit 42, and a transmitting unit 45. The collecting unit 41 is configured to collect routing management information of all the switches in the rack managed by the TOR switch 40, where the routing management information includes device identification information, port information, and topology information of the connection between the devices; the information mapping unit 42, And the routing management information is used to map the collected routing management information of the intra-rack switch to the routing management information of the logical switch, and the sending unit 45 is configured to perform routing management of the logical switch. The information is sent to the controller so that the controller performs route management based on the routing management information of the logical switch.

The TOR switch provided in this embodiment collects routing management information of the switches in the rack through the collecting unit, and maps all the switches in the rack into a logical switch to map the routing management information between the switches in the rack and the logical switches. The controller makes routing decisions for the logical switch to map multiple switches connected to each other in the rack as a whole logical switch. The method is presented to the controller, which reduces the complexity and scale of the network topology at the controller level, thereby speeding up the controller to calculate the data flow forwarding path and improving the communication performance of the entire system.

Optionally, the TOR switch 40 further includes a receiving unit 44 and a message converting unit 43, wherein the receiving unit 44 is configured to receive a first report message sent by the first switch in the rack, where the first report message is a message sent by the switch to the controller; the message conversion unit 43 is configured to convert the information of the first switch in the first report message to the corresponding information of the logical switch according to the mapping relationship between the first switch and the logical switch, and generate a second report. The sending unit 45 is further configured to send the second report message generated by the message converting unit 43 to the controller.

Optionally, in any one of the foregoing implementations, the receiving unit 44 in the TOR switch 40 is further configured to receive a first sent message sent by the controller, where the first sent message is sent by the controller to the logical switch. The message conversion unit 43 is further configured to convert the information of the logical switch in the first sent message into the corresponding information of the destination switch according to the mapping relationship between the switch and the logical switch in the rack, and generate a second sending message, where The destination switch is the execution switch of the second sent message after the conversion; the sending unit 45 is further configured to send the second sent message generated by the message converting unit 43 to the destination switch.

Optionally, the message conversion unit 43 in the TOR switch 40 is further configured to convert the information of the logical switch in the first sent message according to the mapping relationship between the switch and the logical switch in the rack and the topology information of the connection between the switches in the rack. A second delivery message is generated for the corresponding information of the destination switch. When the first issued message sent by the controller is mapped to the actual switch by the logical switch, more than one switch may be required to complete the operation of the first issued message for the logical switch, and the message conversion unit 43 is required to be based on the intra-rack switch. The mapping relationship with the logical switch and the topology information of the connection between the switches in the rack, the first sending message is converted into a plurality of second sending messages, and the sending second sending messages are sent by the sending unit 45 respectively. The corresponding switch is provided, so that the switches complete the operation of the first issued message for the logical switch according to the indication of the second issued message.

Further, the receiving unit 44 of the TOR switch 40 is further configured to receive a first data stream forwarding rule request message sent by the second switch in the rack, where the first data stream forwarding rule request message is used to request the controller The forwarding rule of the new data stream received by the second switch. The message conversion unit 43 is further configured to convert the first data stream according to the mapping relationship between the switch and the logical switch in the rack. The port of the second switch in the sending rule request message is converted into a corresponding port of the logical switch, and the buffer identifier in the second switch in the first data flow forwarding rule request message is converted into a buffer identifier in the corresponding logical switch, and the first The second data stream forwards the rule request message, and the sending unit 45 sends the generated second data stream forwarding rule request message to the controller. The receiving unit 44 is further configured to receive a first flow table processing message sent by the controller, where the first flow table processing message includes a processing rule of the logical switch to the new data flow, where the first flow table processing message is that the controller receives the second data flow forwarding After the rule request message, the route calculation is performed to obtain a message that the logical switch processes the new data flow, and sends the message to the logical switch to indicate the processing rule for the new data flow. The message conversion unit 43 is further configured to process the message according to the first flow table, the mapping relationship between the switch and the logical switch in the rack, and the topology information of the connection between the switches in the rack, generate a second flow table processing message, and send the message by the sending unit 45. The second flow table processes the message to the switch corresponding to the second flow table processing message, so that the corresponding switch processes the message to process the new data stream according to the second flow table. Similar to the previous implementation, the message conversion unit 43 converts the first flow table processing message into multiple pieces according to the mapping relationship between the switch and the logical switch in the rack and the topology information of the connection between the switches in the rack. The flow table processes the message, and the generated multiple flow table processing messages are sent by the sending unit 45 to the corresponding switches, so that the switches cooperate to complete the processing of the new data. The TOR switch converts the data flow forwarding rule request message sent by the switch in the rack into a message for the logical switch, and the controller performs routing planning for the logical switch and sends a flow table processing message, and the TOR switch will be directed to the logical switch. The flow table processing message is converted into a message for the switch in the rack, because the complexity and scale of the network topology visible at the controller level are reduced, thereby speeding up the controller to calculate the data flow in the process of requesting the forwarding of the routing rule in the SDN network. The speed of the transmission path improves the communication performance of the entire system.

Optionally, the collecting unit 41 in the TOR switch 40 is further configured to collect routing capability information of all switches in the rack managed by the TOR switch, where the routing capability information includes the matching domain, the command, and the action information supported by the flow table. . The message mapping unit 42 is further configured to determine, according to the routing capability information collected by the collecting unit 41, a flow table configured by the logical switch and routing capability information. The sending unit 45 is further configured to send the flow table configured by the logical switch and the routing capability information to the controller, so that the controller performs route management according to the routing management information of the logical switch. In general, the cabinet The routing capability information of the switches other than the TOR switch is the same.

Fig. 9 schematically shows another TOR switch 50 of an embodiment of the present invention. As shown in FIG. 9, the TOR switch 50 includes a processor 51, a memory 52, a bus 53, and a communication interface 54. The processor 51 and the memory 52 implement a communication connection with each other through a bus 53. The communication interface 54 uses a transceiver device such as, but not limited to, a transceiver for implementing the management of the TOR switch 50 and the controller and the TOR switch. Other switches in the rack are connected by communication.

Bus 53 may include a path for communicating information between various components of TOR switch 50, such as processor 51, memory 52, and communication interface 54. The bus 53 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.

The processor 51 can be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs. The technical solution provided by the embodiment of the present invention is implemented.

The memory 52 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). Memory 52 can store operating systems and other applications. The program code for implementing the technical solution provided by the embodiment of the present invention is stored in the memory 52 and executed by the processor 51 when the technical solution provided by the embodiment of the present invention is implemented by software or firmware.

Specifically, the memory 52 can be used to store computer execution instructions, and can also be used to store various information, such as mapping relationships between switches and logical switches in the rack, and topology information of connections between switches in the rack. The processor 51 can read the information stored by the memory 52 via the bus system 53, or store the collected information to the memory 52. Additionally, when the TOR switch 50 is running, the processor 51 can read the computer-executed instructions stored by the memory 52 to perform the methods described in the previous embodiments.

It should be noted that although the TOR switch 50 shown in FIG. 9 only shows the processor 51, the memory 52, the communication interface 54, and the bus 53, in the specific implementation process, those skilled in the art It should be understood that the data, TOR switch 50 also contains other devices necessary to achieve proper operation. At the same time, those skilled in the art will appreciate that the TOR switch 50 may also include hardware devices that implement other additional functions, depending on the particular needs.

Those skilled in the art will appreciate that the various method steps and elements described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the steps and composition of the various embodiments have been generally described in terms of function in the foregoing description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. Different methods may be used to implement the described functionality for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit/module is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit is implemented in the form of a software functional unit and sold as a standalone product Or, in use, it can be transmitted in one or more instructions or code stored on a computer readable storage medium or as a computer readable medium. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage medium may be any available media that can be accessed by a computer. By way of example and not limitation, computer readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage media or other magnetic storage device, or can be used for carrying or storing in the form of an instruction or data structure. The desired program code and any other medium that can be accessed by the computer. Also. Any connection may suitably be a computer readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the definition of the medium to which they belong. As used in the present invention, a disk and a disc include a compact disc (CD), a laser disc, a compact disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, and the disc is The laser is used to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media. Based on such understanding, the technical solution of the present invention is essential or part of the prior art, or all or part of the technical solution may be stored in a storage medium, including a plurality of instructions for causing a computer device (may be a personal computer, server, or network device, etc.) performing all or part of the steps of the methods described in various embodiments of the present invention.

It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and are not limited thereto; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; and the modifications or substitutions do not deviate from the technical scope of the embodiments of the present invention.

Claims (15)

A method for routing management in a software-defined network, the method being applied to a data center, comprising: The rack TOR switch in the data center collects routing management information of all switches in the managed rack, where the routing management information includes device identification information, port information, and topology information of connections between devices; The TOR switch creates a logical switch according to the collected routing management information, and maps the collected routing management information of the intra-rack switch to the routing management information of the logical switch. The TOR switch sends routing management information of the logical switch to the controller, so that the controller performs route management according to the routing management information of the logical switch. The method of claim 1 further comprising: Receiving, by the TOR switch, a first report message sent by the first switch in the rack, where the first report message is a message sent by the first switch to the controller; The TOR switch converts the information of the first switch in the first report message to the corresponding information of the logical switch according to the mapping relationship between the first switch and the logical switch, and generates a second report message. Give the controller. The method according to claim 1 or 2, wherein the method further comprises: Receiving, by the TOR switch, a first sent message sent by the controller, where the first sent message is a message sent by the controller to the logical switch; The TOR switch converts the information of the logical switch in the first sent message to the corresponding information of the destination switch according to the mapping relationship between the switch in the rack and the logical switch, and generates a second sent message to the office. Describe the destination switch. The method according to claim 1 or 2, wherein the method further comprises: Receiving, by the TOR switch, a first sent message sent by the controller, where the first sent message is a message sent by the controller to the logical switch; Converting, by the TOR switch, the information of the logical switch in the first sent message to the destination switch according to the mapping relationship between the switch in the rack and the logical switch and the topology information of the connection between the switches in the rack Corresponding information, generating a second sending message to the destination switch. The method according to any one of claims 1 to 4, wherein the method further comprises: Receiving, by the TOR switch, a first data flow forwarding rule request message sent by a second switch in the rack, where the first data flow forwarding rule request message is used to request, by the controller, the second switch to receive Forwarding rules for new data streams; The TOR switch converts a port of the second switch in the first data flow forwarding rule request message to a corresponding port of the logical switch according to a mapping relationship between the switch in the rack and the logical switch, and the The buffer identifier in the second switch in the first data flow forwarding rule request message is converted into a buffer identifier in the corresponding logical switch, and a second data flow forwarding rule request message is generated and sent to the controller; Receiving, by the TOR switch, a first flow table processing message sent by the controller, where the first flow table processing message includes a processing rule of the logical switch to the new data flow; The TOR switch generates a second flow table processing message according to the first flow table processing message, the mapping relationship between the intra-rack switch and the logical switch, and the topology information of the connection between the switches in the rack. The second flow table processes the switch corresponding to the message, so that the corresponding switch processes the new data stream according to the second flow table processing message. The method according to any one of claims 1 to 4, wherein the method further comprises: The TOR switch collects routing capability information of all switches in the managed rack, where the routing capability information includes information about matching domains, commands, and actions supported by the flow table. Determining, by the TOR switch, a flow table configured by the logical switch and routing capability information according to the collected routing capability information; The TOR switch sends the flow table configured by the logical switch and the routing capability information to the controller, so that the controller performs route management according to the routing management information of the logical switch. The method according to any one of claims 1 to 5, characterized in that the routing capability information of the switches other than the TOR switch in the cabinet is the same. A rack TOR switch that is used in a data center and includes: a collecting unit, configured to collect routes of all switches in the rack managed by the TOR switch Management information, where the routing management information includes device identification information, port information, and topology information of connections between devices; An information mapping unit, configured to create a logical switch according to the collected routing management information, and map routing management information of the collected intra-rack switch to routing management information of the logical switch; And a sending unit, configured to send routing management information of the logical switch to the controller, so that the controller performs routing management according to the routing management information of the logical switch. The TOR switch according to claim 8, wherein the TOR switch further comprises: a receiving unit, configured to receive a first report message sent by the first switch in the rack, where the first report message is a message sent by the first switch to the controller; a message conversion unit, configured to convert information of the first switch in the first report message to corresponding information of the logical switch according to a mapping relationship between the first switch and the logical switch, to generate a second report Message The sending unit is further configured to send the second report message to the controller. The TOR switch according to claim 9, wherein: The receiving unit is further configured to receive a first sent message sent by the controller, where the first sent message is a message sent by the controller to the logical switch; The message conversion unit is further configured to convert information of the logical switch in the first sent message to corresponding information of the destination switch according to a mapping relationship between the switch in the rack and the logical switch, and generate a second Send a message; The sending unit is further configured to send the second sent message to the destination switch. The TOR switch according to claim 9, wherein: The receiving unit is further configured to receive a first sent message sent by the controller, where the first sent message is a message sent by the controller to the logical switch; The message conversion unit is further configured to: according to the mapping relationship between the switch in the rack and the logical switch, and the topology information of the connection between the switches in the rack, the information about the logical switch in the first sent message Converting to the corresponding information of the destination switch, generating a second sending message; The sending unit is further configured to send the second sent message to the destination switch. The TOR switch according to any one of claims 8 to 11, characterized in that: The receiving unit is further configured to receive a first data flow forwarding rule request message sent by a second switch in the rack, where the first data flow forwarding rule request message is used to request, for the second a forwarding rule of the new data stream received by the switch, and receiving a first flow table processing message sent by the controller, where the first flow table processing message includes a processing rule of the logical switch to the new data stream; The message conversion unit is further configured to convert, according to a mapping relationship between the intra-rack switch and the logical switch, a port of the second switch in the first data flow forwarding rule request message to a correspondence of the logical switch Transmitting, by the port, the buffer identifier in the second switch in the first data flow forwarding rule request message to a buffer identifier in the corresponding logical switch, generating a second data flow forwarding rule request message, and The first flow table processing message, the mapping relationship between the intra-rack switch and the logical switch, and the topology information of the connection between the switches in the rack, to generate a second flow table processing message; The sending unit is further configured to send the second data stream forwarding rule request message to the controller, and send the second flow table processing message to the switch corresponding to the second flow table processing message, so that The corresponding switch processes the new data stream according to the second flow table processing message. The TOR switch according to any one of claims 8 to 11, characterized in that: The collecting unit is further configured to collect routing capability information of all switches in the managed rack, where the routing capability information includes information about matching domains, commands, and actions supported by the flow table. The message mapping unit is further configured to determine, according to the collected routing capability information, a flow table configured by the logical switch and routing capability information; The sending unit is further configured to send the flow table configured by the logical switch and the routing capability information to the controller, so that the controller performs route management according to the routing management information of the logical switch. The TOR switch according to any one of claims 8 to 12, characterized in that the routing capability information of the switches other than the TOR switch in the cabinet is the same. A TOR switch, comprising: a processor, a memory, a bus, and a communication port; the memory is configured to store a computer to execute an instruction, the processor is connected to the memory through the bus, and the communication port is used by Communicating with a switch in a rack managed by the controller and the TOR switch, the processor executing the computer-executed instructions stored in the memory to perform the method of any one of claims 1 to 7. Methods.

Images