WO2019128612A1 - Method and device for processing routing protocol packet - Google Patents

Abstract

The embodiment of the present application discloses a method and a device for processing a routing protocol packet. The method is applied to a first network edge device of a first data center (DC). Before the first network edge device advertises a routing protocol packet to a second network edge device, adding a first network connection attribute identifier to the routing protocol packet, and after the routing protocol packet is used to enable the second network edge device to acquire information about the first routing protocol packet, determining, according to the first connection attribute identifier sequence of the routing protocol packet, whether there is the possibility of a loop in the route of the routing protocol packet. In the embodiment of the present application, a border network edge device can automatically determine, according to the network connection attribute identifier carried by the received routing protocol packet, whether there is the possibility of a loop in the route of the routing protocol packet, so that loops of routing protocol packets are avoided, thereby avoiding data packet loops.

Description

Routing protocol message processing method and device

This application claims the priority of the Chinese Patent Application filed on Dec. 25, 2017, the Chinese Patent Office, Application No. 201711425078.8, entitled "Processing Method and Apparatus for Routing Protocol Messages", the entire contents of which are incorporated herein by reference. In the application.

Technical field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for processing a routing protocol packet.

Background technique

With the rapid development of technologies such as cloud computing and big data, data centers (DCs) of various scale operations based on technologies such as cloud computing and virtualization have emerged, and data center networks (DCCs) ) Used to connect to various resources within the data center. In order to meet the scenarios of cross-regional operations and remote disaster recovery, more and more enterprises usually deploy multiple DCs in multiple regions. Different DCs need to interact with each other and need to exchange information with each other. The Data Center Interconnect (DCI) network is a solution for communicating between hosts (servers) in different DCs.

DCs are developed based on virtual local area network (VLAN) technologies, such as Virtual eXtensible Local Area Network (VXLAN), Stacked VLAN (QinQ), and Virtual Private LAN (Virtual). Private LAN Service, VPLS) network, etc.

At present, network edge devices used as Layer 3 gateways in different DCNs are configured to encapsulate Layer 2 data packets in Layer 3 packets and cross the middle Layer 3 network by establishing an Internet Protocol (IP) tunnel. Interworking of Layer 2 data between two DCNs. This tunnel is like a virtual bridge that connects multiple DC's Layer 2 networks together. For example, for VXLAN, the DC can be implemented by a three-stage VXLAN scheme, which implements a VXLAN tunnel (VXLAN-DCI tunnel) between two DC boundary VXLAN tunnel endpoints (VTEPs) to achieve DC between DCs. Communication, communication between hosts within the same DC can be achieved by establishing a VXLAN tunnel (VXLAN-DCN tunnel) between VTEPs within the DC. The VTEP is used to add a VXLAN tunnel header to the packet, obtain a VXLAN packet, or delete the VXLAN tunnel header from the VXLAN packet header to terminate the VXLAN tunnel.

In order to avoid routing loops and packet loss when a traditional IP tunnel transmits packets, the network edge device needs to support the horizontal splitting feature, that is, the network edge device receives the packet from a tunnel (VXLAN-DCI tunnel or VXLAN-DCN tunnel). The message will no longer be sent to another tunnel of the same type. However, in order to implement data forwarding between DC internal servers and between different DCs, it is necessary to turn off the horizontal splitting feature on the network edge device, but this may cause packets sent from one DC to return to the DC, which may result in There is a risk of loops when multiple DCs are interconnected.

Summary of the invention

The present invention provides a method and a device for processing a routing protocol packet, which can enable the network edge device to determine whether there is a loop of the routing of the protocol packet when receiving the routing protocol packet.

In a first aspect, the present application provides a method for processing a routing protocol packet, where the method is applied to a first network edge device of a first data center DC, where the first network edge device is a border network edge device or a non- Border network edge device. Before the first network edge device advertises the routing protocol packet to the second network edge device, the first network connection attribute identifier is added to the routing protocol packet, and the routing protocol packet is used to enable the second After learning the routing protocol packet, the network edge device determines, according to the first connection attribute identifier sequence of the routing protocol packet, whether there is a loop of the routing protocol packet. The second network edge device is a border network edge device, and the first network connection attribute identifier is a first identifier or a second identifier, where the first identifier is used to identify the first network edge device and the The second network edge device belongs to the same DC, and the second identifier is used to identify that the first network edge device and the second network edge device do not belong to the same DC, and the first connection attribute identification sequence is the routing protocol. And the sequence formed by the network connection attribute identifier added by each network edge device that is passed by the packet in the forwarding process, where the first connection attribute identification sequence includes the first network connection attribute identifier.

In this application, the network edge device of the DC adds the network connection attribute identifier between the edge device of the edge device of the network and the edge device of the peer end to the routing protocol packet before sending the routing protocol packet, thereby When receiving the routing protocol packet, the edge network edge device can automatically determine whether there is a loop risk of the routing protocol packet according to all the network connection attribute identifiers carried in the routing protocol packet. Through the application, the possibility of looping of data packet forwarding is avoided from the network control plane.

With reference to the first aspect, in a possible implementation, if the first network edge device is a border network edge device, before the first network edge device issues the first routing protocol packet to the second network edge device, The first network edge device receives the routing protocol packet, where the routing protocol packet carries the network connection attribute added by each network edge device that the routing protocol packet passes in the forwarding process. Logo. The first network edge device obtains a second connection attribute identification sequence according to the sequentially added network connection attribute identifier carried in the routing protocol packet, where the second connection attribute identification sequence does not include the first network connection Attribute ID. Determining, by the first network edge device, that the route of the routing protocol packet has a loop according to the second connection attribute identifier sequence; if the first network edge device determines that the route of the routing protocol packet does not exist If the loop is possible, the first network edge device adds the first network connection attribute identifier to the routing protocol message.

With reference to the first aspect, in a possible implementation, if the first network edge device determines that the route of the routing protocol packet is looped, the first network edge device discards the routing protocol packet. .

With reference to the first aspect, in a possible implementation, if the second connection attribute identification sequence satisfies the following first condition and the second condition, the first network edge device determines the routing protocol packet If the route is in the loop, if the second connection attribute identifier sequence is different, the first condition and the second condition are met, and the route of the routing protocol packet is determined to have no loop; the first condition is The number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three; the second condition is a network connection attribute in the connection attribute identification sequence except the first network connection attribute identifier and the last network connection attribute identifier. The first identifier is in the identifier, or the host network protocol IP address or the network segment IP address of the route carried in the routing protocol packet is an IP address connected to the non-boundary network edge device in the DC where the network edge device is located.

With reference to the first aspect, in a possible implementation manner, the first network connection attribute identifier is carried in a value field of an extended type length value TLV field of the routing protocol message.

With reference to the first aspect, in a possible implementation, before the adding the first network connection attribute identifier to the routing protocol packet, the first network edge device is configured according to the first network edge device. The network connection relationship attribute table determines the first network connection attribute identifier. The network connection relationship attribute table is configured to record a network connection attribute identifier between the first network edge device and a neighbor network edge device of the first network edge device, where the network connection relationship attribute table is based on the A data table of a neighbor relationship configuration of the network edge device, the neighbor network edge device including the second network edge device. .

In the present application, the first network edge device sends a routing protocol to its neighbor network edge device by using a data table in the network edge device for storing the network connection attribute identifier of the first network edge device and its first neighbor network edge device. When the packet is received, the corresponding network connection attribute identifier can be quickly determined according to the data table and added to the routing protocol packet, which improves the processing efficiency of the routing protocol packet.

With reference to the first aspect, in a possible implementation, each of the entries of the network connection relationship attribute table stores the first network edge device and a neighbor network edge device of the first network edge device. Corresponding relationship between the network connection attribute identifier and the IP address of the neighbor network edge device; the first network edge device searches for the IP address of the second network edge device in the network connection relationship attribute table The first network connection attribute identifier.

With reference to the first aspect, in a possible implementation manner, the virtual local area network is any one of the following networks: a VXLAN, a QinQ, and a VPLS network.

In a second aspect, the present application provides a method for processing a routing protocol packet, where the method is applied to a first network edge device of a first data center DC, where the first network edge device is a border network edge device.

The first network edge device receives a routing protocol message advertised by the second network edge device, where the second network edge device is a border network edge device of the second DC or the non-boundary network edge device of the first DC . The routing protocol packet carries a network connection attribute identifier that is added by each network edge device that the routing protocol packet passes in the forwarding process, and the network connection attribute identifier is a first identifier or a second identifier. The first identifier is used to identify that the network edge device that advertises the routing protocol packet and the network edge device that receives the routing protocol packet belong to the same DC, and the second identifier is used to identify that the routing protocol packet is advertised. The network edge device and the network edge device that receives the routing protocol packet do not belong to the same DC; the first network edge device obtains the connection attribute according to the sequentially added network connection attribute identifier carried in the routing protocol packet. And an identifier sequence; the first network edge device determines, according to the connection attribute identifier sequence, whether a route of the routing protocol packet has a loop possibility.

