WO2016070406A1

WO2016070406A1 - Topology discovery method and device

Info

Publication number: WO2016070406A1
Application number: PCT/CN2014/090569
Authority: WO
Inventors: 李建飞; 王蛟; 苏金钊
Original assignee: 华为技术有限公司
Priority date: 2014-11-07
Filing date: 2014-11-07
Publication date: 2016-05-12
Also published as: CN105765903B; CN105765903A

Abstract

A topology discovery method and device, the method comprising: a second master controller receiving a topology discovery message sent by a second switch (301), the topology discovery message comprising: link discovery data packets received by the second switch, ID of the second switch and ID of a second port; the second master controller, when judging that the link discovery data packets are not link discovery data packets of a local domain, generating report information on the basis of the topology discovery message (302), the report information comprising: ID of a first switch, ID of a first port, ID of the second switch and ID of the second port; and the second master controller sending the report information to a global topology broker, allowing the global topology broker to discover inter-domain topology links on the basis of the report information (303), therefore, discovery of cross-domain global topology links can be realized.

Description

Topology discovery method and device

Technical field

The present invention relates to the field of communications technologies, and in particular, to a topology discovery method and device.

Background technique

To solve the deployment flexibility and manageability of network elements, the industry has proposed the concept of Software-Defined Network (SDN). The SDN decouples the control logic and the forwarding function of the network element and centrally deploys the control logic, so that the control and maintenance of the network can be realized simply by the operation of the control plane device. In practical applications, the SDN network generally includes a controller (Controller) as a control plane device and a switch (Switch) as a forwarding plane device. The controller controls the data packet processing flow by controlling flow entries on the switch. The switch forwards data packets based on the flow entries. The open flow (Openflow) protocol is the most typical and most widely used protocol in the SDN network. The network elements in the Openflow protocol are called OpenFlow Controller and OpenFlow Switch. And OF switch.

An SDN network is logically composed of a plurality of domains. As shown in Figure 1, each domain includes: a controller, a switch, and a host. The controllers in the domain manage the switches and hosts in the domain. One domain may contain one or more controllers. When multiple controllers are included, one of the multiple controllers is the primary controller. When a controller is included, the controller may be considered as the primary controller. The SDN network also includes a Global Topology Broker that communicates only with the primary controllers of the various domains. Controllers in each domain do not communicate directly, and all inter-domain events, such as cross-domain routing and inter-domain topology link discovery, are handled by global topology agents. An inter-domain topology link refers to a connection between network elements in different domains, and a connection between network elements in the same domain is called an intra-domain topology link. Generally, when an inter-domain topology link is found. The following information about the inter-domain topology link needs to be determined: the domain ID of the network element at both ends of the link, the network element ID and the port ID of both ends of the link. When the information is determined, it indicates that an inter-domain topology link is found. . Based on the SDN network structure shown in Figure 1, how to implement global topology proxy discovery of inter-domain topology links and implement cross-domain global topology discovery is a problem that needs to be solved.

However, in the current SDN network, LLDP is used to implement the discovery of intra-domain topology links, and no cross-domain global topology discovery method is disclosed.

Summary of the invention

In the embodiment of the present invention, a topology discovery method and device are provided, which can implement discovery of a cross-domain global topology link.

In order to solve the above technical problem, the embodiment of the present invention discloses the following technical solutions:

In a first aspect, a topology discovery method is provided, including:

The second main controller receives the topology discovery packet sent by the second switch, where the topology discovery packet includes: a link discovery data packet received by the second switch, a second switch ID, and a second port ID; The link discovery data packet includes: a first switch ID, a first port ID; the first switch ID is used to indicate a first switch that sends the link discovery data packet to the second switch, and the second switch The ID is used to indicate the second switch that receives the link discovery data packet, where the first port ID is used to indicate that the first switch sends the port of the link discovery data packet, and the second port ID is a port for instructing the second switch to receive the link discovery data packet;

When the second primary controller determines that the link discovery data packet is not the link discovery data packet of the local domain, the second primary controller generates the report information according to the topology discovery packet, where the report information includes: a first switch ID, and a first a port ID, a second switch ID, and a second port ID;

The second main controller sends the report information to the global topology agent, so that the global topology agent discovers the inter-domain topology link according to the report information.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the link discovery data packet further includes: a first domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs; The second main controller determines that the link discovery data packet is not a link discovery data packet of the local domain, and includes:

The second main controller determines that the first domain ID included in the link discovery data packet is different from the domain ID of the domain under which the second primary controller is located.

With reference to the first aspect, in a second possible implementation manner of the first aspect, the second main controller determines that the link discovery data packet is not a link discovery data packet of the local domain, and includes:

The second main controller determines that the first switch indicated by the first switch ID is not a switch of a domain under the second main controller.

With reference to the first aspect, and/or the first possible implementation of the first aspect, and/or the second possible implementation of the first aspect, in the third possible implementation of the first aspect, the second After the main controller determines that the link discovery data packet is not the link discovery data packet of the local domain, the main controller further includes:

The second main controller adds the second switch ID and the second port ID to the border switch management information.

In a second aspect, a topology discovery method is provided, including:

The global topology agent receives the report information sent by the second primary controller, where the report information includes: a first switch ID, a first port ID, a second switch ID, and a second port ID; the first switch ID is used to indicate sending a first switch of the link discovery data packet, where the second switch ID is used to indicate that a second switch that receives the link discovery data packet is used, where the first port ID is used to indicate that the first switch sends The port of the link discovery data packet, where the second port ID is used to indicate that the second switch receives the port of the link discovery data packet;

The global topology agent discovers an inter-domain topology link according to the reported information.

