WO2015017974A1

WO2015017974A1 - Topology generating method, virtual cluster and controller

Info

Publication number: WO2015017974A1
Application number: PCT/CN2013/080894
Authority: WO
Inventors: 王军; 杨大鹏
Original assignee: 华为技术有限公司
Priority date: 2013-08-06
Filing date: 2013-08-06
Publication date: 2015-02-12
Also published as: CN103891218A

Abstract

The present invention provides a topology generating method, a virtual cluster and a controller. The method comprises: receiving, by a controller, local physical connecting information of an FP (forward point) transmitted from the FP; binding, by the controller, physical connection between every two FPs according to the physical connecting information to generate logical connection; and generating, by the controller, logical connection topology according to the physical connection and the logical connection, wherein the logical connection topology or the physical connection topology composed of the physical connection is used for computing routing. The technical solution provided by the present invention is used for improving the topology generating efficiency in the virtual cluster.

Description

Topology generation method, virtual cluster and controller

【技术领域】[Technical Field]

The present invention relates to the field of Internet communications, and in particular, to a topology generation method, a virtual cluster, and a controller.

【背景技术】【Background technique】

Figure 1 is a networking diagram of a virtual cluster. Refer to Figure 1. The virtual cluster includes the controller and FP (Forward). Point, forwarding node), the edge FP receives the protocol packet from the out-of-cluster device and reports it to the controller. The controller internally processes the protocol packet and sends the protocol packet to the out-of-cluster device through the other edge FP. Figure 2 is a logical connection diagram of a virtual cluster. Referring to Figure 2, the topology of the virtual cluster is fully connected to the edge FP. The internal FP is not exposed. The edge FPs are logically connected through vFabric, such as MPLS. Multi Protocol Label System, a multi-protocol label switching tunnel or MPLS tunnel group.

At present, the virtual cluster internally relies on the MPLS path to implement data forwarding, and the CSPF inside the virtual cluster (Constrained) Shortest Path First, the constraint shortest path first) When calculating the virtual path of the virtual cluster, the entity only depends on the logical connection of the virtual cluster. For the schematic diagram of the logical connection topology of the virtual cluster, refer to Figure 3. However, the CSPF entity is inside the virtual cluster. For the specific path, you need to refer to the physical connection of the virtual cluster. For the schematic diagram of the physical connection topology of the virtual cluster, refer to Figure 4, so the controller's ISIS (Intermediate) System to Intermediate System, intermediate system to intermediate system) The entity needs to publish two topologies to the controller's CSPF entity. The existing ISIS multi-topology is mainly used to plan the traffic and differentiate the different topologies of the service based on the actual network topology. The different topologies are advertised to the corresponding users. The ISIS multi-topology technology can implement the virtual cluster. Multi-topology release.

At present, ISIS multi-topology technology has the following disadvantages:

1. It is necessary to manually deploy and configure multiple topologies on each FP of the virtual cluster, which results in high hardware implementation cost of the virtual cluster, and the deployment and configuration of multiple topologies also consumes more labor costs.

2. Neighbor nodes that issue multi-topology ISIS modules need to negotiate to generate their own neighbor nodes according to the topology. Each node needs to collect corresponding connections for each topology and flood the collected connections in the virtual cluster. The amount of information that needs to be processed is very large, resulting in lower processing efficiency of the nodes.

3. When the physical connection of the node changes, the node needs to respond to the change of the physical connection, that is, regain the logical connection according to the change of the physical connection, and then report the new logical connection to the ISIS module of the controller, and the ISIS module The original physical connection topology and the logical connection topology are adjusted according to the changed physical connection and the logical connection. Therefore, when the physical connection changes, the node first adjusts, and then the ISIS module performs topology adjustment according to the changed connection. Finally, The adjusted topology is flooded out by adjacent FPs, which causes the controller's ISIS module to be inefficient in responding to topology changes caused by physical connection changes.

【发明内容】 [Summary of the Invention]

In view of this, the embodiment of the present invention provides a topology generation method, a virtual cluster, and a controller, so as to improve topology generation efficiency in a virtual cluster.

In a first aspect, an embodiment of the present invention provides a virtual cluster, where the virtual cluster includes: a forwarding node and a controller;

The forwarding node FP is configured to acquire local physical connection information, and flood the physical connection information to the controller.

The controller is configured to bundle a physical connection between each two FPs according to the physical connection information to generate a logical connection; generate a logical connection topology according to the physical connection and the logical connection; A physical connection topology consisting of a connection topology or the physical connection is used to calculate the route.