With reference to the second aspect, in a possible implementation, if the connection attribute identification sequence satisfies the following first condition and the second condition, the first network edge device determines that the route of the routing protocol message exists. The loop may be that if the connection attribute identification sequence is different, the first network condition and the second condition are met, and the first network edge device determines that the route of the routing protocol message does not have a loop. The first condition is that the number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three. The second condition is that the first identifier exists in the network connection attribute identifier of the connection attribute identifier sequence except the first network connection attribute identifier and the last network connection attribute identifier, or is carried in the routing protocol packet. The routed host network protocol IP address or network segment IP address is the IP address to which the non-boundary network edge device in the DC where the network edge device resides.

With reference to the second aspect, in a possible implementation, if the first network edge device determines that the route of the routing protocol packet does not exist in a loop according to the connection attribute identification sequence, the first network edge After the device adds the first network connection attribute identifier to the sequentially added network connection attribute identifier in the routing protocol packet, the first network edge device issues the added routing protocol packet to the third Network edge device. The first network connection attribute identifier is a network connection attribute identifier between the first network edge device and the third network edge device, and the third network edge device is a third DC border network edge device. Or the non-boundary network edge device of the first DC.

With reference to the second aspect, in a possible implementation, the first network edge device adds a first network connection attribute identifier to the routing protocol packet, and the first network edge device is configured according to the first a network connection relationship attribute table in the network edge device, where the first network connection attribute identifier is determined; wherein the network connection relationship attribute table is used to record a neighbor of the first network edge device and the first network edge device a network connection attribute identifier between the network edge devices, the network connection relationship attribute table is a data table configured based on a neighbor relationship of the first network edge device, and the neighbor network edge device includes the third network edge device.

With reference to the second aspect, in a possible implementation, each entry of the network connection relationship attribute table stores a network of the first network edge device and a neighbor network edge device of the first network edge device A connection attribute identifier corresponding to an IP address of the neighbor network edge device. The first network edge device searches, in the network connection relationship attribute table, a first network connection attribute identifier corresponding to an IP address of the third network edge device.

With reference to the second aspect, in a possible implementation manner, if the first network edge device determines that a route of the routing protocol packet exists in a loop according to the connection attribute identification sequence, the first network edge device Discard the routing protocol packet.

With reference to the second aspect, in a possible implementation manner, the network connection attribute identifier that is sequentially added by each network edge device is carried in a value field of an extended type length value TLV field of the routing protocol message.

In a third aspect, the present application provides a processing device for routing protocol messages, the processing device including functional modules for implementing the methods in the first aspect and various implementation manners thereof.

In a fourth aspect, the application provides a processing device for routing protocol messages, and the device includes functional modules for implementing the methods in the second aspect and various implementation manners thereof.

In a fifth aspect, the application provides a network edge device, the network edge device comprising a processor and a memory; the memory for storing executable computer program code; the processor for reading the computer program code A computer program corresponding to the computer program code is executed for performing a processing method of a routing protocol message in any of the possible embodiments of the first aspect of the present application.

In a sixth aspect, the present application provides a computer readable storage medium having stored therein computer instructions that, when executed on a computer, cause the computer to perform any of the first aspect of the present application A method for processing a routing protocol message in a possible implementation manner.

In a seventh aspect, the application provides a network edge device, the network edge device comprising a processor and a memory; the memory is configured to store executable computer program code; the processor is configured to read the The computer program code is operative to execute a computer program corresponding to the computer program code for performing a method of processing a routing protocol message in any of the possible embodiments of the second aspect of the present application.

In an eighth aspect, the present application provides a computer readable storage medium having stored therein computer instructions that, when executed on a computer, cause the computer to perform any of the second aspect of the present application A method for processing a routing protocol message in a possible implementation manner.

DRAWINGS

FIG. 1 is a schematic diagram showing a process in which two data centers forward messages through DCI;

2 is a schematic diagram showing a message forwarding loop in a plurality of data center interconnections;

FIG. 3 is a schematic diagram of a network architecture provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a network edge device according to an embodiment of the present disclosure;

FIG. 5 is a schematic flowchart diagram of a method for processing a routing protocol packet according to an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a BGP EVPN protocol packet of an extended type length value (TLV) field according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a TLV field according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a BGP EVPN protocol packet that extends two TLV fields according to an embodiment of the present application;

FIG. 9 is a schematic flowchart diagram of a method for processing a routing protocol packet according to an embodiment of the present application;

FIG. 10 is a schematic block diagram of a processing apparatus for routing protocol messages according to an embodiment of the present application;

FIG. 11 is a schematic block diagram of a processing apparatus for routing protocol messages according to another embodiment of the present application;

FIG. 12 is a schematic block diagram of a processing apparatus for a routing protocol message according to still another embodiment of the present application;

FIG. 13 is a schematic block diagram of a processing apparatus for routing protocol messages according to an embodiment of the present application;

FIG. 14 is a schematic block diagram of a processing apparatus for a routing protocol message according to still another embodiment of the present application;

FIG. 15 is a schematic block diagram of a processing apparatus for a routing protocol message according to still another embodiment of the present application;

FIG. 16 shows a schematic block diagram of a network edge device according to an embodiment of the present application.

Detailed ways

The embodiment of the present application provides a method, a device, a device, and a storage medium for processing a routing protocol packet, which can be used in a network edge device of a DC. The DC can adopt various network architectures such as a VXLAN, a QinQ, and a VPLS network. Network edge devices in the same DC communicate through DCN tunnels. Network edge devices of different DCs communicate through DCI tunnels. The method and device of the embodiments of the present application can identify network configuration errors and avoid network loops when DC interconnection occurs.

The network edge device may be a network edge device as an access device in the DC, or may be a network edge device in the DC for connecting to the DC. In this application, a network edge device that is an access device is referred to as a non-boundary network edge device, and a network edge device that is used to connect other DCs is referred to as a border network edge device.

It can be understood that the types and/or names of network edge devices may also be different for different types of virtual local area networks. For example, in VXLAN, a network edge device refers to a VTEP in a DC, and a network edge device in a DC may include a boundary VTEP and a non-boundary VTEP. For a QinQ network, a VPLS network, or a Transparent Interconnection of Lots of Links (TRILL) network, the network edge device is an operator network edge device, such as a provider edge (PE) and TRILL in a VPLS network. Edge routing bridge (RB) devices in the network. Correspondingly, the network edge device in the VPLS may include a border PE and a non-boundary PE, and the network edge device in the TRILL network may include a boundary RB and a non-edge RB.

FIG. 1 is a schematic diagram showing a process of forwarding a message between two DCs in a VXLAN through DCI. As shown in FIG. 1, A1, B1, C1, D1, and E1 are VTEPs in DC1, and A2, B2, C2, D2, and E2 are VTEPs in DC2. Among them, A1 and B1 are the boundary VTEP of DC1 connected to DC2 as DC1, C1, D1 and E1 are non-boundary VTEPs as access devices in DC1, and A2 and B2 are borders VTEP, C2 and D2 of DC2 connected to DC1 in DC2. And E2 is the non-boundary VTEP in DC2 as the access device. In VXLAN, two VTEPs communicate by establishing a VXLAN tunnel. Among them, in the VXLAN, the VTEP as the inter-DC connection device may be referred to as a bone node (Spine), and the VTEP as an access device may be referred to as a leaf node (Leaf).

In the network architecture shown in Figure 1, DC1 and DC2 can be interconnected in a three-stage manner. As shown in Figure 1, when the host 1 connected to D1 in DC1 needs to send packets to the host 2 connected to D2 in DC2, the forwarding path of the packet can be as shown by the arrow in Figure 1, and D1 is sent as the host 1. The first VXLAN tunnel header of the first packet added with the information of B1 obtains the first VXLAN packet, and the first VXLAN packet is sent to B1 through the VXLAN-DCN tunnel between D1 and B1, and the B1 deletes the first packet. The first VXLAN tunnel header of the VXLAN packet obtains the first packet, and the second VXLAN tunnel header including the B2 information is added to the first packet to obtain the second VXLAN packet, and the second VXLAN packet is obtained. The second VXLAN tunnel header of the second VXLAN packet is deleted by the VXLAN-DCI tunnel between B1 and B2, and the B2 deletes the second VXLAN tunnel header of the second VXLAN packet to obtain the first packet, and then adds the first packet to the first packet. The third VXLAN tunnel header of the D2 information obtains the third VXLAN packet, and the third VXLAN packet is sent to the D2 through the VXLAN-DCN tunnel between B2 and D2, and finally the third VXLAN packet is deleted by the D2. The third VXLAN tunnel header obtains the first packet and sends the first packet to the host 2 in the DC2.

If the VTEP supports the split horizon feature, after receiving the first VXLAN packet sent by D1 through the VXLAN-DCN tunnel, B1 will not pass the first VXLAN through the VXLAN-DCN tunnel in DC1. The message is sent to C1 or E1. Similarly, after receiving the second VXLAN message sent by B1 through the VXLAN-DCI tunnel, B2 will not send the second VXLAN message to other DCs through the VXLAN-DCI tunnel. Therefore, VTEP supporting horizontal splitting cannot achieve interconnection between multiple DCs.