With reference to the second aspect, in a first possible implementation manner of the second aspect, after the global topology proxy discovers the inter-domain topology link according to the reported information, the method further includes:

The global topology agent controls the first switch or the second switch to perform inter-domain data packet forwarding according to the inter-domain topology link.

With reference to the second aspect, and/or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the global topology proxy discovers an inter-domain topology link according to the reported information, including :

Determining, by the global topology agent, the domain to which the first switch belongs according to the first switch ID, and determining a domain to which the second switch belongs according to the second switch ID;

Determining, by the global topology agent, the first end of the inter-domain topology link according to the domain to which the first switch belongs, the first switch ID, and the first port ID, according to the domain to which the second switch belongs, the second switch ID, and The second port ID determines the second end of the inter-domain topology link.

With reference to the second aspect, and/or the first possible implementation manner of the second aspect, in the third possible implementation manner of the second aspect, the reporting information further includes: a first domain ID, a second domain ID, The first domain ID is used to indicate the domain to which the first switch belongs, and the second domain ID is used to indicate the domain to which the second switch belongs; the global topology proxy discovers the inter-domain topology link according to the reported information. include:

Determining, by the global topology proxy, the first end of the inter-domain topology link according to the first domain ID, the first switch ID, and the first port ID, according to the second domain ID, the second switch ID, and the second The port ID determines the second end of the inter-domain topology link.

In a third aspect, a host controller is provided, including:

a receiving unit, configured to receive a topology discovery packet sent by the second switch, where the topology discovery packet includes: a link discovery data packet, a second switch ID, and a second port ID received by the second switch; The link discovery data packet includes: a first switch ID, a first port ID; and the first switch ID And a first switch indicating that the link discovery data packet is sent to the second switch, where the second switch ID is used to indicate the second switch that receives the link discovery data packet, the first port The ID is used to indicate that the first switch sends the port of the link discovery data packet, and the second port ID is used to indicate that the second switch receives the port of the link discovery data packet;

a generating unit, configured to: when the link discovery data packet received by the receiving unit is not a link discovery data packet of the local domain, generate report information according to the topology discovery packet, where the report information includes: a switch ID, a first port ID, a second switch ID, and a second port ID;

And a sending unit, configured to send the report information generated by the generating unit to a global topology agent, so that the global topology agent discovers an inter-domain topology link according to the reported information.

With the third aspect, in a first possible implementation manner of the third aspect, the link discovery data packet further includes: a first domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs; The generating unit is specifically configured to:

Determining that the first domain ID included in the link discovery data packet is different from the domain ID of the domain controlled by the second primary controller.

With reference to the third aspect, in a second possible implementation manner of the third aspect, the generating unit is specifically configured to:

Determining that the first switch indicated by the first switch ID is not a switch of a domain controlled by the second primary controller.

With reference to the third aspect, and/or the first possible implementation manner of the third aspect, and/or the second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the method further includes:

And a management unit, configured to: after the generating unit determines that the link discovery data packet is not a link discovery data packet of the local domain, adding the second switch ID and the second port ID to the boundary switch management information.

In a fourth aspect, a global topology proxy is provided, including:

a receiving unit, configured to receive report information sent by the second main controller, where the report information includes: a first switch ID, a first port ID, a second switch ID, and a second port ID; the first switch ID is used by And indicating a first switch that sends the link discovery data packet, where the second switch ID is used to indicate that a second switch that receives the link discovery data packet is used, where the first port ID is used to indicate the first switch The switch sends the port of the link discovery data packet, where the second port ID is used to indicate that the second switch receives the port of the link discovery data packet;

And a determining unit, configured to discover an inter-domain topology link according to the report information received by the receiving unit.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the method further includes:

And a control unit, configured to control the first switch or the second switch to perform inter-domain data packet forwarding according to the inter-domain topology link discovered by the determining unit.

With reference to the fourth aspect, and/or the first possible implementation manner of the fourth aspect, in the second possible implementation manner of the fourth aspect, the determining unit is specifically configured to:

Determining, according to the first switch ID, a domain to which the first switch belongs, and determining, according to the second switch ID, a domain to which the second switch belongs;

Determining, according to the domain to which the first switch belongs, the first switch ID, and the first port ID, the first end of the inter-domain topology link, according to the domain to which the second switch belongs, the second switch ID, and the second port ID The second end of the inter-domain topology link.

With reference to the fourth aspect, and/or the first possible implementation manner of the fourth aspect, in a third possible implementation manner of the fourth aspect, the reporting information further includes: a first domain ID, a second domain ID, The first domain ID is used to indicate the domain to which the first switch belongs, and the second domain ID is used to indicate the domain to which the second switch belongs; the determining unit is specifically configured to:

Determining, according to the first domain ID, the first switch ID, and the first port ID, a first end of the inter-domain topology link, determining, according to the second domain ID, the second switch ID, and the second port ID The second end of the inter-domain topology link.

In the embodiment of the present invention, the second main controller receives the topology discovery packet sent by the second switch, where the topology discovery packet includes: a link discovery data packet, a second switch ID, and a second received by the second switch. a two-port ID; the link discovery data packet includes: a first switch ID, a first port ID; the first switch ID is used to indicate a first switch that sends the link discovery data packet to the second switch The second switch ID is used to indicate the second switch that receives the link discovery data packet, where the first port ID is used to indicate that the first switch sends the port of the link discovery data packet. The second port ID is used to indicate that the second switch receives the port of the link discovery data packet; the second main controller determines that the link discovery data packet is not a link discovery data packet of the local domain. And generating the report information according to the topology discovery packet, where the report information includes: a first switch ID, a first port ID, a second switch ID, and a second port ID; the second host controller reports the report letter Sending to the global topology agent, so that the global topology agent discovers the cross-domain global topology link according to the reported information, so that the second primary controller provides data support for the global topology agent to discover the cross-domain global topology link, so that the global topology The agent is able to discover cross-domain global topology links.

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. Obviously, for those skilled in the art, no creative labor is required. Further drawings can also be obtained from these drawings.