In a first possible implementation of the first aspect, The controller is further configured to store the physical connection topology formed by the logical connection topology and the physical connection, and the stored logical connection topology and the physical connection topology are distinguished by a value of a flag bit.

In a second possible implementation manner of the first aspect, the flooding the physical connection information to the controller includes:

After obtaining the local physical connection information, the FP floods the physical connection information to the controller through an ISIS message;

The ISIS message carries the identifier of the FP, the interface index of the FP, the identifier of the FP peer node, and the interface index of the FP peer node.

In a third possible implementation manner of the first aspect, the bundling the physical connection between each two of the FPs to generate a logical connection includes:

When there are more than two physical connections between the two FPs, the two physical interfaces of the FP are bundled into one logical interface, and the bandwidth between the logical interfaces after the binding is equal to the original two. The sum of the bandwidths between the physical connections described above;

When there is one physical connection between two of the FPs, one of the logical interfaces is generated, and a bandwidth between the logical interfaces is equal to a bandwidth of the original one of the physical connections.

In a fourth possible implementation manner of the first aspect, the logical connection topology includes an identifier of the FP, a logical interface index of the FP, an identifier of the FP peer node, and an FP peer node Logical interface index.

In conjunction with the first possible implementation of the first aspect, the controller is further configured to: after obtaining the logical connection topology, advertise the logical connection topology or the physical connection topology to a pre-subscribed topology Calculation module; or,

The controller is further configured to: after receiving the topology request of the node, distinguish the physical connection topology from the logical connection topology according to the value of the flag bit, and issue the topology requested by the route calculation module to the Used by the routing calculation module; or,

The controller is further configured to: after receiving the topology request of the route calculation module, issue the physical connection topology and the logical connection topology to the requested route calculation module, where the route calculation module is configured according to the The flag bits distinguish the topology.

In a second aspect, an embodiment of the present invention provides a controller, where the controller includes: a receiving module, a binding processing module, and an ISIS module;

The receiving module is configured to receive local physical connection information of the FP that is sent by the FP;

The binding processing module is configured to bundle a physical connection between each two FPs according to the physical connection information to generate a logical connection;

The ISIS module is configured to generate a logical connection topology according to the physical connection and the logical connection; the logical connection topology or a physical connection topology composed of the physical connection is used to calculate a route.

In a first possible implementation manner of the second aspect, the controller further includes:

The storage module is further configured to store the logical connection topology and the physical connection topology formed by the physical connection, and the stored logical connection topology and the physical connection topology are distinguished by a value of a flag bit.

In a second possible implementation manner of the second aspect, the bundling the physical connection between each two of the FPs to generate a logical connection includes:

In a third possible implementation manner of the second aspect, the logical connection topology includes an identifier of the FP, a logical interface index of the FP, an identifier of the FP peer node, and an FP peer node Logical interface index.

In conjunction with the first possible implementation of the second aspect, the controller further includes a topology publishing module:

The topology publishing module is configured to advertise the logical connection topology or the physical connection topology to a route calculation module of a pre-subscribed topology after obtaining the logical connection topology; or

The topology issuance module is configured to: after receiving the topology request of the node, distinguish the physical connection topology from the logical connection topology according to the value of the flag bit, and issue the topology requested by the route calculation module to the Used by the routing calculation module; or,

The topology publishing module is configured to: after receiving the topology request of the route calculation module, the physical connection topology and the logical connection topology are advertised to the requested route calculation module, where the route calculation module is configured according to the The flag bits distinguish the topology.

In a third aspect, an embodiment of the present invention provides a topology generation method, where the method includes:

The controller receives the physical connection information of the FP locally sent by the FP;

The controller bundles the physical connection between each two of the FPs according to the physical connection information to generate a logical connection;

The controller generates a logical connection topology according to the physical connection and the logical connection; the logical connection topology or a physical connection topology composed of the physical connection is used to calculate a route.

In a first possible implementation manner of the third aspect, the method further includes:

The controller stores the logical connection topology and the physical connection topology composed of the physical connection, and the stored logical connection topology and the physical connection topology are distinguished by a value of a flag bit.

In a second possible implementation manner of the third aspect, the controller receives the physical connection information of the FP that is sent by the FP, including:

In a third possible implementation manner of the third aspect, the bundling the physical connection between each two of the FPs to generate a logical connection includes:

In a fourth possible implementation manner of the third aspect, the logical connection topology includes an identifier of the FP, a logical interface index of the FP, an identifier of the FP peer node, and an FP peer node Logical interface index.