In order to achieve forwarding between DCs and interconnection between multiple DCs, it is necessary to cancel the horizontal splitting feature on VTEP. However, the elimination of the split horizon feature may result in the risk of data forwarding loops when interconnecting multiple DCs. As shown in FIG. 2, when four data centers DC1, DC2, DC3, and DC4 are interconnected, 1, 2, 3, and 4 represent Spines of DC1, DC2, DC3, and DC4, respectively. If the configuration information of a certain Spine is incorrect, the message sent by DC1 as shown by the direction of the arrow in Figure 2 is forwarded back to DC1, and a network loop occurs. The processing method of the routing protocol packet provided by the embodiment of the present application effectively avoids the possibility of looping in the data plane packet forwarding from the network control plane.

FIG. 3 is a schematic diagram of a VXLAN architecture applicable to an embodiment of the present application. As shown in FIG. 3, the VXLAN architecture includes a plurality of data centers, each data center including at least one boundary VTEP and at least one non-boundary VTEP. As an example, three DCs are shown in FIG. 3: DC10, DC20, and DC30. Wherein, A ₁₀ , A ₂₀ and A ₃₀ are border VTEPs, and Spines of DC10, DC20 and DC30, respectively, B ₁₀ , B ₂₀ and B _{30 are} non-boundary VTEPs, and are respectively DC10, DC20 and DC30, respectively Network access for network segment 10, host 20, and host 30. The IP addresses of A ₁₀ , A ₂₀ , A ₃₀ , B ₁₀ , B _{20 ,} and B ₃₀ are IP1, IP2, IP3, IP4, IP5, and IP6, respectively, and the network segment IP address of network segment 10 is 1.1.1.0/24. It can be understood that the B ₁₀ connection network segment 10 means that the B _{10 is} connected to multiple hosts in the network segment 10 to implement network access of all hosts in the network segment 10.

A ₁₀ , A ₂₀ , A ₃₀ , B ₁₀ , B _{20 ,} and B ₃₀ all run a routing protocol, which may be a Border Gateway Protocol (BGP) Ethernet Virtual Private Network (EVPN). Protocol, Intermediate System to Intermediate System (IS-IS) protocol, Open Shortest Path First (OSPF) protocol, etc. During the network configuration of the VTEP, the network connection attribute between the VTEP and its neighbor VTEP is configured based on the neighbor relationship of each VTEP. The network connection attribute is used to identify whether a VTEP and its neighbor VTEP belong to the same DC, that is, the VTEP goes. The route to the neighbor VTEP is DCN) or DCI.

For convenience of description, in the embodiment of the present application, if a VTEP and its neighbor VTEP are in the same DC, the network connection attribute between the two VTEPs is DCN. If a VTEP and its neighbor VTEP are not in the same DC, the two VTEPs are The network connection property between them is DCI. If the network connection attribute is DCN, the corresponding network connection attribute identifier can be directly represented by DCN. If the network connection attribute is DCI, the corresponding network connection attribute identifier can also be directly represented by DCI. Of course, you can also set two different network connection attributes by setting other different identifiers, as long as the two types of identifiers are different. For example, it can be used for 1 to indicate that the network connection attribute is DCN, and 0 to indicate that the network connection attribute is DCI.

Based on the network architecture shown in FIG. 3, the BGP neighbor relationships of A ₁₀ , A ₂₀ , A ₃₀ , B ₁₀ , B _{20 ,} and B ₃₀ are: B ₁₀ , A _{20 ,} and A ₃₀ are neighbor VTEPs of A ₁₀ , B ₂₀ , A ₁₀ and A ₃₀ are neighbor VTEPs of A ₂₀ , B ₃₀ , A ₁₀ and A ₂₀ are neighbor VTEPs of A ₃₀ , A ₁₀ is a neighbor VTEP of B ₁₀ , A ₂₀ is a neighbor VTEP of B ₂₀ , and A ₃₀ is B ₃₀ Neighbor VTEP. The network connection attribute identifier between each VTEP and its neighbor VTEP is as shown in FIG. 3. If the network connection attribute between the devices A ₁₀ and B ₁₀ is identified as DCN, the network connection attribute between the devices A ₁₀ and A ₂₀ is identified as DCI.

It should be noted that there is no direct physical link between the leafs in the same DC, and the Spine communication in the DC is required between the leaves in the same DC, and the Spine in the same DC does not generally communicate directly.

On the VXLAN control plane, in order to implement interworking between multiple DCs, the leaf in the DC needs to advertise the IP route of its subordinate host or network segment. Otherwise, Spine and other leaves cannot learn the route of the other party, thus failing to perform data plane. Data forwarding. Hereinafter network route B ₁₀ to release segment 10 will be described as an example routing protocol packet forwarding process.

B ₁₀ through the network routing protocol packets to route A distribution network ₁₀ information segment 10, B ₁₀ release routing protocol packets comprising an outer layer, in addition to a source packet VXLAN (B IP address encapsulated in ₁₀ IP4 IP address), IP address IP1 of A ₁₀ (outer destination IP address in encapsulated VXLAN packet), IP address of network segment 10 1.1.1.0/24 (inner source IP in encapsulated VXLAN packet) external address) protocol packets basic parameters, also carry B ₁₀ is connected to a network a ₁₀ B ₁₀ i.e. attribute identifies the attribute identifier a network connection ₁₀ between the DCN.

When A ₁₀ learns the routing protocol message advertised by B ₁₀ , the DCN carried in the routing protocol packet is first sent by the leaf in the same DC, and A ₁₀ learns the routing protocol packet. The routing information is the IP address of the network segment 10 and the transmission path corresponding to the network segment 10, and the network connection attribute identifier DCI between A ₁₀ and A ₂₀ is added to the DCN in the routing protocol packet, and the route is added. The protocol message is further advertised to A ₂₀ , and A ₁₀ adds the network connection attribute identifier DCI between A ₁₀ and A ₃₀ to the DCN and DCI in the routing protocol message, and then advertises the routing protocol message to A ₃₀ . The processing principle of the packet after the A ₂₀ and the A ₃₀ learn the routing protocol packet advertised by the device A _{10 is the} same. The following takes A ₂₀ as an example for description.