1 is an exemplary diagram of an SDN network structure;

2 is a schematic diagram of an application scenario according to an embodiment of the present invention;

3 is a flow chart of an embodiment of a topology discovery method according to the present invention;

4 is a flow chart of another embodiment of a topology discovery method according to the present invention;

FIG. 5A is a schematic diagram of an application scenario of a topology discovery method according to the present invention; FIG.

5B is a flowchart of another embodiment of a topology discovery method according to the present invention;

5C is a flowchart of another embodiment of a topology discovery method according to the present invention;

Figure 6 is a block diagram of an embodiment of a main controller of the present invention;

7 is a block diagram of an embodiment of a global topology proxy of the present invention;

Figure 8 is a block diagram of another embodiment of the main controller of the present invention;

9 is a block diagram of another embodiment of a global topology agent of the present invention.

detailed description

The above-mentioned objects, features, and advantages of the embodiments of the present invention will become more apparent and understood. Give further details.

Embodiments of the invention may be applied to an SDN network comprising at least two domains.

The application scenarios of the embodiments shown in FIG. 3 to FIG. 6 will be exemplified below through FIG. 2 . As shown in FIG. 2, the method includes: a global topology proxy 210, a first domain 220, and a second domain 230. The first domain 220 includes: a first primary controller 2201, a plurality of switches 1202 of the first domain, and a second domain. 230 includes: a second main controller 2301, a plurality of switches 2302 of the second domain; the first main controller 2201 and the second main controller 2301 are connected to the global topology proxy 210, and the respective switches 2202 of the first domain are respectively associated with the first The main controller 2201 is connected, and the switches 2302 of the second domain are respectively connected to the second main controller 2301. In addition, each switch 2202 of the first domain may be connected to each other, and each switch 2302 of the second domain may be connected to each other, and the switch 2202 of the first domain and the switch 2302 of the second domain may be connected, and the switch in the same domain The connection between the two is called the intra-domain topology link, and the connection between the switches in different domains is called the inter-domain topology link.

In addition, the first domain 220 and the second domain 230 may also include a plurality of hosts respectively, which are not shown in FIG. 2 because they are not involved in the embodiment of the present invention.

The first and second of the first main controller and the second main controller are only used to distinguish the main controllers in the two domains, and have no other practical significance.

In an actual application, an SDN network may include more than two domains. When the topology discovery method of the embodiment of the present invention is applied to an SDN network structure including two or more domains, the topology discovery method is determined according to the embodiment of the present invention. It is an inter-domain topology link between two domains. In the process, only two domains in multiple domains are involved. Therefore, the actual application scenario can be summarized as the scenario shown in Figure 2.

In the following embodiments, it is assumed that the first primary controller 2201 of the first domain 220 initiates topology link discovery for the first port of the first switch in the first domain 220, the first port of the first switch and the second domain 230 An inter-domain topology link exists between the second ports of the second switch. The first and second of the first switch and the second switch are only used to distinguish the two switches, and have no other practical meaning. The first and second of the first port and the second port are only used to distinguish two. The port of the switch has no other practical significance. The first switch may be any switch in the first domain that has an inter-domain topology link with the switch in the second domain, and the second switch is a switch in the second domain that has an inter-domain topology link with the first switch.

The topology discovery method of the embodiment of the present invention will be described below in the application scenario shown in FIG.

FIG. 3 is a flowchart of an embodiment of a method for discovering a topology according to the present invention. The embodiment is described from the second main controller side, and includes:

Step 301: The second main controller receives the topology discovery packet sent by the second switch, where the topology discovery packet includes: a link discovery data packet, a second switch ID, and a second port ID received by the second switch.

The link discovery data packet includes: a first switch ID and a first port ID;

The first switch ID is used to indicate a first switch that sends a link discovery data packet;

The second switch ID is used to indicate a second switch that receives the link discovery data packet;

The first port ID is used to indicate that the first switch sends the first port of the link discovery data packet;

The second port ID is used to indicate that the second switch receives the second port of the link discovery data packet.

Step 302: When the second primary controller determines that the link discovery data packet is not the link discovery data packet of the domain managed by the second primary controller, the second primary controller generates the report information according to the topology discovery packet, where the report information includes: the first switch ID, the first A port ID, a second switch ID, and a second port ID.

In a possible implementation, the link discovery data packet may further include: a first domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs; and the second primary controller determines The link discovery data packet is not a link discovery data packet of the local domain, and may include:

In another possible implementation manner, the determining, by the second main controller, that the link discovery data packet is not a link discovery packet of the local domain may include:

The second main controller determines that the link discovery data packet is not a link discovery data packet of the local domain, and indicates that the second switch indicated by the second switch ID and the port indicated by the second port ID are not connected to the local port. The network element of the domain, but the network element of the other domain. Therefore, after the second primary controller determines that the link discovery data packet is not the link discovery data packet of the local domain, the second primary controller may The second switch ID and the second port ID are added to the border switch management information, so as to implement management of the border switch in the domain under the jurisdiction of the second host controller, where the border switch refers to inter-domain exchange with switches of other domains. A switch for a topology link.

As shown in Table 1 below, the primary controllers of each domain can maintain the information of the border switches in the domain under the following table. The information of the border switches includes: switch ID, switch attributes, port ID, and port status. The fields in the fields of the switch ID, switch attributes, port IDs, and port status are as follows. You can define them in the actual application according to the actual scenario. For details, for example, the port in the following table indicates the port. When it is on, lastseetime indicates the last discovery time of the port, and state indicates the congestion status of the port, the amount of data sent and received, and other states.