In conjunction with the second possible implementation of the third aspect, the method further includes:

After obtaining the logical connection topology, the controller issues the logical connection topology or the physical connection topology to a route calculation module of a pre-subscribed topology; or

After receiving the topology request of the node, the controller distinguishes the physical connection topology from the logical connection topology according to the value of the flag bit, and advertises the topology requested by the route calculation module to the route calculation module. Use; or,

After receiving the topology request of the route calculation module, the controller issues the physical connection topology and the logical connection topology to the requested route calculation module, and the route calculation module performs the topology according to the flag bit. Make a distinction.

Through the foregoing technical solution, the controller generates a logical connection topology according to the physical connection topology. Therefore, the FP only needs to collect and flood the collected physical connection information, and does not need to collect logical connection information, thereby improving topology generation in the virtual cluster. effectiveness.

【附图说明】 [Description of the Drawings]

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in 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. One of ordinary skill in the art can also obtain other drawings based on these drawings without paying for inventive labor.

1 is a schematic diagram of networking of a virtual cluster;

2 is a logical connection diagram of a virtual cluster;

3 is a schematic diagram of a logical connection topology of a virtual cluster;

4 is a schematic diagram of a physical connection topology of a virtual cluster;

FIG. 5 is a functional block diagram of a virtual cluster according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic flowchart diagram of a topology generation method according to an embodiment of the present invention;

7 is a schematic diagram of generating a logical connection for physical connection bundling according to an embodiment of the present invention;

FIG. 8 is a functional block diagram of a controller according to an embodiment of the present invention; FIG.

FIG. 9 is a schematic structural diagram of a controller according to an embodiment of the present invention.

【具体实施方式】【detailed description】

For a better understanding of the technical solutions of the present invention, the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

It should be understood that the described embodiments are only a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The embodiment of the present invention provides a virtual cluster. Referring to FIG. 5, it is a functional block diagram of a virtual cluster according to an embodiment of the present invention. As shown in FIG. 5, the virtual cluster includes: FP. 51. Controller 52.

A method for generating a topology is provided in the embodiment of the present invention. Please refer to FIG. 6 , which is a schematic flowchart of a method for generating a topology according to an embodiment of the present invention. As shown in FIG. 6 , the method includes the following steps:

Step 601: The controller receives the physical connection information of the FP locally sent by the FP.

Specifically, referring to FIG. 4, the ISIS module is pre-configured on each FP in the virtual cluster. After the ISIS module is started, the hello message is broadcasted in the virtual cluster to establish a neighbor relationship with other nodes in the virtual cluster. After the neighbor relationship is established, the two nodes with the neighbor relationship send their related information to the peer node. The related information includes the identifier of the node and the interface index that establishes a physical connection with the peer node. And the interface index, the ISIS module of the FP obtains a local physical connection, where the physical connection includes an interface index of the FP itself and an interface index of the FP peer node; wherein the FP can establish a neighbor with a controller or other FP in the virtual cluster. relationship.

After obtaining the local physical connection, the ISIS module of the FP floods the local physical connection information to the controller of the virtual cluster through the ISIS message, where the ISIS message carries the identifier of the FP, the interface index of the FP itself, The identifier of the FP peer node and the interface index of the FP peer node; the identifier of the FP may be an IP address of the FP.

Step 602: The controller bundles a physical connection between each two of the FPs according to the physical connection information to generate a logical connection.

Specifically, the receiving module of the controller receives the physical connection information reported by the ISIS module of each FP, and then sends the physical connection information to the binding processing module of the controller, and the binding processing module according to the physical connection information collected by the ISIS module. , the physical connection topology that makes up the virtual cluster.

Referring to FIG. 7 , in the physical connection topology of the virtual cluster, there are one physical connection or two physical connections between the two FPs for the two FPs that establish the neighbor relationship. In the embodiment of the present invention, two FPs are used. The two or more physical connections are bundled to generate a logical connection. The binding of the physical connections between the two FPs means that two or more physical interfaces between the two FPs are bundled together as a logical interface. Use and superimpose the bandwidth between two or more physical interfaces; therefore, after the physical connection is bundled, there is one logical connection between each two FPs, and each end of each logical connection is an FP. The bandwidth of the logical connection is equal to the sum of the bandwidths of the two or more physical connections that are bundled. To ensure the integrity of the logical connection topology, a logical interface is directly generated for the case where there is only one physical connection between the two FPs. The logical connection between two FPs, the bandwidth of the logical connection is equal to the bandwidth of the original physical connection.