When A ₂₀ learns the routing protocol message advertised by the device A ₁₀ , the A ₂₀ sends the device according to the inner layer IP address 1.1.1.0/24 in the routing protocol message, and the protocol message is not sent by the device in the DC ₂₀ where the A ₂₀ is located. packets, routing information for DCN-DCI, can know the protocol packets according to the route protocol packet network connection attribute identifies the sequence of a ₂₀ and ₂₀ are not on the same DC from the apparatus a Spine released, the ring is not present After the device A ₂₀ learns the routing information of the received routing protocol packet, the device A ₂₀ copies the routing protocol packet according to the number of ports of the A ₂₀ (when the number of ports is N, a total of N-1 routing protocol packets are required. In order to send to other ports than the receiving port, in FIG. 3, A ₂₀ copies two routing protocol messages, and adds the network connection attribute identifier DCI of the device A ₂₀ to the device A ₃₀ to a routing protocol. After the DCN and DCI are identified in the text, the routing protocol message is advertised to A ₃₀ , and the network connection attribute identifier DCN of the device A ₂₀ to the device B ₂₀ is added to the identifier DCN and DCI in another routing protocol message. , continue the other routing protocol message Published to B ₂₀ .

When B ₂₀ learns the routing protocol message advertised by A ₂₀ , since B _{20 is a} non-boundary VTEP, the routing protocol packet received by B ₂₀ is definitely sent by the VTEP of the DC where the DC is located. Therefore, it is not necessary to determine whether there is a DC interconnection. The loop is possible. After When configured with the correct routing policy, B ₂₀ to learn routing information of the routing protocol packets and discard the BCP EVPN protocol packets. When an abnormal situation such as a network configuration error occurs, the B ₂₀ may also add the network connection attribute DCN of the B ₂₀ to the A ₂₀ to the network connection attribute identifiers DCN, DCI, and DCN in the routing protocol report, and then the routing protocol. The message is posted to A ₂₀ .

When A ₃₀ learns the protocol packet issued by the A ₂₀ , the A ₃₀ can know that the routing protocol packet is not sent by the device in the DC ₃₀ where the A ₃₀ is located according to the inner layer IP address 1.1.1.0/24 in the routing protocol packet. If the network connection attribute identification sequence in the routing protocol packet is DCN-DCI-DCI, the routing protocol packet is determined to be a packet sent by the device in another DC forwarded by one DC Spine, so There is no loop possibility. A ₃₀ adds the network connection attribute identifier between the A ₃₀ and the next hop device, such as B ₃₀ , to the DCN-DCI-DCI, and then sends the routing protocol message to B ₃₀ .

When A ₂₀ learns the routing protocol message advertised by B ₂₀ , the connection attribute identification sequence in the routing protocol message is DCN-DCI-DCN-DCN, and according to the sequence, it can be determined that the routing protocol message received at this time is The routing protocol packets received from other DCs are forwarded again after being forwarded by the DCN in which the A ₂₀ is located. If the routing protocol packets are advertised again, the routing protocol packets may be re-entered into the initial release. The route of the routing protocol packet causes a loop in the routing (forwarding path) of the routing protocol packet. Therefore, A ₂₀ directly discards the routing protocol packet, thereby avoiding the possibility of loops.

It can be seen that, according to the embodiment of the present application, the border VTEP of the DC can detect the risk of loops in the received routing protocol packet when the routing protocol packet is received, and prevent the network fault from being caused by the incorrect routing configuration. The embodiment of the present application avoids the possibility of loops in packet forwarding from the network control plane. Therefore, loop-free forwarding of data plane packets between DCs is ensured from the source.

FIG. 4 is a schematic structural diagram of a network edge device according to an embodiment of the present disclosure. The network edge device may be implemented as any VTEP in the network architecture shown in FIG. 3. As shown in FIG. 4, a central processing unit (CPU) is a control unit of a network edge device, and programs running in the device and statically configured parameters are saved in a flash memory, and code and data executed when the program is running. It can be placed in a random access memory (RAM) connected to the CPU. The CPU controls the Ethernet switch (LSW) chip to perform initialization, service entry delivery, protocol packet transmission and reception, and various types of interrupts. The LSW chip can be used to store the forwarded packets, which can solve some scenarios where the internal buffer of the LSW chip is insufficient. The physical layer (PHY) interface connected to the LSW chip completes the optical interface of the optical interface or electrical interface between the devices. The processing method of the routing protocol packet in the embodiment of the method may be specifically performed by the CPU of the network edge device shown in FIG. 4, and the CPU controls the unicast (unicast), broadcast, unknown unicast, and multiple received by the LSW chip to the device. The forwarding behavior of the routing protocol packets is broadcasted from the control plane. This avoids the possibility of loops in routing and forwarding.

FIG. 5 is a schematic flowchart of a method for processing a routing protocol packet according to an embodiment of the present disclosure. The method for processing a routing protocol packet is applicable to a network edge device of a DC. The network edge device can be any of the network edge devices shown in Figures 1-4. The first network edge device of the first DC is used to refer to the network edge device. As shown in FIG. 5, the protocol packet processing method may include:

Step S10: Before the first network edge device issues the first routing protocol packet to the second network edge device, the first network connection attribute identifier is added to the first routing protocol packet.

In the embodiment of the present application, the first network edge device may be a border network edge device or a non-boundary network edge device, and the second network edge device is a border network edge device. If the first network edge device is a border network edge device, if the first network edge device is a border network edge device, the second network edge device is the second network edge device. A border network edge device for the second DC.

In order to implement the interconnection communication between different DCs and different hosts in the same DC, the network edge device of the DC runs a routing protocol, and the network edge device advertises the routing protocol packet to the neighboring network edge device to receive the route. The neighboring network edge device of the protocol packet can learn the relevant routing information in the routing protocol packet, establish a tunnel between the two network edge devices, and implement communication between the two network edge devices based on the established tunnel.

In the embodiment of the present application, in order to avoid the possibility of a packet forwarding loop (that is, a protocol packet sent from one DC is forwarded back to the DC), the first network edge device is in the second network. Before the routing device advertises the routing protocol packet, the edge device adds the first network connection attribute identifier to the routing protocol packet, where the routing protocol packet is used to enable the second network edge device to learn the routing protocol packet. The inner IP address (host IP address or network segment IP address) and the first connection attribute identification sequence in the routing protocol packet determine whether there is a loop in the route of the routing protocol packet. The routing protocol packet routing refers to the forwarding path of the first routing protocol packet. The routing information in the routing protocol packet refers to the routing information carried in the routing protocol packet, such as the host IP address or network segment. IP address, etc.

In the embodiment of the present application, the first network connection attribute identifier is used to identify whether the first network edge device and the second network edge device belong to the same DC, and the first network connection attribute identifier is the first identifier or the second identifier, and the first identifier is used by the first identifier. The first network edge device and the second network edge device are identified as belonging to the same DC, and the second identifier is used to identify that the first network edge device and the second network edge device do not belong to the same DC.

It can be understood that the specific forms of the first identifier and the second identifier may be set as needed. For example, the first identifier may be a DCN and the second identifier may be a DCI. For another example, the first identifier may be 1 and the second identifier may be 0.

The first connection attribute identification sequence is a sequence formed by the network connection attribute identifier sequentially added by each network edge device that the routing protocol message passes during the forwarding process, and the first connection attribute identification sequence includes the first network connection attribute identifier. .

That is, in the process of forwarding the routing protocol packets, each network edge device that sends the routing protocol message needs to send the edge device of the network to the edge of the network to which the edge device of the network is to be sent before sending. The network connection attribute identifier of the device is added to the routing protocol packet. If at least one network connection attribute identifier already exists in the routing protocol packet, the network connection attribute identifier to be added by the network edge device is added before the addition. After the network connection attribute identifier is used, the sequence of the network connection attribute identifier in the routing protocol packet represents the forwarding path information of the packet. Therefore, when receiving the routing protocol packet, the second network edge device can determine, according to the connection attribute identification sequence carried in the routing protocol message, whether the route of the routing protocol packet, that is, the forwarding path, has a loop.

In the embodiment of the present application, if the first network edge device is a border network edge device, the first network edge device adds the first network connection attribute identifier to the routing protocol packet before advertising the routing protocol packet to the second network edge device. Specifically, including:

The first network edge device receives the routing protocol packet, where the routing protocol packet carries the network connection attribute identifier sequentially added by each network edge device that the routing protocol packet passes during the forwarding process;

The first network edge device obtains the second connection attribute identification sequence according to the sequentially added network connection attribute identifier carried in the routing protocol packet;

Determining, by the first network edge device, whether a route of the routing protocol packet exists in a loop according to the second connection attribute identification sequence;

If the first network edge device determines that there is no loop in the route of the routing protocol packet, the first network edge device adds the first network connection attribute identifier to the routing protocol packet.

In the embodiment of the present application, if the first network edge device determines that the route of the routing protocol packet is in a loop, the processing method further includes:

The first network edge device discards the routing protocol packet.

In the embodiment of the present application, if the first network edge device is a border network edge device, the first network edge device needs to determine whether the received routing protocol packet has a loop after receiving the routing protocol packet. After determining that there is no loop possibility, the first network connection attribute identifier is added to the routing protocol packet, and is sent to the second network edge device. If it is determined that there is a loop, the protocol packet is directly discarded. Continue forwarding. Specifically, the first network edge device may obtain the second connection attribute identification sequence corresponding to the protocol packet according to the identifier of all the network connection attributes carried in the received routing protocol packet, and determine the received routing protocol packet based on the sequence. If there is a loop in the route, the routing protocol packet is further processed only when it is determined that there is no loop in the routing protocol packet.

In the embodiment of the present application, the first network edge device determines, according to the second connection attribute identification sequence, whether a routing protocol packet has a loop, including:

If the second connection attribute identification sequence satisfies the following first condition and the second condition, determining that the route of the routing protocol packet is loopable, and if the second connection attribute identification sequence is different, the first condition and the second condition are met, The route of the routing protocol packet is determined to be loop-free.

The first condition is that the number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three; the second condition is that the connection attribute identification sequence is other than the first network connection attribute identifier and the last network connection attribute identifier. The first identifier is in the network connection attribute identifier, or the host IP address or the network segment IP address of the route carried in the routing protocol packet is the IP address connected to the non-boundary network edge device in the DC where the network edge device is located.

In the network architecture shown in FIG. 3, if the A ₁₀ receives the routing protocol packet advertised by the B ₁₀ , the inner IP address in the routing protocol packet is the IP address 1.1.1.0/24 of the network segment 10, The network connection attribute identifier carried is only one DCN. Because the network connection attribute identifier is only one, the first condition is not met. Therefore, A ₁₀ determines that there is no loop possibility in the received routing protocol message advertised by B ₁₀ . A ₂₀ B ₂₀ when receiving the inner IP address is published 1.1.1.0/24, connection attribute identifies the sequence of DCN-DCI-DCN-DCN routing protocol packets, the number of sequence identity is four, the condition 1. In the sequence, except for the identifier DCN of the sequence header and the identifier DCN of the sequence tail, there is a first identifier, that is, the DCN. If the condition 2 is satisfied, the A ₂₀ determines that the received routing protocol message advertised by the B ₂₀ exists. The path may be that A ₂₀ discards the received routing protocol message.

In the embodiment of the present application, the first network connection attribute identifier is carried in a value field of an extended type length value TLV field of the routing protocol message.

In the embodiment of the present application, the network connection attribute identifier may be carried in the routing protocol packet by using the extended TLV field according to the specific packet format of the routing protocol based on the routing protocol packet, and the network edge of each routing protocol packet is forwarded. Before forwarding the routing protocol packet, the device adds the network connection attribute identifier of the network edge device to be sent by the local device and the routing protocol packet to the value field of an extended TLV field.

For example, the routing protocol packet is a BCP EVPN packet. For the BGP EVPN protocol, a new network layer reachability information (NLRI) is defined in the EVPN. The EVPN NLRI defines a new BGP EVPN route type, and the network edge device can carry the release and The BGP EVPN protocol packets of the BGP EVPN route are learned to implement IP address learning and advertisement between the same DC and/or network edge devices of different DCs to establish a tunnel between two network edge devices.

FIG. 6 is a schematic diagram showing part of the content of the NLRI field format in the BGP EVPN protocol packet in the embodiment of the present application. As shown in FIG. 6, the NLRI format includes fixed format field information such as route distinguisher (RD), Ethernet segment identifier (ESI), and Ethernet tag ID. In addition, the newly extended TLV field, that is, the DCN Type field shown in FIG. 6, carries the network between the edge device of the network (the network edge device that sends the protocol packet) and the neighbor network edge device through the TLV field. Connection attribute ID.

FIG. 7 shows a schematic diagram of a specific structure of a TLV field. As shown in Figure 7, the T field (DCN type) is used to carry the type of the network connection attribute identifier, the L field (length) is used to indicate the total length of the V field, and the V field (DCN value) carries the specific network connection attribute identifier. . For example, if the first network edge device and the second network edge device belong to the same DC, the value of the V field may be 1. If the first network edge device and the second network edge device do not belong to the same DC, the value of the V field may be Is 0.

Each time a BGP EVPN packet is sent, the network edge device that sends the BGP EVPN packet adds the network connection attribute between the network edge device and the network edge device that receives the BGP EVPN packet to the new extended TLV field. In the V field. As shown in Figure 8, the NLRI field of the BGP EVPN protocol packet is sent after the BGP EVPN protocol packet is sent twice.

In the embodiment of the present application, before the first network connection attribute identifier is added to the routing protocol packet, the method further includes:

Determining, according to a network connection relationship attribute table in the first network edge device, a first network connection attribute identifier;

The network connection relationship attribute table is configured to record a network connection attribute identifier between the first network edge device and the neighbor network edge device of the first network edge device, where the network connection relationship attribute table is a neighbor relationship configuration based on the first network edge device. The data table, the neighbor network edge device of the first network edge device includes a second network edge device.

It can be understood that the foregoing network connection relationship attribute table may be pre-configured in the first network edge device, or may be automatically generated by the first network edge device, for example, the first network edge device may receive other After the routing protocol packet sent by the network edge device, the network connection relationship attribute table of the first network edge device and other network edge devices automatically established according to the IP address of the other network edge device carried in the routing protocol packet, the other network The edge device is the neighbor edge device of the first network edge device.

In the embodiment of the present application, the first network edge device sends a route to the neighbor network edge device by using a data table in the first network edge device for recording the network connection attribute identifier of the first network edge device and its neighbor network edge device. When the protocol packet is received, the corresponding network connection attribute identifier can be quickly determined according to the data table and added to the routing protocol packet, thereby improving the processing efficiency of the routing protocol packet.

In the embodiment of the present application, each entry of the network connection relationship attribute table stores a correspondence between a network connection attribute identifier of the first network edge device and one of the neighbor network edge devices, and an IP address of the neighbor network edge device.

In the embodiment of the present application, determining the first network connection attribute identifier according to the network connection relationship attribute table in the first network edge device, including:

And searching, according to the IP address of the second network edge device, the first network connection attribute identifier that matches the IP address of the second network edge device in the network connection relationship attribute table.

In the embodiment of the present application, the IP address of the neighbor network edge device of the first network edge device may be directly used as an index, and the IP address of the neighbor network edge device and the neighbor network edge device corresponding to the IP address and the first network edge device may be used as an index. The network connection properties are associated with the network connection relationship property sheet. In this way, the network connection attribute identifier of the first network edge device and the neighbor network edge device can be quickly found based on the IP address of the neighbor network edge device.

As a specific example, Table 1 shows a schematic structure of a network connection relationship attribute table configured on the device A ₁₀ in the network architecture shown in FIG. As shown in Table 1, the neighbor network edge device A ₁₀ to B _10, A ₂₀ and A _30, B ₁₀ and A ₁₀ the DC belong to the same, the network connection properties identified as one of the two, A ₂₀ and A ₁₀ belonging to For different DCs, the network connection attribute identifier between the two is 0, A ₃₀ and A ₁₀ belong to different DCs, and the network connection attribute identifier between the two is 0. The IP address of B ₁₀ is IP4, the IP address of A ₂₀ is IP2, and the IP address of A ₃₀ is IP3. When A ₁₀ sends a routing protocol packet to A ₂₀ , it can quickly find the corresponding network connection attribute identifier 0 in Table 1 based on the IP address of A ₂₀ .

Table 1

IP2	0
IP3	0
IP4	1

FIG. 9 is a schematic flowchart of a method for processing a routing protocol packet according to an embodiment of the present application. The protocol packet processing method is applicable to a network edge device of a DC, as applicable to any of the devices shown in FIG. A network edge device. The first network edge device using the first DC below refers to any network edge device. As shown in FIG. 9, the method for processing the routing protocol packet may include:

Step S21: The first network edge device receives the routing protocol packet advertised by the second network edge device.

The first network edge device is a border network edge device, and the second network edge device is a boundary network edge device of the second DC or a non-boundary network edge device of the first DC.

The routing protocol packet carries the network connection attribute identifier added by each network edge device that the routing protocol packet passes in the forwarding process. The network connection attribute identifier is the first identifier or the second identifier, and the first identifier is used to identify The network edge device that advertises the routing protocol packet and the network edge device that receives the routing protocol packet belong to the same DC. The second identifier is used to identify the network edge device that advertises the routing protocol packet and the network edge device that receives the routing protocol packet. The same DC.

It can be understood that the specific forms of the first identifier and the second identifier can be set according to actual needs. As long as the two identifiers are different, the two identifiers can distinguish whether the two network edge devices belong to the same DC.

Step S22: The first network edge device obtains the connection attribute identification sequence according to the sequentially added network connection attribute identifier carried in the routing protocol message.

Step S23: The first network edge device determines, according to the obtained connection attribute identification sequence, whether there is a loop of routing protocol packet routing.

In the embodiment of the present application, each network edge device (including the border network edge device and the non-boundary network edge device) needs to send the edge device and the routing protocol packet to the peer network before sending the routing protocol packet. The network connection relationship attribute identifier between the edge devices is added to the routing protocol packet, so that the border network edge device that subsequently receives the routing protocol packet can be based on the inner layer source IP address of the routing protocol packet and the routing protocol. The connection attribute identification sequence corresponding to all network connection attribute identifiers carried in the packet determines whether there is a loop in the routing protocol packet.

The network connection attribute identifier added by each of the network edge devices is carried in a value field of an extended type length value TLV field of the routing protocol packet.

In the embodiment of the present application, if the first network edge device determines that the route of the routing protocol packet does not exist in the loop according to the obtained connection attribute identification sequence, the processing method may further include:

The first network edge device adds the first network connection attribute identifier to the network connection attribute identifier added in the routing protocol packet.

The first network edge device advertises the added routing protocol message to the third network edge device.

The first network connection attribute identifier is a network connection attribute identifier between the first network edge device and the third network edge device, and the third network edge device is a third DC border network edge device or a first DC non-boundary network. The edge device, that is, the third network edge device, may be a non-border network edge device that belongs to the same DC as the first network edge device, or may be a border network edge device that belongs to a different DC from the first network edge device.

In the embodiment of the present application, if the first network edge device determines that the route of the routing protocol packet exists in a loop according to the obtained connection attribute identification sequence, the processing method may further include:

The first network edge device discards the routing protocol packet.

In the embodiment of the present application, if the first network edge device determines that there is a loop in the routing protocol packet, the first network edge device directly discards the routing protocol packet, that is, does not learn the route carried in the protocol packet. The information does not continue to be forwarded to avoid the occurrence of network loops due to the continued forwarding of the protocol packets. If it is determined that there is no loop possibility, the corresponding network connection attribute identifier is added to the existing network connection attribute identifier in the packet, and the protocol packet is further forwarded to the neighbor network edge device, and the devices in the network are continued. The process of routing and learning of routes provides the basis for data forwarding at the data level.

In the embodiment of the present application, the first network edge device determines, according to the connection attribute identifier sequence, whether a route of the second routing protocol packet exists in a loop, and specifically includes:

If the connection attribute identification sequence satisfies the following first condition and the second condition, the route of the routing protocol packet is determined to be loopable. If the connection attribute identification sequence is different, the first condition and the second condition are met, and the routing protocol report is determined. There is no loop in the route of the text. The conditions for determining include:

The first condition is that the number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three;

The second condition is that the first identifier is in the network connection attribute identifier of the connection attribute identifier sequence except the first network connection attribute identifier and the last network connection attribute identifier, or the host IP of the route carried in the routing protocol packet The IP address of the address or network segment is the IP address of the non-boundary network edge device in the DC where the network edge device resides.

In the embodiment of the present application, the first network edge device determines, according to the first condition and the second condition, the second condition to determine whether the route of the routing protocol packet has a detailed description of the loop. For details, refer to the processing corresponding to Figure 5 in the foregoing. In the method, when the first network edge device is a border network edge device, the first network edge device determines, according to the second connection attribute identification sequence, whether the route of the routing protocol message has a description of a possible part of the loop. Let me repeat.

In the embodiment of the present application, the first network edge device adds the first network connection attribute identifier to the routing protocol packet, and further includes:

The first network edge device determines the first network connection attribute identifier according to the network connection relationship attribute table in the first network edge device.

In the embodiment of the present application, the network connection relationship attribute table is configured to record a network connection attribute identifier between the first network edge device and the neighbor network edge device of the first network edge device, where the network connection relationship attribute table is based on the first network edge device. The data table of the neighbor relationship configuration, the neighbor network edge device of the first network edge device includes a third network edge device.

In the embodiment of the present application, the network connection relationship attribute table stores the network connection attribute identifier of the first network edge device and the neighbor network edge device of the first network edge device, and the corresponding relationship between the IP address of the neighbor network edge device.

Correspondingly, the first network edge device determines the first network connection attribute identifier according to the network connection relationship attribute table in the first network edge device, which may include:

And searching, according to the IP address of the third network edge device, a first network connection attribute identifier that matches an IP address of the third network edge device in the network connection relationship attribute table.

The first network edge device determines a detailed description of the first network connection attribute identifier according to the network connection relationship attribute table. For details, refer to the first network edge device in the processing method corresponding to FIG. 5 in the foregoing method, searching according to the network connection relationship attribute table. The content of the relevant part of the first network connection attribute identifier is not described here for brevity.

It should be noted that when receiving the routing protocol packet, the network edge device needs to first decapsulate the encapsulation header of the packet, that is, delete the encapsulation header in the received routing protocol packet, if the original encapsulation is based on the decapsulation The content of the packet indicates that there is no loop in the route of the packet. After learning the routing information carried in the original packet, the original packet needs to be encapsulated and then forwarded. The encapsulation header added by each network edge device is added. The information is different. Therefore, in the embodiment of the present application, the same routing protocol packet is not identical in the protocol packet sent by different network edge devices, and the different network edge devices are received. And/or forwarding the protocol packets are collectively referred to as the same routing protocol packet, because the content of the original packet in the protocol packet (excluding the extended TLV field) is the same, that is, the same original packet is forwarded. For example, for the foregoing routing protocol packet, when the first network edge device sends the packet to the second network edge device, the outer IP address of the encapsulation header in the encapsulation header is the IP address of the first network edge device. The IP address of the outer network destination device is the IP address of the second network edge device. When the first network edge device receives the protocol packet, the outer destination address of the packet is the IP address of the first network edge device. The address is the IP address of the other network edge device that sends the protocol message to the first network edge device.

Corresponding to a processing method of a routing protocol packet shown in FIG. 5, FIG. 10 is a schematic structural diagram of a processing apparatus 100 of a routing protocol packet provided by an embodiment of the present application, where the processing apparatus is applicable to Any of the network edge devices shown in Figures 1 - 4. Hereinafter, the first network edge device of the first DC refers to any network edge device, and the first network edge device is a border network edge device or a non-boundary network edge device. The processing device 100 can include a connection attribute identification adding module 130.

The connection attribute identifier adding module 130 is configured to add the first network connection attribute identifier to the routing protocol message before the routing protocol message is advertised to the second network edge device, where the routing protocol message is used to make the second network When the routing device learns the routing protocol packet, the edge device can determine whether the route of the routing protocol packet has a loop according to the first connection attribute identifier sequence of the routing protocol packet.

The second network edge device is a border network edge device, and the first network connection attribute identifier is a first identifier or a second identifier, where the first identifier is used to identify that the first network edge device and the second network edge device belong to the same DC, The second identifier is used to identify that the first network edge device and the second network edge device do not belong to the same DC, and the first connection attribute identifier sequence is a network that is added by each network edge device that the first routing protocol packet passes in the forwarding process. A sequence formed by the connection attribute identifier, the first connection attribute identification sequence including the first network connection attribute identifier.

It can be understood that the processing apparatus 100 according to the embodiment of the present application may correspond to the execution subject in the processing method of the routing protocol message according to the embodiment of the present application shown in FIG. 5, and the connection attribute identifier of the processing apparatus 100 is added. The module 130 is used to implement the corresponding process in the processing method of the embodiment of the present application corresponding to FIG. 5, and the detailed implementation of the operation and/or function of the connection attribute identifier adding module 130 can be referred to the processing of the embodiment of the present application corresponding to FIG. The description in the method section is not repeated here for brevity.

In an optional embodiment of the present application, if the first network edge device is a border network edge device, the processing device 100 further includes a protocol packet receiving module 110 and a loop determining module 120, as shown in FIG.

The protocol packet receiving module 110 is configured to receive a routing protocol packet, where the routing protocol packet carries a network connection attribute identifier sequentially added by each network edge device that the routing protocol packet passes during the forwarding process.

The loop determining module 120 is configured to obtain a second connection attribute identification sequence according to the sequentially added network connection attribute identifier carried in the routing protocol message, and determine, according to the second connection attribute identification sequence, whether the route of the first routing protocol message exists. The road may be.

The connection attribute identifier adding module 130 is configured to add the first network connection attribute identifier to the routing protocol message when the loop determining module determines that the route of the routing protocol message does not have a loop.

In an optional embodiment of the present application, the processing apparatus 100 may further include a packet discarding module 140, as shown in FIG.

The packet discarding module 140 is configured to discard the routing protocol packet when the loop determining module determines that the route of the routing protocol packet exists in a loop.

In an optional embodiment of the present application, the loop determining module 120 is specifically configured to:

When the second connection attribute identification sequence satisfies the following first condition and the second condition, the route of the protocol packet is determined to be loopable, and when the second connection attribute identification sequence is different, the first condition and the second condition are met. Then, it is determined that there is no loop in the route of the protocol packet.

The first condition is that the number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three, and the second condition is that the connection attribute identification sequence is other than the first network connection attribute identifier and the last network connection attribute identifier. The first identifier is in the network connection attribute identifier, or the host IP address or the network segment IP address of the route carried in the routing protocol packet is the IP address connected to the non-boundary network edge device in the DC where the network edge device is located.

In an optional embodiment of the present application, the first network connection attribute identifier is carried in a value field of an extended TLV field of the routing protocol message.

In an optional embodiment of the present application, the connection attribute identifier adding module 130 is further configured to determine, according to the network connection relationship attribute table in the first network edge device, before adding the first network connection attribute identifier to the routing protocol message. The first network connection attribute identifier.

The network connection relationship attribute table is configured to record a network connection attribute identifier between the first network edge device and the neighbor network edge device of the first network edge device, where the network connection relationship attribute table is a neighbor relationship configuration based on the first network edge device. The data table, the neighbor network edge device of the first network edge device includes a second network edge device.

In an optional embodiment of the present application, the network connection relationship attribute table stores a network connection attribute identifier of the first network edge device and a neighbor network edge device of the first network edge device, and an IP address of the neighbor network edge device Correspondence relationship.

Correspondingly, when the connection attribute identifier adding module 130 determines the first network connection attribute identifier according to the network connection relationship attribute table, specifically:

And searching, according to the IP address of the second network edge device, the first network connection attribute identifier that matches the IP address of the second network edge device in the network connection relationship attribute table.

It can be understood that the processing apparatus 100 of the embodiment of the present application may correspond to the execution subject in the processing method of the routing protocol message according to the embodiment of the present application shown in FIG. 5 or the module of the processing apparatus 100. The operation and/or function is to implement the corresponding flow in the processing method of the embodiment of the present application corresponding to FIG. 5 or FIG. 5, and the detailed implementation manner of the operation and/or function of each module of the processing apparatus 100 can be referred to the foregoing. The description in the corresponding processing method section will not be repeated here for brevity.

Corresponding to the processing method of a routing protocol packet shown in FIG. 9, FIG. 13 is a schematic structural diagram of a processing apparatus 200 of a routing protocol packet according to an embodiment of the present application. The processing apparatus 200 is applicable to the processing apparatus 200. Any of the network edge devices shown in Figures 1 - 4. Hereinafter, the first network edge device of the first DC is referred to by the processing device as any boundary network device, and the first network edge device is a border network edge device. The processing device 200 includes a protocol message receiving module 210 and a loop determining module 220.

The protocol packet receiving module 210 is configured to receive a routing protocol packet advertised by the second network edge device.

The second network edge device is a border network edge device or a non-border network edge device, and the routing protocol packet carries the network connection attribute identifier added by each network edge device that the routing protocol packet passes in the forwarding process. The network connection attribute identifier is a first identifier or a second identifier, and the first identifier is used to identify that the network edge device that advertises the routing protocol packet and the network edge device that receives the routing protocol packet belong to the same DC, and the second identifier is used to identify the advertisement route. The network edge device of the protocol packet and the network edge device that receives the routing protocol packet do not belong to the same DC.

The loop determining module 220 is configured to obtain a connection attribute identification sequence according to the sequentially added network connection attribute identifier carried in the routing protocol packet, and determine whether a route of the routing protocol packet has a loop according to the connection attribute identification sequence.

It can be understood that the processing apparatus 200 according to the embodiment of the present application may correspond to the execution body in the processing method of the routing protocol message according to the embodiment of the present application shown in FIG. 9, and the protocol message receiving of the processing apparatus 200 The module 210 and the loop determining module 220 are specific implementations of the operations and/or functions of the protocol packet receiving module 210 and the loop determining module 220 in order to implement the corresponding processes in the processing method of the embodiment of the present application corresponding to FIG. 9 . The description in the processing method part of the embodiment of the present application corresponding to FIG. 9 is omitted for brevity.

In an optional embodiment of the present application, the loop determining module 220 is specifically configured to: when the connection attribute identification sequence satisfies the following first condition and the second condition, determining that the route of the routing protocol packet exists in a loop may be If the second connection attribute identification sequence does not meet the first condition and the second condition, it is determined that there is no loop in the route of the routing protocol packet.

The first condition is that the number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three.

The second condition is that the first identifier is in the network connection attribute identifier of the connection attribute identifier sequence except the first network connection attribute identifier and the last network connection attribute identifier, or the host IP of the route carried in the routing protocol packet The IP address of the address or network segment is the IP address of the non-boundary network edge device in the DC where the network edge device resides.

In an optional embodiment of the present application, the processing apparatus 200 further includes a connection attribute identifier adding module 230 and a protocol packet sending module 240, as shown in FIG.

The connection attribute identifier adding module 230 is configured to add the first network connection attribute identifier to the sequentially added network connection attribute in the routing protocol packet when the route of the routing protocol packet is determined according to the connection attribute identification sequence. After the logo.

The protocol packet sending module 240 is configured to post the added routing protocol packet to the third network edge device.

The first network connection attribute identifier is a network connection attribute identifier between the first network edge device and the third network edge device, and the third network edge device is a border network edge device or a non-boundary network edge device.

In an optional embodiment of the present application, the connection attribute identifier adding module 230 is further configured to determine, according to the network connection relationship attribute table in the first network border device, before adding the first network connection attribute identifier to the routing protocol message. The first network connection attribute identifier.

The network connection relationship attribute table is configured to record a network connection attribute identifier between the first network edge device and the neighbor network edge device of the first network edge device, where the network connection relationship attribute table is a neighbor relationship configuration based on the first network edge device. The data table, the neighbor network edge device of the first network edge device includes a third network edge device.

In an optional embodiment of the present application, the network connection relationship attribute table stores a network connection attribute identifier of the first network edge device and a neighbor network edge device of the first network edge device, and an IP address of the neighbor network edge device Correspondence relationship.

Correspondingly, the connection attribute identifier adding module 230 is configured to search, in the network connection relationship attribute table, the first network connection attribute identifier that matches the IP address of the third network edge device according to the IP address of the third network edge device.

In an optional embodiment of the present application, the processing apparatus 200 further includes a packet discarding module 250, as shown in FIG.

The packet discarding module 250 is configured to discard the routing protocol packet when the route of the routing protocol packet is determined according to the connection attribute identifier sequence.

In an optional embodiment of the present application, the network connection attribute identifier added by each network edge device is carried in a value field of an extended TLV field of a routing protocol message.

It can be understood that the processing device 200 of the embodiment of the present application may correspond to the execution body in the processing method of the routing protocol message according to the embodiment of the present application shown in FIG. 9 or the module of the processing device 200. The operation and/or function is to implement the corresponding process in the processing method of the embodiment of the present application corresponding to FIG. 9 or FIG. 9 , and the detailed implementation of the operation and/or function of each module of the processing device 200 can be referred to the foregoing. The description in the corresponding processing method section will not be repeated here for brevity.

FIG. 16 is a schematic block diagram of a network edge device 300 in accordance with an embodiment of the present application. As shown in FIG. 16, the network edge device 300 includes a processor 301, a memory 302 for storing executable computer program code, and a communication interface 303 for reading the computer program code stored in the memory 302. The computer program corresponding to the computer program code is used to execute the processing method of the routing protocol message according to any embodiment of the present application. The communication interface 303 is configured to communicate with an external device, and the network edge device 300 can further include a bus 304 for connecting the processor 301, the memory 302, and the communication interface 303 such that the processor 301, the memory 302, and the communication interface 303 pass through the bus 304. Communicate with each other.

The network edge device 300 according to the embodiment of the present application may correspond to the execution body of the processing method of the routing protocol message according to the embodiment of the present application, and the operations and/or functions of the respective modules in the network edge device 300 are respectively implemented to implement the present The corresponding processes of the processing methods in the respective embodiments are not described herein for the sake of brevity.

The embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium stores a computer protocol, and when the computer instruction is run on the computer, causes the computer to execute the routing protocol message of any embodiment of the present application. Approach.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium such as a solid state disk (SSD) or the like.

Claims (28)

1. A method for processing a routing protocol packet, wherein the method is applied to a first network edge device of a first data center DC, where the first network edge device is a border network edge device or a non-boundary network edge device. , the method includes:

   Before the first network edge device advertises the routing protocol packet to the second network edge device, the first network connection attribute identifier is added to the routing protocol packet, and the routing protocol packet is used to enable the second After learning the routing protocol packet, the network edge device determines, according to the first connection attribute identifier sequence of the routing protocol packet, whether a route of the routing protocol packet exists in a loop;

   The second network edge device is a border network edge device, and the first network connection attribute identifier is a first identifier or a second identifier, where the first identifier is used to identify the first network edge device and the The second network edge device belongs to the same DC, and the second identifier is used to identify that the first network edge device and the second network edge device do not belong to the same DC, and the first connection attribute identification sequence is the routing protocol. And the sequence formed by the network connection attribute identifier added by each network edge device that is passed by the packet in the forwarding process, where the first connection attribute identification sequence includes the first network connection attribute identifier.
2. The method according to claim 1, wherein if the first network edge device is a border network edge device, the first network edge device sends a first routing protocol message to the second network edge device, The first network connection attribute identifier is added to the routing protocol packet, including:

   The first network edge device receives the routing protocol packet, where the routing protocol packet carries the network connection attribute added by each network edge device that the routing protocol packet passes in the forwarding process. Identification

   The first network edge device obtains a second connection attribute identification sequence according to the sequentially added network connection attribute identifier carried in the routing protocol message; the second connection attribute identification sequence does not include the first network connection Attribute identifier

   Determining, by the first network edge device, whether a route of the routing protocol packet exists in a loop according to the second connection attribute identifier sequence;

   And if the first network edge device determines that there is no loop in the route of the routing protocol packet, the first network edge device adds the first network connection attribute identifier to the routing protocol packet.
3. The method according to claim 2, wherein the method further comprises: if the first network edge device determines that a route of the routing protocol message exists in a loop, the method further includes:

   The first network edge device discards the routing protocol packet.
4. The method according to claim 2 or 3, wherein the first network edge device determines, according to the second connection attribute identification sequence, whether the route of the routing protocol message has a loop, including:

   If the second connection attribute identification sequence satisfies the following first condition and the second condition, determining that the route of the routing protocol packet is loopable, and if the second connection attribute identification sequence is different, the first a condition and a second condition, determining that there is no loop in the route of the routing protocol packet;

   The first condition is that the number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three;

   The second condition is that the first identifier exists in the network connection attribute identifier of the connection attribute identifier sequence except the first network connection attribute identifier and the last network connection attribute identifier, or is carried in the routing protocol packet. The routed host network protocol IP address or network segment IP address is the IP address to which the non-boundary network edge device in the DC where the network edge device resides.
5. The method according to any one of claims 1 to 4, wherein the first network connection attribute identifier is carried in a value field of an extended type length value TLV field of the routing protocol message.
6. The method according to any one of claims 1-5, wherein before the adding the first network connection attribute identifier to the routing protocol message, the method further includes:

   Determining, according to the network connection relationship attribute table in the first network edge device, the first network connection attribute identifier;

   The network connection relationship attribute table is configured to record a network connection attribute identifier between the first network edge device and a neighbor network edge device of the first network edge device, where the neighbor network edge device includes the Two network edge devices.
7. The method according to claim 6, wherein each of the entries of the network connection relationship attribute table stores a network of the first network edge device and a neighbor network edge device of the first network edge device. Corresponding relationship between the connection attribute identifier and the IP address of the neighbor network edge device;

   Determining, according to the network connection relationship attribute table in the first network edge device, the first network connection attribute identifier, including:

   And searching, in the network connection relationship attribute table, a first network connection attribute identifier that matches an IP address of the second network edge device.
8. A method for processing a routing protocol packet, the method is applied to a first network edge device of a first data center DC, and the first network edge device is a border network edge device, and the method includes:

   The first network edge device receives a routing protocol message advertised by the second network edge device, where the second network edge device is a border network edge device of the second DC or the non-boundary network edge device of the first DC ;

   The routing protocol packet carries the network connection attribute identifier that is added by each network edge device that the routing protocol packet passes in the forwarding process, and the network connection attribute identifier is the first identifier or the second identifier. And the first identifier is used to identify that the network edge device that advertises the routing protocol packet and the network edge device that receives the routing protocol packet belong to the same DC, and the second identifier is used to identify the routing protocol. The network edge device of the packet and the network edge device receiving the routing protocol packet do not belong to the same DC;

   The first network edge device obtains a connection attribute identification sequence according to the sequentially added network connection attribute identifier carried in the routing protocol message;

   The first network edge device determines, according to the connection attribute identification sequence, whether a route of the routing protocol packet has a loop possibility.
9. The method according to claim 8, wherein the first network edge device determines, according to the connection attribute identification sequence, whether a route of the routing protocol message exists in a loop, including:

   If the connection attribute identification sequence satisfies the following first condition and the second condition, determining that the route of the routing protocol packet is loopable, if the connection attribute identification sequence is different, the first condition and the In the second condition, it is determined that there is no loop in the route of the routing protocol packet:

   The first condition is that the number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three;

   The second condition is that the first identifier exists in the network connection attribute identifier of the connection attribute identifier sequence except the first network connection attribute identifier and the last network connection attribute identifier, or is carried in the routing protocol packet. The routed host network protocol IP address or network segment IP address is the IP address to which the non-boundary network edge device in the DC where the network edge device resides.
10. The method according to claim 8 or 9, wherein if the first network edge device determines that the route of the routing protocol message does not have a loop according to the connection attribute identification sequence, the method further includes :

    Adding, by the first network edge device, the first network connection attribute identifier to the sequentially added network connection attribute identifier in the routing protocol packet;

    The first network edge device issues the added routing protocol message to the third network edge device;

    The first network connection attribute identifier is a network connection attribute identifier between the first network edge device and the third network edge device, and the third network edge device is a third DC border network edge device. Or the non-boundary network edge device of the first DC.
11. The method according to claim 10, wherein the first network edge device adds the first network connection attribute identifier to the routing protocol message, and further includes:

    Determining, by the first network edge device, the first network connection attribute identifier according to the network connection relationship attribute table in the first network edge device;

    The network connection relationship attribute table is configured to record a network connection attribute identifier between the first network edge device and a neighbor network edge device of the first network edge device, where the neighbor network edge device includes the Three network edge devices.
12. The method according to claim 11, wherein each entry of the network connection relationship attribute table stores a network connection of the first network edge device and a neighbor network edge device of the first network edge device. Attribute identifier, a correspondence relationship with an IP address of the neighbor network edge device;

    Determining, by the first network edge device, the first network connection attribute identifier according to the network connection relationship attribute table in the first network edge device, including:

    The first network edge device searches, in the network connection relationship attribute table, a first network connection attribute identifier corresponding to an IP address of the third network edge device.
13. The method according to any one of claims 8 to 12, wherein if the first network edge device determines, according to the connection attribute identification sequence, that a route of the routing protocol message exists, the loop may be The method also includes:

    The first network edge device discards the routing protocol packet.
14. The method according to any one of claims 8 to 13, wherein the network connection attribute identifier sequentially added by each network edge device is carried in an extended type length value TLV field of the routing protocol message. In the value field.
15. A processing device for routing protocol packets, wherein the processing device is applied to a first network edge device of a first data center DC, where the first network edge device is a border network edge device or a non-boundary network edge The device, the processing device includes:

    a connection attribute identifier adding module, configured to add a first network connection attribute identifier to the routing protocol packet before the routing protocol packet is advertised to the second network edge device, where the routing protocol packet is used to enable the After learning the routing protocol packet, the second network edge device determines, according to the first connection attribute identifier sequence of the routing protocol packet, whether a route of the routing protocol packet exists in a loop;

    The second network edge device is a border network edge device, and the first network connection attribute identifier is a first identifier or a second identifier, where the first identifier is used to identify the first network edge device and the The second network edge device belongs to the same DC, and the second identifier is used to identify that the first network edge device and the second network edge device do not belong to the same DC, and the first connection attribute identification sequence is the routing protocol. And the sequence formed by the network connection attribute identifier added by each network edge device that is passed by the packet in the forwarding process, where the first connection attribute identification sequence includes the first network connection attribute identifier.
16. The device according to claim 15, wherein if the first network edge device is a border network edge device, the device further includes:

    The protocol packet receiving module is configured to receive the routing protocol packet, where the routing protocol packet carries a network connection sequentially added by each network edge device that the routing protocol packet passes during the forwarding process. Attribute identifier

    a loop determining module, configured to obtain a second connection attribute identification sequence according to the sequentially added network connection attribute identifier carried in the routing protocol packet, and determine the routing protocol packet according to the second connection attribute identification sequence Whether there is a loop in the route;

    The connection attribute identifier adding module is specifically configured to add the first network connection attribute identifier to the routing protocol report when the loop determining module determines that the route of the routing protocol packet does not exist in a loop. In the text.
17. The device according to claim 16, wherein the device further comprises:

    The packet discarding module is configured to discard the routing protocol packet when the loop determining module determines that the route of the routing protocol packet exists in a loop.
18. The device according to claim 16 or 17, wherein the loop determining module is specifically configured to:

    When the second connection attribute identification sequence satisfies the following first condition and the second condition, determining that the route of the routing protocol message has a loop possibility, and satisfying when the second connection attribute identification sequence is different When the first condition and the second condition are met, determining that the route of the routing protocol packet does not have a loop;

    The first condition is that the number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three;

    The second condition is that the first identifier exists in the network connection attribute identifier of the connection attribute identifier sequence except the first network connection attribute identifier and the last network connection attribute identifier, or is carried in the routing protocol packet. The routed host network protocol IP address or network segment IP address is the IP address to which the non-boundary network edge device in the DC where the network edge device resides.
19. The apparatus according to any one of claims 15 to 18, wherein the first network connection attribute identifier is carried in a value field of an extended type length value TLV field of the routing protocol message.
20. Apparatus according to any one of claims 15 to 19, wherein

    The connection attribute identifier adding module is further configured to determine, according to the network connection relationship attribute table in the first network edge device, the first before adding the first network connection attribute identifier to the routing protocol message Network connection attribute identifier;

    The network connection relationship attribute table is configured to record a network connection attribute identifier between the first network edge device and a neighbor network edge device of the first network edge device, where the neighbor network edge device includes the Two network edge devices.
21. The device according to claim 20, wherein each of the entries of the network connection relationship attribute table stores a network of the first network edge device and a neighbor network edge device of the first network edge device Corresponding relationship between the connection attribute identifier and the IP address of the neighbor network edge device;

    The connection attribute identifier adding module is specifically configured to: when determining the first network connection attribute identifier according to the network connection relationship attribute table,

    And searching, in the network connection relationship attribute table, a first network connection attribute identifier that matches an IP address of the second network edge device.
22. A device for processing a routing protocol packet, wherein the device is applied to a first network edge device of a first data center DC, and the first network edge device is a border network edge device, and the device includes:

    The protocol packet receiving module is configured to receive a routing protocol packet advertised by the second network edge device;

    The second network edge device is a border network edge device of the second DC or the non-boundary network edge device of the first DC, and the routing protocol packet carries the routing protocol packet in the forwarding process. a network connection attribute identifier that is added to each of the network edge devices that are passed through, and the network connection attribute identifier is a first identifier or a second identifier, where the first identifier is used to identify a network edge device that advertises the routing protocol packet. The network edge device that receives the routing protocol packet belongs to the same DC, and the second identifier is used to identify that the network edge device that advertises the routing protocol packet and the network edge device that receives the routing protocol packet do not belong to the same DC. DC;

    a loop determining module, configured to obtain a connection attribute identification sequence according to the sequentially added network connection attribute identifier carried in the routing protocol packet, and determine, according to the connection attribute identification sequence, whether the routing protocol packet routing exists The loop is possible.
23. The device according to claim 22, wherein the loop determining module is specifically configured to:

    When the connection attribute identification sequence satisfies the following first condition and the second condition, determining that the route of the routing protocol packet has a loop possibility, and satisfying the first when the second connection attribute identification sequence is different The condition and the second condition determine that there is no loop in the route of the routing protocol packet;

    The first condition is that the number of network connection attribute identifiers in the connection attribute identification sequence is greater than or equal to three;

    The second condition is that the first identifier exists in the network connection attribute identifier of the connection attribute identifier sequence except the first network connection attribute identifier and the last network connection attribute identifier, or is carried in the routing protocol packet. The routed host network protocol IP address or network segment IP address is the IP address to which the non-boundary network edge device in the DC where the network edge device resides.
24. The device according to claim 22 or 23, wherein the device further comprises:

    a connection attribute identifier adding module, configured to add a first network connection attribute identifier to the routing protocol packet when determining that the route of the routing protocol packet does not have a loop according to the connection attribute identifier sequence After the network connection attribute identifiers are added in sequence;

    a protocol packet sending module, configured to advertise the added routing protocol packet to a third network edge device;

    The first network connection attribute identifier is a network connection attribute identifier between the first network edge device and the third network edge device, and the third network edge device is a third DC border network edge device. Or the non-boundary network edge device of the first DC.
25. The device according to claim 24, wherein

    The connection attribute identifier adding module is further configured to determine, according to the network connection relationship attribute table in the first network edge device, the first before adding the first network connection attribute identifier to the routing protocol message Network connection attribute identifier;

    The network connection relationship attribute table is configured to record a network connection attribute identifier between the first network edge device and a neighbor network edge device of the first network edge device, where the neighbor network edge device includes the Three network edge devices.
26. The apparatus according to claim 25, wherein each entry in the network connection relationship attribute table stores a network of the first network edge device and a neighbor network edge device of the first network edge device Corresponding relationship between the connection attribute identifier and the IP address of the network edge device;

    The connection attribute identifier adding module is specifically configured to search, in the network connection relationship attribute table, a first network connection attribute identifier that matches an IP address of the third network edge device.
27. The device according to any one of claims 22 to 26, wherein the device further comprises:

    The packet discarding module is configured to discard the routing protocol packet when the route of the routing protocol packet is determined according to the connection attribute identifier sequence.
28. The device according to any one of claims 22 to 27, wherein the network connection attribute identifier sequentially added by each network edge device is carried in an extended type length value TLV field of the routing protocol message. In the value field.

Images