Table 1

Step 303: The second primary controller sends the report information to the global topology proxy, so that the global topology proxy discovers the inter-domain topology link according to the reported information.

The inter-domain topology link can be used to forward inter-domain data packets. The global topology agent may control the first switch or the second switch to perform inter-domain data packet forwarding according to the inter-domain topology link. Optionally, the global topology proxy may control the first exchange by using the second primary controller. The device or the second switch forwards the inter-domain data packet.

In this embodiment, the second main controller receives the topology discovery packet sent by the second switch, and determines that the link discovery data packet in the topology discovery packet is not the link discovery data packet of the local domain, and generates the packet according to the topology discovery packet. The report information is sent to the global topology agent, so that the global topology agent discovers the cross-domain global topology link according to the reported information, thereby providing data support for the global topology agent to discover the cross-domain global topology link, so that the global topology agent can discover Cross-domain global topology link.

FIG. 4 is a flowchart of another embodiment of a method for discovering a topology according to the present invention. The embodiment is described from the global topology proxy side, and includes:

Step 401: The global topology proxy receives the report information sent by the second primary controller, where the report information includes: a first switch ID, a first port ID, a second switch ID, and a second port ID;

The first switch ID can be implemented by using the name, MAC address, or IP address of the first switch, and is not limited herein; the second switch ID can be implemented by using the name, MAC address, or IP address of the second switch.

The port ID of the switch may be set for each port in advance. The specific setting method is not limited in the embodiment of the present invention.

Step 402: The global topology proxy discovers the inter-domain topology link according to the reported information.

In a possible implementation manner, the global topology proxy may discover the inter-domain topology link according to the reporting information, and the method may include:

In another possible implementation, the reporting information may further include: a first domain ID, a second domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs, and the second domain The ID is used to indicate the domain to which the second switch belongs; and the global topology agent discovers the inter-domain topology chain according to the reported information. Roads can include:

The domain ID of each domain may be set in advance for each domain. The specific setting method is not limited in the embodiment of the present invention.

After the step 402, the global topology agent may further control the first switch or the second switch to perform inter-domain data packet forwarding according to the discovered inter-domain topology link. Optionally, the global topology proxy may pass The second main controller controls the first switch or the second switch to forward the inter-domain data packet.

In this embodiment, the global topology proxy receives the report information sent by the second primary controller, and the report information includes: the first switch ID, the first port ID, the second switch ID, and the second port ID, and the cross-domain global is found according to the reported information. Topology links, enabling the discovery of cross-domain global topology links.

5A is an application scenario example of a topology discovery method according to the present invention. The network includes: a global topology proxy, domain 1, and domain 2. In domain 1, the host controller OFC_1, the switch Sw1_1, the switch Sw1_2, and the switch Sw1_3 are included in the domain 1. In the domain 2, the main controller OFC_2, the switch Sw2_1, and the switch Sw2_2, the port 1 of the switch Sw1_1 in the domain 1 is connected to the port 1 of the switch Sw2_1 in the domain 2, and an inter-domain topology link is formed. The domain ID of the domain 1 is Domain 1, the domain ID of the domain 2 is Domain 2, the ID of the switch Sw1_1 is Sw1_1, the ID of the switch Sw2_1 is Sw2_1, and the ID of the port 1 of the switch Sw1_1 and the switch Sw2_1 are Port1. The purpose of the method is to enable the global topology agent to discover this inter-domain topology link. The domain 1 and the domain 2 may also include a host. Since the embodiment of the present invention is not involved, it is not illustrated.

FIG. 5B is a flowchart of another embodiment of a topology discovery method according to the present invention, which will be described in conjunction with the example shown in FIG. 5A.

In this embodiment, a domain ID is set in advance for each domain, and the domain ID may be set by the global topology proxy for each domain, or may be set by the primary controller of each domain as the domain of the master controller itself, for example, The main controller can obtain a value according to the IP address or MAC address and time of the main controller itself as a domain ID of the domain under the control of the main controller, and the method for determining the domain ID is not limited. No longer.

Step 501: The primary controller of each domain sends registration information to the global topology proxy to register each domain in the global topology proxy.

The registration information may include: an address of the primary controller, a domain ID of a domain under the jurisdiction of the primary controller, and domain information of the domain under the jurisdiction.

The address of the primary controller may be an IP address or a MAC address. The domain information of the domain may include: the ID of each network element in the domain, and the IP address range of the network element in the domain. The ID of the network element may be the name of the network element, the IP address of the network element, or the MAC address.

Referring to FIG. 5A, the registration information reported by the primary controllers of the two domains may be as shown in Table 2. The primary controller OFC_1 is domain 1 and the domain ID is Domain1. The IP address of the primary controller OFC_1 is 192.168.1.11. The domain information of the domain is Host1_1 and the IP address range is 192.168.1.10 to 192.168. The IP address of the primary controller OFC_2 is 192.168.2.11, and the domain information of the domain is: Host2_1, and the IP address range is 192.168.2.10 to 192.168. 2.100.

Table 2

Among them, this step is an optional step.

Step 502: The first primary controller of the first domain generates a link discovery data packet for the first port of the first switch, where the link discovery data packet may include: a first switch ID, a first port ID, and a first domain. ID.

With reference to FIG. 5A, assuming that the first domain is domain 1, the first primary controller is the primary controller OFC_1, the first switch is the switch Sw1_1, and the first port is the port 1, the first switch ID is Sw1_1, and the first port ID is For Port1, the first domain ID is Domain1.

In addition to the above three types of information, the link discovery data packet may further include other information, and the specific information included in the embodiment of the present invention is not limited.