Step 603: The controller generates a logical connection topology according to the physical connection and the logical connection; the logical connection topology or the physical connection topology formed by the physical connection is used to calculate a route.

Specifically, after the logical connection is generated, the ISIS module of the controller can directly generate a logical connection topology according to the physical connection and the generated logical connection, and the logical connection topology includes an identifier of the FP, a logical interface index of the FP, and an FP peer node. The logical interface index of the FP peer node, where the FP identifier can be obtained from the physical connection, and the logical interface index can be randomly generated or allocated in order, as long as the logical interface index of the node in the virtual cluster is unique.

The ISIS module of the controller saves the logical connection topology and the original physical connection topology after the logical connection topology of the virtual cluster is generated. In the embodiment of the present invention, the saved logical connection topology and the physical connection topology pass the flag bit ( The value of flag is distinguished. For example, a flag equal to 1 indicates that the connection between the nodes is a physical connection, and a flag equal to 0 indicates that the connection between the nodes is a logical connection.

For the generated logical connection topology and physical connection topology, the route calculation module in the virtual cluster, such as the CSPF entity of the controller, can subscribe to the ISIS module of the controller in advance. After the ISIS module obtains the logical connection topology and the physical connection topology, The topology is published to the subscribed route calculation module; or when the route calculation module needs to use the physical connection topology or the logical connection topology, the ISIS module can initiate a request to the controller, and the ISIS module distinguishes the physical connection topology and the logical connection topology according to the flag. Then, the topology requested by the route calculation module is advertised to the route calculation module; if the route calculation module requests to obtain the physical connection topology and the logical connection topology, the ISIS module passes the locally saved physical connection topology and the logical connection topology through the private TLV (Tag). The -Length-Value, label-length-value information is advertised to the requesting route calculation module, and the route calculation module distinguishes the topology by itself according to the flag in the private TLV information. After obtaining the logical connection topology or the physical connection topology formed by the physical connection, the route calculation module may calculate the route according to the logical connection topology or the physical connection topology.

Referring to FIG. 5, as shown in the figure, in the virtual cluster provided by the embodiment of the present invention:

The forwarding node FP51 is configured to acquire local physical connection information, and flood the physical connection information to the controller 52;

The controller 52 is configured to bundle a physical connection between each two FPs according to the physical connection information to generate a logical connection, and generate a logical connection topology according to the physical connection and the logical connection; A logical connection topology or a physical connection topology composed of the physical connections is used to calculate routes.

In the virtual cluster:

The controller 52 is further configured to store the physical connection topology formed by the logical connection topology and the physical connection, and the stored logical connection topology and the physical connection topology are distinguished by a value of a flag bit.

The flooding the physical connection information to the controller includes:

After obtaining the local physical connection information, the FP 51 floods the physical connection information to the controller 52 through an ISIS message;

The binding of the physical connection between each two of the FPs to generate a logical connection includes:

The logical connection topology includes an identifier of the FP, a logical interface index of the FP, an identifier of the FP peer node, and a logical interface index of the FP peer node.

In the virtual cluster:

The controller 52 is further configured to: after obtaining the logical connection topology, publish the logical connection topology or the physical connection topology to a route calculation module of a pre-subscribed topology; or

The controller 52 is further configured to: after receiving the topology request of the node, distinguish the physical connection topology from the logical connection topology according to the value of the flag bit, and issue the topology requested by the route calculation module to the topology The routing calculation module uses; or,

The controller 52 is further configured to: after receiving the topology request of the route calculation module, the physical connection topology and the logical connection topology are advertised to the requested route calculation module, where the route calculation module is The flag bits distinguish the topology.

It should be noted that, in the functional block diagram of the virtual cluster shown in FIG. 5, only one FP is represented, and the system does not include only one FP. In the embodiment of the present invention, the virtual cluster may include more than one FP. FP.

Please refer to FIG. 8. FIG. 8 is a functional block diagram of a controller according to an embodiment of the present invention. As shown in the figure, the controller provided by the embodiment of the present invention includes: a receiving module 81, a binding processing module 82, and an ISIS module. 83; Among them,

The receiving module 81 is configured to receive local physical connection information of the FP that is sent by the FP.

The binding processing module 82 is configured to bundle a physical connection between each two FPs according to the physical connection information to generate a logical connection;

The ISIS module 83 is configured to generate a logical connection topology according to the physical connection and the logical connection; the logical connection topology or a physical connection topology composed of the physical connection is used to calculate a route.

The controller further includes:

The storage module 84 is further configured to store the logical connection topology and the physical connection topology formed by the physical connection, and the stored logical connection topology and the physical connection topology are distinguished by a value of a flag bit.

The controller also includes a topology publishing module 85:

The topology publishing module 85 is configured to advertise the logical connection topology or the physical connection topology to a route calculation module of a pre-subscribed topology after obtaining the logical connection topology; or

The topology publishing module 85 is configured to: after receiving the topology request of the node, distinguish the physical connection topology from the logical connection topology according to the value of the flag bit, and issue the topology requested by the route calculation module to the topology The routing calculation module uses; or,

The topology publishing module 85 is configured to: after receiving the topology request of the route calculation module, the physical connection topology and the logical connection topology are advertised to the requested route calculation module, where the route calculation module is The flag bits distinguish the topology.

Please refer to FIG. 9 , which is a schematic structural diagram of a controller according to an embodiment of the present invention. As shown in the figure, the controller includes:

a receiver 91, configured to receive local physical connection information of the FP sent by the FP;

a memory 92, configured to store information including a program routine;

The processor 93 is coupled to the memory 92 and the receiver 91 for controlling the execution of the program routine, and specifically includes: bundling and generating logic for the physical connection between each of the two FPs according to the physical connection information. Connecting; generating a logical connection topology according to the physical connection and the logical connection; the logical connection topology or a physical connection topology composed of the physical connection is used to calculate a route.

The technical solution of the embodiment of the invention has the following beneficial effects:

1. The controller generates a logical connection topology based on the physical connection topology. Therefore, the FP only needs to collect and flood the collected physical connections, and does not need to collect logical connections. Therefore, the topology generation efficiency in the virtual cluster can be improved.

2. For a node that needs to generate a logical connection topology, the controller only needs to publish the generated logical connection topology to the route calculation module. It is not necessary to deploy and configure multiple topologies on each node of the virtual cluster. The hardware implementation cost of the cluster saves manpower and material resources.

3. The physical connection topology and the logical connection topology can be obtained only by collecting the physical connection information. Therefore, the neighbors of the controller do not need to negotiate neighbors according to multiple topologies. Each node only needs to release its physical connection information to the controller. Local routing calculations are required to reduce the amount of information processed by the nodes and improve the processing efficiency of the nodes.

4. When the physical connection of the node changes, the node only needs to report the changed physical connection information to the controller. The controller adjusts the physical connection topology and the logical connection topology according to the changed physical connection information, thereby greatly improving the controller pair. The response efficiency of physical connection changes.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are made within the spirit and principles of the present invention, should be included in the present invention. Within the scope of protection.

Claims

A virtual cluster, the virtual cluster includes: a forwarding node and a controller; wherein

The forwarding node FP is configured to acquire local physical connection information, and flood the physical connection information to the controller.

The controller is configured to bundle a physical connection between each two FPs according to the physical connection information to generate a logical connection; generate a logical connection topology according to the physical connection and the logical connection; A physical connection topology consisting of a connection topology or the physical connection is used to calculate the route.
The virtual cluster of claim 1 wherein:

The controller is further configured to store the physical connection topology formed by the logical connection topology and the physical connection, and the stored logical connection topology and the physical connection topology are distinguished by a value of a flag bit.
The virtual cluster according to claim 1, wherein the flooding the physical connection information to the controller comprises:

After obtaining the local physical connection information, the FP floods the physical connection information to the controller through an ISIS message;

The ISIS message carries the identifier of the FP, the interface index of the FP, the identifier of the FP peer node, and the interface index of the FP peer node.
The virtual cluster according to claim 1, wherein the bundling the physical connection between each of the two FPs to generate a logical connection comprises:

When there are more than two physical connections between the two FPs, the two physical interfaces of the FP are bundled into one logical interface, and the bandwidth between the logical interfaces after the binding is equal to the original two. The sum of the bandwidths between the physical connections described above;

When there is one physical connection between two of the FPs, one of the logical interfaces is generated, and a bandwidth between the logical interfaces is equal to a bandwidth of the original one of the physical connections.
The virtual cluster according to claim 1, wherein the logical connection topology includes an identifier of the FP, a logical interface index of the FP, an identifier of the FP peer node, and an FP peer node. Logical interface index.
The virtual cluster of claim 2, wherein

The controller is further configured to: after obtaining the logical connection topology, publish the logical connection topology or the physical connection topology to a route calculation module of a pre-subscribed topology; or

The controller is further configured to: after receiving the topology request of the node, distinguish the physical connection topology from the logical connection topology according to the value of the flag bit, and issue the topology requested by the route calculation module to the Used by the routing calculation module; or,

The controller is further configured to: after receiving the topology request of the route calculation module, issue the physical connection topology and the logical connection topology to the requested route calculation module, where the route calculation module is configured according to the The flag bits distinguish the topology.
A controller, comprising: a receiving module, a binding processing module, and an ISIS module; wherein

The receiving module is configured to receive local physical connection information of the FP that is sent by the FP;

The binding processing module is configured to bundle a physical connection between each two FPs according to the physical connection information to generate a logical connection;

The ISIS module is configured to generate a logical connection topology according to the physical connection and the logical connection; the logical connection topology or a physical connection topology composed of the physical connection is used to calculate a route.
The controller according to claim 7, wherein the controller further comprises:

The storage module is further configured to store the logical connection topology and the physical connection topology formed by the physical connection, and the stored logical connection topology and the physical connection topology are distinguished by a value of a flag bit.
The controller according to claim 7, wherein the bundling the physical connection between each two of the FPs to generate a logical connection comprises:

When there are more than two physical connections between the two FPs, the two physical interfaces of the FP are bundled into one logical interface, and the bandwidth between the logical interfaces after the binding is equal to the original two. The sum of the bandwidths between the physical connections described above;

When there is one physical connection between two of the FPs, one of the logical interfaces is generated, and a bandwidth between the logical interfaces is equal to a bandwidth of the original one of the physical connections.
The controller according to claim 7, wherein the logical connection topology includes an identifier of the FP, a logical interface index of the FP, an identifier of the FP peer node, and an FP peer node. Logical interface index.
The controller according to claim 8, wherein the controller further comprises a topology publishing module:

The topology publishing module is configured to advertise the logical connection topology or the physical connection topology to a route calculation module of a pre-subscribed topology after obtaining the logical connection topology; or

The topology issuance module is configured to: after receiving the topology request of the node, distinguish the physical connection topology from the logical connection topology according to the value of the flag bit, and issue the topology requested by the route calculation module to the Used by the routing calculation module; or,

The topology publishing module is configured to: after receiving the topology request of the route calculation module, the physical connection topology and the logical connection topology are advertised to the requested route calculation module, where the route calculation module is configured according to the The flag bits distinguish the topology.
A topology generation method, the method comprising:

The controller receives the physical connection information of the FP locally sent by the FP;

The controller bundles the physical connection between each two of the FPs according to the physical connection information to generate a logical connection;

The controller generates a logical connection topology according to the physical connection and the logical connection; the logical connection topology or a physical connection topology composed of the physical connection is used to calculate a route.
The method of claim 12, wherein the method further comprises:

The controller stores the logical connection topology and the physical connection topology composed of the physical connection, and the stored logical connection topology and the physical connection topology are distinguished by a value of a flag bit.
The method according to claim 12, wherein the controller receives the physical connection information of the FP locally sent by the FP, including:

After obtaining the local physical connection information, the FP floods the physical connection information to the controller through an ISIS message;

The ISIS message carries the identifier of the FP, the interface index of the FP, the identifier of the FP peer node, and the interface index of the FP peer node.
The method according to claim 12, wherein the bundling the physical connection between each two of the FPs to generate a logical connection comprises:

When there are more than two physical connections between the two FPs, the two physical interfaces of the FP are bundled into one logical interface, and the bandwidth between the logical interfaces after the binding is equal to the original two. The sum of the bandwidths between the physical connections described above;

When there is one physical connection between two of the FPs, one of the logical interfaces is generated, and a bandwidth between the logical interfaces is equal to a bandwidth of the original one of the physical connections.
The method according to claim 12, wherein the logical connection topology comprises an identifier of the FP, a logical interface index of the FP, an identifier of the FP peer node, and a logic of the FP peer node. Interface index.
The method of claim 13 wherein the method further comprises:

After obtaining the logical connection topology, the controller issues the logical connection topology or the physical connection topology to a route calculation module of a pre-subscribed topology; or

After receiving the topology request of the node, the controller distinguishes the physical connection topology from the logical connection topology according to the value of the flag bit, and advertises the topology requested by the route calculation module to the route calculation module. Use; or,

After receiving the topology request of the route calculation module, the controller issues the physical connection topology and the logical connection topology to the requested route calculation module, and the route calculation module performs the topology according to the flag bit. Make a distinction.