In a possible implementation manner, the link discovery data packet can be implemented by the structure shown in Table 3 below. Now.

table 3

The src_mac indicates the MAC address of the source network element that sends the link discovery data packet. In this embodiment, the source network element is the first switch; dst_mac indicates the MAC address of the target network element that receives the link discovery data packet, because the first The primary controller does not know the target network element of the link discovery packet when generating the link discovery packet. Therefore, this field can be defaulted, see Table 2, represented by FF: FF: FF: FF: FF; eth_type indicates : Ethernet type, used to indicate that the data packet is a data packet for link discovery; the chassis ID triplet (TLV) indicates: a field of the TLV in the LLDP data packet; and the Port ID TLV indicates the transmission chain in the source network element. The port ID triplet of the route discovery packet, where Value is used to record the port ID of the port in the source network element that sends the link discovery packet, such as Port1 shown in Table 2; TTL TLV means: timeout; Domain The TLV represents a domain triplet, where Value is used to record the domain ID of the domain under the jurisdiction of the primary controller; Action represents the action taken by the source network element on the link discovery packet, for example, it can be set to the out- shown in Table 2 To-port1, which indicates the source network The link forwarding packet is forwarded from the port whose port ID is port1. When the source NE forwards the link discovery packet, the Action field will be cleared or set to the default by the source NE; End of TLV indicates : The end of the TLV field in the packet.

Step 503: The first switch receives the link discovery data packet, and forwards the link discovery data packet from the first port indicated by the first port ID.

According to the above example, the first port ID in FIG. 5A is Port1, the first port indicated is port 1, and the switch Sw1_1 will forward the link discovery data packet from its own port 1.

Step 504: The second switch receives the link discovery data packet from the second port, and generates a topology discovery packet to be sent to the second primary controller.

The topology discovery packet includes: a link discovery data packet received by the second switch, a second switch ID, and a second port ID.

The second switch ID is used to indicate the second switch; the second port ID is used to indicate the second port in the second switch that receives the link discovery data packet.

According to the above example, since port 1 of switch Sw1_1 in FIG. 5A is actually connected to port 1 of switch Sw2_1, the second switch is switch Sw2_1 and the second port is port 1, correspondingly,

The switch Sw2_1 will receive the link discovery packet from its own port 1; the switch Sw2_1 is born. The second switch ID in the topology discovery packet is Sw2_1, the second port ID is Port1, and the second host controller is the primary controller OFC2_1 in the second domain.

Step 505: The second primary controller receives the topology discovery packet, and determines that the first domain ID in the link discovery data packet is different from the domain ID of the domain in which the second primary controller is located, and generates the report information according to the topology discovery packet. The report information is sent to the global topology agent.

The reporting information may include: a first switch ID, a first port ID, a first domain ID, a second switch ID, a second port ID, and a second domain ID.

In this embodiment, if the second primary controller determines that the first domain ID in the link discovery data packet is the same as the domain ID of the domain under the second primary controller, the second primary controller performs intra-domain topology link discovery. The process is not repeated here.

According to the above example and in conjunction with FIG. 5A, the second primary controller is the primary controller OFC2_1, the domain ID of the domain 2 under its jurisdiction is Domain 2, and the first domain ID is Domain 1, and the primary controller OFC2_1 determines that the two are different. The report information is generated. The first switch ID in the report information is Sw1_1, the first port ID is Port1, the first domain ID is Domain 1, the second switch ID is Sw2_1, the second port ID is Port1, and the second domain ID is For Domain 2.

Step 506: The global topology agent receives the report information, and discovers the inter-domain topology link according to the report information.

The global topology proxy may discover the inter-domain topology link according to the reported information, and may include:

The global topology agent determines the first end of the inter-domain topology link according to the first domain ID, the first switch ID, and the first port ID, and discovers the inter-domain topology link according to the second domain ID, the second switch ID, and the second port ID. The second end.

According to the above example and in conjunction with FIG. 5A, the global topology agent determines that the first end of the inter-domain topology link is: port 1 of the switch Sw1_1 of the domain 1, and the second end of the inter-domain topology link is: the switch Sw2_1 of the domain 2. Port 1.

In this embodiment, when generating the link discovery data packet, the first primary controller carries the first domain ID of the first domain under its jurisdiction in the link discovery data packet, so that the link discovery data packet passes the inter-domain topology. When the link is transmitted to the second primary controller of the other domain, the second primary controller may determine, according to the first domain ID, that the link discovery data packet is not a link discovery data packet of a domain managed by the second primary controller, and further The global topology agent is reported, enabling the global topology agent to discover cross-domain global topology links.

Referring to FIG. 5C, it is a flowchart of another embodiment of the topology discovery method of the present invention, which will also be described in conjunction with the example shown in FIG. 5A.

In this embodiment, a domain ID is set in advance for each domain, and the domain ID may be set by the global topology proxy for each domain, or may be set by the primary controller of each domain as the domain of the master controller itself, for example, The main controller can obtain a value as a domain ID of the domain under the control of the host controller by hashing according to the IP address or MAC address and time of the host controller itself.

Step 511: The primary controller of each domain sends registration information to the global topology proxy to register each domain in the global topology proxy.

For the implementation of this step, refer to the related description in step 501, and details are not described herein.

Step 512: The first primary controller of the first domain generates a link discovery data packet for the first port of the first switch, where the link discovery data packet may include: a first switch ID and a first port ID.

With reference to FIG. 5A, assuming that the first domain is domain 1, the first primary controller is the primary controller OFC_1, the first switch is the switch Sw1_1, and the first port is the port 1, the first switch ID is Sw1_1, and the first port ID is For port1.

For the implementation structure of the link discovery data packet, refer to the related description of step 502. The Domain TLV field in Table 2 may be omitted.

Step 513: The first switch receives the link discovery data packet, and forwards the link discovery data packet from the first port indicated by the first port ID.

Step 514: The second switch receives the link discovery data packet from the second port, and generates a topology discovery packet to be sent to the second primary controller.

The switch Sw2_1 receives the link discovery data packet from its own port 1. The second switch ID of the topology discovery packet generated by the switch Sw2_1 is Sw2_1, and the second port ID is Port1. The second primary controller is the master of the second domain. Controller OFC2_1.

Step 515: The second primary controller receives the topology discovery packet, and determines that the first switch indicated by the first switch ID in the link discovery data packet is not the switch of the domain controlled by the second primary controller, according to the topology. The device generates the report information and sends the report information to the global topology agent.

The reporting information may include: a first switch ID, a first port ID, a second switch ID, and a second port ID.

Generally, the information of each network element in the jurisdiction domain is stored in the second main controller. Therefore, in this step, the second main controller may determine, according to the pre-stored information, the first switch ID indicated in the link discovery data packet. Whether the first switch is a switch of a domain under the jurisdiction of the second primary controller, and details are not described herein again.

In this embodiment, if the second primary controller determines that the first switch indicated by the first switch ID in the link discovery data packet is a switch of a domain controlled by the second primary controller, the second primary controller performs an intra-domain topology. The link discovery process is not described here.

According to the above example and in conjunction with FIG. 5A, the second main controller is the main controller OFC2_1, the first switch ID is Sw1_1, and the second main controller can determine that the first switch with the ID Sw1_1 is not the switch in the domain 2 under its jurisdiction. .

Step 516: The global topology agent receives the report information, and discovers the inter-domain topology link according to the report information.

Determining, by the global topology agent, the first end of the inter-domain topology link according to the domain to which the first switch belongs, the first switch ID, and the first port ID, according to the domain to which the second switch belongs, the second switch ID, and The second port identifier determines a second end of the inter-domain topology link.

In this step, the primary controller of each domain in the step 511 has sent the registration information of each domain to the global topology proxy. Therefore, in this step, the global topology proxy may determine, according to the received registration information of each domain, the first switch belongs to. The domain and the domain to which the second switch belongs.

According to the above example and in conjunction with FIG. 5A, the global topology agent may determine that the first switch with the ID Sw1_1 belongs to the domain 1 and the second switch with the ID Sw2_1 belongs to the domain 2 according to the registration information sent by each primary controller in step 511; The first end of the inter-domain topology link is determined as: port 1 of the switch Sw1_1 of the domain 1, and the second end is the port 1 of the switch Sw2_1 of the domain 2.

In this embodiment, when the link discovery data packet generated by the first primary controller is transmitted to the second primary controller of another domain through the inter-domain topology link, the second primary controller determines that the link discovery data packet is not the first The link of the domain under the jurisdiction of the two primary controllers discovers the data packet, and then reports the global topology agent, so that the global topology agent can realize the discovery of the cross-domain global topology link.

Corresponding to the embodiment of the topology discovery method of the present invention, the present invention also provides an embodiment of a primary controller and a global topology agent.

Referring to Figure 6, a block diagram of one embodiment of a main controller of the present invention is shown. The main controller 600 includes: a receiving unit 610, a generating unit 620, and a sending unit 630, where

The receiving unit 610 is configured to receive a topology discovery packet sent by the second switch, where the topology discovery packet includes: a link discovery data packet, a second switch ID, and a second port ID received by the second switch; The link discovery data packet includes: a first switch ID, a first port ID; the first switch ID is used to indicate a first switch that sends the link discovery data packet to the second switch, and the second The switch ID is used to indicate the second switch that receives the link discovery data packet, where the first port ID is used to indicate that the first switch sends the port of the link discovery data packet, and the second port The ID is used to indicate that the second switch receives the port of the link discovery data packet;

The generating unit 620 is configured to: when the link discovery data packet received by the receiving unit is not the link discovery data packet of the local domain, generate report information according to the topology discovery packet, where the report information includes: a switch ID, a first port ID, a second switch ID, and a second port ID;

The sending unit 630 is configured to send the report information generated by the generating unit to the global topology agent, so that the global topology agent discovers the inter-domain topology link according to the report information.

Optionally, the link discovery data packet may further include: a first domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs; and the generating unit 620 may be specifically configured to:

Optionally, the generating unit 620 is specifically configured to:

Optionally, the main controller 600 may further include:

In this embodiment, the second main controller receives the topology discovery packet sent by the second switch, and determines that the link discovery data packet in the topology discovery packet is not the link discovery data packet of the local domain, and generates the packet according to the topology discovery packet. The report information is sent to the global topology agent, so that the global topology agent discovers the cross-domain global topology link according to the reported information, thereby providing the global topology agent with the number of cross-domain global topology links. Supported to enable global topology agents to discover cross-domain global topology links.

Referring to FIG. 7, a block diagram of an embodiment of a global topology proxy of the present invention is shown. The global topology agent 700 includes: a receiving unit 710 and a determining unit 720, where

The receiving unit 710 is configured to receive the report information sent by the second main controller, where the report information includes: a first switch ID, a first port ID, a second switch ID, and a second port ID; And indicating to the first switch that sends the link discovery data packet, where the second switch ID is used to indicate that a second switch that receives the link discovery data packet is used, where the first port ID is used to indicate the a switch sends a port of the link discovery data packet, where the second port ID is used to indicate that the second switch receives the port of the link discovery data packet;

The determining unit 720 is configured to discover an inter-domain topology link according to the report information received by the receiving unit 710.

Optionally, the determining unit 720 is specifically configured to:

Optionally, the reporting information may further include: a first domain ID, a second domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs, and the second domain ID is used to indicate the The domain to which the second switch belongs; the determining unit 720 may be specifically configured to:

In this embodiment, the global topology proxy receives the report information sent by the second primary controller, and the report information includes: the first switch ID, the first port ID, the second switch ID, and the second port ID, and the inter-domain topology is found according to the reported information. Link, which enables the discovery of cross-domain global topology links.

FIG. 8 is a schematic structural diagram of a main controller according to an embodiment of the present invention. The main controller 800 includes a processor 810, a memory 820, a transceiver 830, and a bus 840.

The processor 810, the memory 820, and the transceiver 830 are connected to each other through a bus 840; the bus 840 can be So ISA bus, PCI bus or 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 8, but it does not mean that there is only one bus or one type of bus.

The memory 820 is configured to store a program. In particular, the program can include program code, the program code including computer operating instructions. The memory 820 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.

The transceiver 830 is used to connect other devices and communicate with other devices. The transceiver 830 is configured to: receive a topology discovery packet sent by the second switch, where the topology discovery packet includes: a link discovery data packet, a second switch ID, and a second port ID received by the second switch; The link discovery data packet includes: a first switch ID, a first port ID; the first switch ID is used to indicate a first switch that sends the link discovery data packet to the second switch, and the second The switch ID is used to indicate the second switch that receives the link discovery data packet, where the first port ID is used to indicate that the first switch sends the port of the link discovery data packet, and the second port The ID is used to indicate that the second switch receives the port of the link discovery data packet, and is further configured to send the report information generated by the processor 810 to the global topology proxy, so that the global topology proxy is configured according to the report Information discovery inter-domain topology links.

The processor 810 executes the program code, and is configured to: when the link discovery data packet is not a link discovery data packet of the local domain, generate report information according to the topology discovery packet, where the report information includes: A switch ID, a first port ID, a second switch ID, and a second port ID.

Optionally, the link discovery data packet may further include: a first domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs; and the processor 810 may be specifically configured to: determine the The first domain ID included in the link discovery packet is different from the domain ID of the domain under which the second primary controller is located.

Optionally, the processor 810 is specifically configured to: determine that the first switch indicated by the first switch ID is not a switch of a domain that is controlled by the second primary controller.

Optionally, the processor 810 is further configured to: after determining that the link discovery data packet is not a link discovery data packet of the local domain, adding the second switch ID and the second port ID to the border switch management information. in.

In this embodiment, the second main controller receives the topology discovery packet sent by the second switch, and determines that the link discovery data packet in the topology discovery packet is not the link discovery data packet of the local domain, and generates the packet according to the topology discovery packet. The report information is sent to the global topology agent, so that the global topology agent discovers the inter-domain topology link according to the report information, thereby providing data support for the global topology agent to discover the cross-domain global topology link. Hold, enabling the global topology agent to discover cross-domain global topology links.

9 is a schematic structural diagram of a base station according to an embodiment of the present invention. The base station 900 includes: a processor 910, a memory 920, a transceiver 930, and a bus 940.

The processor 910, the memory 920, and the transceiver 930 are connected to each other through a bus 940; the bus 940 may be an ISA bus, a PCI bus, or an 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 memory 920 is configured to store a program. In particular, the program can include program code, the program code including computer operating instructions. Memory 920 may include high speed RAM memory and may also include non-volatile memory, such as at least one disk memory.

The transceiver 930 is used to connect other devices and communicate with other devices. The transceiver 930 is configured to: receive the report information sent by the second main controller, where the report information includes: a first switch ID, a first port ID, a second switch ID, and a second port ID; And indicating to the first switch that sends the link discovery data packet, where the second switch ID is used to indicate that a second switch that receives the link discovery data packet is used, where the first port ID is used to indicate the A switch sends a port of the link discovery data packet, where the second port ID is used to indicate that the second switch receives the port of the link discovery data packet.

The processor 910 executes the program code, and is configured to discover an inter-domain topology link according to the report information.

Optionally, the processor 910 is specifically configured to:

Optionally, the reporting information may further include: a first domain ID, a second domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs, and the second domain ID is used to indicate the The second switch belongs to the domain; the processor 910 is specifically configured to: determine, according to the first domain ID, the first switch ID, and the first port ID, the first end of the inter-domain topology link, according to the first The second domain ID, the second switch ID, and the second port ID determine a second end of the inter-domain topology link.

It will be apparent to those skilled in the art that the techniques in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution in the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM. , a disk, an optical disk, etc., including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or portions of the embodiments.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

The embodiments of the invention described above are not intended to limit the scope of the invention. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

A topology discovery method, comprising:

The second main controller receives the topology discovery packet sent by the second switch, where the topology discovery packet includes: a link discovery data packet received by the second switch, a second switch ID, and a second port ID; The link discovery data packet includes: a first switch ID, a first port ID; the first switch ID is used to indicate a first switch that sends the link discovery data packet to the second switch, and the second switch The ID is used to indicate the second switch that receives the link discovery data packet, where the first port ID is used to indicate that the first switch sends the port of the link discovery data packet, and the second port ID is a port for instructing the second switch to receive the link discovery data packet;

When the second primary controller determines that the link discovery data packet is not the link discovery data packet of the local domain, the second primary controller generates the report information according to the topology discovery packet, where the report information includes: a first switch ID, and a first a port ID, a second switch ID, and a second port ID;

The second main controller sends the report information to the global topology agent, so that the global topology agent discovers the inter-domain topology link according to the report information.
The method according to claim 1, wherein the link discovery data packet further comprises: a first domain ID, the first domain ID is used to indicate a domain to which the first switch belongs; and the second primary The controller determines that the link discovery data packet is not a link discovery data packet of the local domain, and includes:

The second main controller determines that the first domain ID included in the link discovery data packet is different from the domain ID of the domain under which the second primary controller is located.
The method according to claim 1, wherein the second main controller determines that the link discovery data packet is not a link discovery data packet of the local domain, and includes:

The second main controller determines that the first switch indicated by the first switch ID is not a switch of a domain under the second main controller.
The method according to any one of claims 1 to 3, wherein after the second main controller determines that the link discovery data packet is not a link discovery data packet of the local domain, the second main controller further includes:

The second main controller adds the second switch ID and the second port ID to the border switch management information.
A topology discovery method, comprising:

The global topology proxy receives the report information sent by the second primary controller, where the report information includes: a switch ID, a first port ID, a second switch ID, and a second port ID; the first switch ID is used to indicate a first switch that sends the link discovery data packet, and the second switch ID is used to indicate reception a second switch of the link discovery data packet, where the first port ID is used to indicate that the first switch sends the port of the link discovery data packet, and the second port ID is used to indicate the Receiving, by the second switch, a port of the link discovery data packet;

The global topology agent discovers an inter-domain topology link according to the reported information.
The method according to claim 5, wherein after the global topology agent discovers the inter-domain topology link according to the reported information, the method further includes:

The global topology agent controls the first switch or the second switch to perform inter-domain data packet forwarding according to the inter-domain topology link.
The method according to claim 5 or 6, wherein the global topology agent discovers an inter-domain topology link according to the reported information, including:

Determining, by the global topology agent, the domain to which the first switch belongs according to the first switch ID, and determining a domain to which the second switch belongs according to the second switch ID;

Determining, by the global topology agent, the first end of the inter-domain topology link according to the domain to which the first switch belongs, the first switch ID, and the first port ID, according to the domain to which the second switch belongs, the second switch ID, and The second port ID determines the second end of the inter-domain topology link.
The method according to claim 5 or 6, wherein the report information further includes: a first domain ID and a second domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs. The second domain ID is used to indicate the domain to which the second switch belongs; the global topology proxy discovers the inter-domain topology link according to the reported information, including:

Determining, by the global topology proxy, the first end of the inter-domain topology link according to the first domain ID, the first switch ID, and the first port ID, according to the second domain ID, the second switch ID, and the second The port ID determines the second end of the inter-domain topology link.
A main controller, comprising:

a receiving unit, configured to receive a topology discovery packet sent by the second switch, where the topology discovery packet includes: a link discovery data packet, a second switch ID, and a second port ID received by the second switch; The link discovery data packet includes: a first switch ID, a first port ID; the first switch ID is used to indicate a first switch that sends the link discovery data packet to the second switch, and the second switch The ID is used to indicate the second switch that receives the link discovery data packet, where the first port ID is used to indicate that the first switch sends the port of the link discovery data packet, and the second port The ID is used to indicate that the second switch receives the port of the link discovery data packet;

a generating unit, configured to: when the link discovery data packet received by the receiving unit is not a link discovery data packet of the local domain, generate report information according to the topology discovery packet, where the report information includes: a switch ID, a first port ID, a second switch ID, and a second port ID;

And a sending unit, configured to send the report information generated by the generating unit to a global topology agent, so that the global topology agent discovers an inter-domain topology link according to the reported information.
The master controller according to claim 9, wherein the link discovery data packet further comprises: a first domain ID, the first domain ID is used to indicate a domain to which the first switch belongs; The unit is specifically used to:

Determining that the first domain ID included in the link discovery data packet is different from the domain ID of the domain controlled by the second primary controller.
The main controller according to claim 9, wherein the generating unit is specifically configured to:

Determining that the first switch indicated by the first switch ID is not a switch of a domain controlled by the second primary controller.
The main controller according to any one of claims 9 to 11, further comprising:

And a management unit, configured to: after the generating unit determines that the link discovery data packet is not a link discovery data packet of the local domain, adding the second switch ID and the second port ID to the boundary switch management information.
A global topology agent, comprising:

a receiving unit, configured to receive report information sent by the second main controller, where the report information includes: a first switch ID, a first port ID, a second switch ID, and a second port ID; the first switch ID is used by And indicating a first switch that sends the link discovery data packet, where the second switch ID is used to indicate that a second switch that receives the link discovery data packet is used, where the first port ID is used to indicate the first switch The switch sends the port of the link discovery data packet, where the second port ID is used to indicate that the second switch receives the port of the link discovery data packet;

And a determining unit, configured to discover an inter-domain topology link according to the report information received by the receiving unit.
The global topology agent according to claim 13, further comprising:

And a control unit, configured to control the first switch or the second switch to perform inter-domain data packet forwarding according to the inter-domain topology link discovered by the determining unit.
The global topology agent according to claim 13 or 14, wherein the determining unit is specifically configured to:

Determining, according to the first switch ID, a domain to which the first switch belongs, and determining, according to the second switch ID, a domain to which the second switch belongs;

Determining, according to the domain to which the first switch belongs, the first switch ID, and the first port ID, the first end of the inter-domain topology link, according to the domain to which the second switch belongs, the second switch ID, and the second port ID The second end of the inter-domain topology link.
The global topology agent according to claim 13 or 14, wherein the report information further includes: a first domain ID and a second domain ID, where the first domain ID is used to indicate a domain to which the first switch belongs. The second domain ID is used to indicate the domain to which the second switch belongs; the determining unit is specifically configured to:

Determining, according to the first domain ID, the first switch ID, and the first port ID, a first end of the inter-domain topology link, determining, according to the second domain ID, the second switch ID, and the second port ID The second end of the inter-domain topology link.