CN113904981A - Routing information processing method and device, electronic equipment and storage medium - Google Patents

Routing information processing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113904981A
CN113904981A CN202111082501.5A CN202111082501A CN113904981A CN 113904981 A CN113904981 A CN 113904981A CN 202111082501 A CN202111082501 A CN 202111082501A CN 113904981 A CN113904981 A CN 113904981A
Authority
CN
China
Prior art keywords
service
side edge
routing information
network
edge device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202111082501.5A
Other languages
Chinese (zh)
Other versions
CN113904981B (en
Inventor
戴志滨
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ruijie Networks Co Ltd
Original Assignee
Ruijie Networks Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ruijie Networks Co Ltd filed Critical Ruijie Networks Co Ltd
Priority to CN202111082501.5A priority Critical patent/CN113904981B/en
Publication of CN113904981A publication Critical patent/CN113904981A/en
Application granted granted Critical
Publication of CN113904981B publication Critical patent/CN113904981B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/54—Organization of routing tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management

Abstract

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for processing routing information, an electronic device, and a storage medium, so as to improve processing efficiency of routing information. The method comprises the following steps: configuring a service index for the session interface, wherein the service index is used for identifying VPN services to which public networks connected by the client-side edge device belong; if the VPN service is in an activated state, generating first service routing information carrying forwarding information according to the service index, and sending the first service routing information to other network side edge equipment; and generating prefix routing information carrying service indexes based on each public network connected with the client-side edge device, and sending the prefix routing information to other network-side edge devices, so that the other network-side edge devices construct related routing forwarding table entries based on the service routing information and the prefix routing information. By introducing the service index and the service route, the method and the device effectively improve the effective bearing rate of the protocol and the information processing efficiency.

Description

Routing information processing method and device, electronic equipment and storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for processing routing information, an electronic device, and a storage medium.
Background
An EVPN (Ethernet Virtual Private Network) is a two-layer VPN (Virtual Private Network), the control plane interacts EVPN routing information through MP-BGP (Multi Protocol Border Gateway Protocol), and the data plane may employ MPLS (Multi Protocol Label switching) or VXLAN (Virtual eXtensible Local Area Network) to forward a packet.
The EVPN IP Prefix route (IP Prefix routing information, i.e., an interconnection Protocol between IP networks) is carried in a BGP (Border Gateway Protocol) update packet. In the related art, when a client-side edge device is connected to multiple public networks, based on each IP address, it is necessary to generate one piece of EVPN IP prefix routing information, some identical information is repeatedly carried in each piece of EVPN IP prefix routing information, the number of routes that can be carried in one BGP update message is small, and the routing payload rate and the routing information processing efficiency are low.
Disclosure of Invention
The embodiment of the application provides a method and a device for processing routing information, electronic equipment and a storage medium, which are used for improving the effective bearing rate of a protocol and the processing efficiency of the routing information in the interaction process of an EVPN protocol.
The routing information processing method provided by the embodiment of the application is applied to the target network side edge device in the EVPN, and comprises the following steps:
configuring a service index for a session interface, wherein the session interface is an interface of the target network-side edge device and a client-side edge device, and the service index is used for identifying VPN services to which a public network connected with the client-side edge device belongs;
if the VPN service is in an activated state, generating first service routing information carrying forwarding information according to the service index, and sending the first service routing information to other network side edge devices, wherein the forwarding information is used for representing a routing forwarding path corresponding to the service index;
generating prefix routing information carrying the service index based on each public network connected by the client-side edge device, and sending the prefix routing information to the other network-side edge device, so that the other network-side edge device constructs a related routing forwarding table entry in a local routing table based on the first service routing information and the prefix routing information, wherein different prefix routing information corresponds to different public networks.
In the above embodiment, the target network-side edge device first generates first service routing information carrying forwarding information according to the service index, and then only needs to send one piece of first service routing information to other network-side edge devices; and then, based on each public network connected with the client side edge device, generating each prefix routing information carrying the service index, and sending each prefix routing information to other network side edge devices, wherein the first service routing information is associated with the prefix routing information based on the service index, so that one first service routing information can be referred by a plurality of prefix routing information, the routing payload rate and the routing information processing efficiency are improved, and the learning performance of the EVPN prefix routing is improved.
An optional implementation manner is that, after configuring a service index for a session interface, before generating first service routing information carrying forwarding information according to the service index, the method further includes:
determining respective session links established between the target network-side edge device and the client-side edge device;
and if at least one session link is in an active state, setting the VPN service to be in an active state.
In the above embodiment, if at least one session link of the session links established between the target network-side edge device and the client-side edge device is in an active state, the VPN service is in an active state, which ensures that the devices can perform interaction of routing information.
In an optional embodiment, the configuring a service index for a session interface includes at least one of:
if a plurality of session links exist between the target network side edge device and the client side edge device, configuring the same service index for each session interface corresponding to each session link;
if the client-side edge device is connected to at least one other target network-side edge device except the target network-side edge device, configuring the same service index for the session interfaces corresponding to the target network-side edge device and the at least one other target network-side edge device.
In the above embodiment, when there are a plurality of session links between one target network-side edge device and one client-side edge device, the same index is configured for the plurality of session links; when a plurality of session links exist when a plurality of target network side edge devices are connected with one client side edge device, the same index is configured for the plurality of session links, so that the routing information of the same VPN network has the same service index, and the prefix route can be accurately identified.
An optional implementation manner is that, the generating, according to the service index, first service routing information carrying forwarding information includes:
allocating an MPLS label for the service index;
generating the first service routing information based on the MPLS label.
In the above embodiment, the target network side edge device allocates an MPLS label to the service index; further, first service routing information is generated based on the MPLS label.
An optional implementation manner is that the NLRI of the first service routing information includes: a routing specifier, an ethernet segment identifier, an ethernet label index, a service index, a default gateway address, and an MPLS label;
the NLRI of the prefix routing information includes: a routing specifier, an ethernet tag index, an IP prefix length, and an IP prefix address.
An optional implementation manner is that the prefix routing information carries the service index based on a preset service index extended community attribute; wherein the service index extended community attribute comprises at least four fields: two type value fields for indicating an extended community attribute type value, a reserved field, and an index field for indicating the service index.
An optional implementation manner is that, before configuring the service index for the session interface, the method further includes:
configuring an enabling service routing function for the target network side edge device and the EVPN neighbor;
and configuring the VPN service for the VPN site of the client-side edge device, and specifying protocol related information for the VPN service, so that the target network-side edge device and the other network-side edge devices can communicate based on the protocol related information.
In the above embodiment, by configuring the service-enabling routing function for the target network-side edge device and the EVPN neighbor, the VPN service is configured for the VPN site of the client-side edge device, and protocol-related information is specified for the VPN service, so that communication between the target network-side edge device and other network-side edge devices, between the target network-side edge device and the client-side edge device, can be performed based on the protocol-related information, so that the EVPN prefix route and the EVPN service route can be issued and received.
An optional implementation manner is that second service routing information carrying forwarding information sent by the other network-side edge device is received;
receiving each prefix routing information which is sent by the other network side edge devices and carries the service index;
and constructing a related routing forwarding table entry in a local routing table based on the second service routing information and the prefix routing information.
In the above embodiment, the target network-side edge device first receives second service routing information carrying forwarding information sent by other network-side edge devices, then receives each prefix routing information carrying a service index sent by other network-side edge devices, and finally constructs a relevant routing forwarding table entry in the local routing table based on the second service routing information and each prefix routing information, and the second service routing information and the prefix routing information are associated based on the service index, so that one second service routing information can be referred by a plurality of prefix routing information, thereby improving the routing payload rate and the routing information processing efficiency, and improving the learning performance of the EVPN prefix routing.
An optional implementation manner is that, if second service routing information corresponding to the service index sent by a plurality of other network-side edge devices is received, before the receiving of each prefix routing information carrying the service index sent by the other network-side edge devices, the method further includes:
importing the second service routing information into the routing table;
determining different next hop information in the second service routing information sent by each other network side edge device;
and in the routing table, establishing at least one next hop table entry corresponding to the second service routing information by taking the VPN service and the service index as key fields, wherein different next hop table entries correspond to different next hop information in the second service routing information.
In the foregoing embodiment, when the target network-side edge device receives service routing information corresponding to service indexes sent by a plurality of other network-side edge devices, the service routing information is imported into the local routing table, so as to determine different next hop information in the service routing information sent by each other network-side edge device, and then, in the routing table, at least one next hop table entry corresponding to the service routing information is established with the VPN service and the service index as key fields, so that the next hop table entry corresponding to the service routing information can be established in the local routing table according to the VPN service and the service index.
In an optional implementation manner, the next-hop table entry includes an inner layer tag, an outer layer tag, a next-hop address, and an outgoing interface; each next hop table entry is established based on the following method:
using the MPLS label distributed by the corresponding other network side edge device for the service index as the inner layer label in the next hop list item; and
and determining the next hop address, the outer layer label and the outgoing interface according to the next hop information.
An optional implementation manner is that, the constructing a relevant routing forwarding entry in the routing table based on the second service routing information and the prefix routing information includes:
searching corresponding second service routing information in the routing table according to the service index;
and cascading the prefix routing information and a next hop forwarding table entry corresponding to the second service routing information to obtain the route forwarding table entry.
In an optional embodiment, each session link established between the target network-side edge device and the client-side edge device is determined;
if the session links are determined to be in the disconnected state, deleting the first service routing information in a local routing table, and reserving prefix routing information related to the first service routing information; and the number of the first and second groups,
and sending a first message for indicating to delete the first service routing information to the other network-side edge device, so that the other network-side edge device deletes the first service routing information in the local routing table of the other network-side edge device according to the first message.
In the foregoing embodiment, if it is determined that each session link established between the target network-side edge device and the client-side edge device is in a disconnected state, the target network-side edge device only needs to delete the first service routing information associated with the target network-side edge device in the local routing table, and send the first packet for instructing to delete the first service routing information to the other network-side edge device, so that the other network-side edge device deletes the first service routing information in the local routing table of the other network-side edge device according to the first packet, and does not need to delete the other first service routing information and also does not need to delete the prefix routing information, thereby improving the EVPN routing convergence performance under the condition of a link failure, a protocol failure, or configuration change.
An optional implementation manner is that, if it is determined that all session links between the client-side edge device and other target network-side edge devices except the client-side edge device are in a disconnected state, the prefix routing information is deleted;
and sending a second message for indicating deletion of each prefix routing information to the other network-side edge device, so that the other network-side edge device deletes each prefix routing information and first service routing information sent by other target network-side edge devices except the target network-side edge device in the local routing table of the other network-side edge device according to the second message.
In the above embodiment, if the target network-side edge device determines that all session links established between the target network-side edge device and the client-side edge device are in a disconnected state except for the target network-side edge device, deleting each prefix routing information; and sending a second message for indicating deletion of each prefix routing information to other network side edge devices, so that the other network side edge devices delete each prefix routing information in a local routing table according to the second message and first service routing information sent by other target network side edge devices, thereby improving the EVPN routing convergence performance under the conditions of link failure, protocol failure or configuration change.
An optional implementation manner is that a third message sent by other network-side edge devices is received, where the third message is used to instruct to delete the second service routing information;
and deleting the second service routing information in a local routing table according to the first message, and reserving each prefix routing information related to the second service routing information.
In the foregoing embodiment, the target network-side edge device receives a third packet sent by another network-side edge device and used for instructing to delete the second service routing information, where the third packet is sent after the other network-side edge device determines that all session links between the target network-side edge device and the client-side edge device are in the disconnected state, and therefore, the target network-side edge device only needs to delete the second service routing information related to the other network-side edge device in the local routing table according to the first packet, and keep the other second service routing information and each prefix routing information related to the second service routing information, thereby improving the EVPN routing convergence performance under the condition of a link failure, a protocol failure, or a configuration change.
An optional implementation manner is that a fourth message, which is sent by the other network-side edge device and used for instructing to delete each prefix routing information related to the second service routing information, is received;
and deleting the prefix routing information and second service routing information sent by the network side edge equipment except the other network side edge equipment in a local routing table according to the fourth message.
In the foregoing embodiment, the target network-side edge device receives the fourth packet sent by the other network-side edge device and used for instructing to delete each piece of prefix routing information related to the second service routing information, and deletes each piece of prefix routing information in the local routing table according to the fourth packet and the second service routing information sent by the other network-side edge device, thereby improving the EVPN routing convergence performance under the condition of a link failure, a protocol failure, or a configuration change.
The routing information processing device provided by the embodiment of the application is applied to a target network side edge device in an EVPN, and comprises:
a first configuration unit, configured to configure a service index for a session interface, where the session interface is an interface between the target network-side edge device and a client-side edge device, and the service index is used to identify a VPN service to which a public network connected to the client-side edge device belongs;
a first sending unit, configured to generate, according to the service index, first service routing information carrying forwarding information if the VPN service is in an activated state, and send the first service routing information to other network-side edge devices, where the forwarding information is used to represent a route forwarding path corresponding to the service index;
a second sending unit, configured to generate, based on each public network connected to the client-side edge device, each prefix routing information carrying the service index, and send each prefix routing information to the other network-side edge device, so that the other network-side edge device constructs, based on the first service routing information and each prefix routing information, a relevant route forwarding table entry in a local routing table, where different prefix routing information corresponds to different public networks.
Optionally, after configuring the service index for the session interface and before generating the first service routing information carrying the forwarding information according to the service index, the apparatus further includes a first determining unit, configured to:
determining respective session links established between the target network-side edge device and the client-side edge device;
and if at least one session link is in an active state, setting the VPN service to be in an active state.
Optionally, the first configuration unit may be configured to perform at least one of the following operations:
if a plurality of session links exist between the target network side edge device and the client side edge device, configuring the same service index for each session interface corresponding to each session link;
if the client-side edge device is connected to at least one other target network-side edge device except the target network-side edge device, configuring the same service index for the session interfaces corresponding to the target network-side edge device and the at least one other target network-side edge device.
Optionally, the first sending unit is specifically configured to:
allocating an MPLS label for the service index;
generating the first service routing information based on the MPLS label.
Optionally, the NLRI of the first service routing information includes: a routing specifier, an ethernet segment identifier, an ethernet label index, a service index, a default gateway address, and an MPLS label;
the NLRI of the prefix routing information includes: a routing specifier, an ethernet tag index, an IP prefix length, and an IP prefix address.
Optionally, the second sending unit is specifically configured to:
the prefix routing information carries the service index based on the preset service index extended community attribute; wherein the service index extended community attribute comprises at least four fields: two type value fields for indicating an extended community attribute type value, a reserved field, and an index field for indicating the service index.
Optionally, the apparatus further comprises:
the first processing unit is used for configuring an enabling service routing function for the target network side edge device and the EVPN neighbor before the first configuration unit configures the service index for the session interface;
and configuring the VPN service for the VPN site of the client-side edge device, and specifying protocol related information for the VPN service, so that the target network-side edge device and the other network-side edge devices can communicate based on the protocol related information.
Optionally, the apparatus further comprises:
a first receiving unit, configured to receive second service routing information carrying forwarding information sent by the other network-side edge device;
a second receiving unit, configured to receive prefix routing information that carries the service index and is sent by the other network-side edge device;
and the constructing unit is used for constructing a related routing forwarding table entry in a local routing table based on the second service routing information and each prefix routing information.
Optionally, the apparatus further includes an importing unit, configured to:
if second service routing information corresponding to the service index sent by a plurality of other network-side edge devices is received, before the receiving of each prefix routing information carrying the service index sent by the other network-side edge device, the method further includes:
importing the second service routing information into the routing table;
and determining different next hop information in the second service routing information sent by each other network side edge device.
Optionally, the next hop table entry includes an inner layer tag, an outer layer tag, a next hop address, and an outgoing interface; each next hop table entry is established based on the following method:
using the MPLS label distributed by the corresponding other network side edge device for the service index as the inner layer label in the next hop list item; and
and determining the next hop address, the outer layer label and the outgoing interface according to the next hop information.
Optionally, the building unit is specifically configured to:
searching corresponding second service routing information in the routing table according to the service index;
and cascading the prefix routing information and a next hop forwarding table entry corresponding to the second service routing information to obtain the route forwarding table entry.
Optionally, the apparatus further comprises:
a second determining unit configured to determine each session link established between the target network-side edge device and the client-side edge device;
a first deleting unit, configured to delete the second service routing information in a local routing table if it is determined that each session link is in a disconnected state, and retain prefix routing information related to the second service routing information;
a third sending unit, configured to send, to the other network-side edge device, a first packet for instructing to delete the second service routing information, so that the other network-side edge device deletes, according to the first packet, the second service routing information in the local routing table of the other network-side edge device.
Optionally, the apparatus further comprises:
a second processing unit, configured to delete each prefix routing information if it is determined that all session links between the client-side edge device and other target network-side edge devices except the target network-side edge device are in a disconnected state;
and sending a second message for indicating deletion of each prefix routing information to the other network-side edge device, so that the other network-side edge device deletes each prefix routing information and second service routing information sent by other target network-side edge devices except the target network-side edge device in the local routing table of the other network-side edge device according to the second message.
Optionally, the apparatus further comprises:
a third receiving unit, configured to receive a third packet sent by the other network-side edge device and used to instruct to delete the first service routing information;
and a second deleting unit, configured to delete the first service routing information in a local routing table according to the third packet, and retain prefix routing information related to the first service routing information.
Optionally, the apparatus further comprises:
a third processing unit, configured to receive a fourth packet sent by the other network-side edge device and used to instruct to delete each prefix routing information related to the second service routing information;
and deleting the prefix routing information and second service routing information sent by the network side edge equipment except the other network side edge equipment in a local routing table according to the fourth message.
An electronic device provided in an embodiment of the present application includes a processor and a memory, where the memory stores a program code, and when the program code is executed by the processor, the processor is caused to execute any one of the steps of the routing information processing method.
An embodiment of the present application provides a computer-readable storage medium, which includes program code, when the program product runs on an electronic device, the program code is configured to enable the electronic device to execute any one of the steps of the routing information processing method described above.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1A is an optional schematic diagram of a prefix routing information NLRI format of EVPN IPv4 in the related art;
fig. 1B is an optional schematic diagram of a prefix routing information NLRI format of EVPN IPv6 in the related art;
fig. 2 is a flowchart of an implementation of a method for processing routing information according to an embodiment of the present application;
fig. 3A is a network topology diagram in an embodiment of the present application;
fig. 3B is a flowchart illustrating an overall interaction between network-side edge devices according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram of an NLRI format of service routing information in the embodiment of the present application;
fig. 5 is a flowchart of a route information generation in an embodiment of the present application;
fig. 6 is a routing representation intent on the first network-side edge PE1 in an embodiment of the present application;
fig. 7 is a schematic diagram of a prefix routing information NLRI format in an embodiment of the present application;
FIG. 8 is a diagram illustrating a service index extended community attribute format according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a network-side edge device in an embodiment of the present application;
fig. 10 is a flowchart of another implementation of a routing information processing method in an embodiment of the present application;
fig. 11 is a schematic diagram illustrating a structure of a service route forwarding table entry in an embodiment of the present application;
fig. 12 is a schematic diagram illustrating a structure of a routing information forwarding table entry in an embodiment of the present application;
fig. 13 is a schematic diagram illustrating a structure of a routing information forwarding table entry after a session link is disconnected in an embodiment of the present application;
fig. 14 is a flowchart of route convergence of a network-side edge device in an embodiment of the present application;
fig. 15 is a timing diagram illustrating an interaction procedure between network-side edge devices according to an embodiment of the present application;
fig. 16 is a flowchart of a route convergence method in an embodiment of the present application;
FIG. 17 is a flow chart of another route convergence method in an embodiment of the present application;
fig. 18 is a schematic structural diagram of a routing information processing apparatus in an embodiment of the present application;
fig. 19 is a schematic diagram of a hardware component structure of an electronic device in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments, but not all embodiments, of the technical solutions of the present application. All other embodiments obtained by a person skilled in the art without any inventive step based on the embodiments described in the present application are within the scope of the protection of the present application.
Some concepts related to the embodiments of the present application are described below.
1. In the embodiment of the present application, the term "and/or" describes an association relationship of associated objects, and means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
2. The term "NLRI (Network Layer availability Information)" in the embodiments of the present application is included in BGP routing updates, which describe a route and how it is reached. One NLRI is a prefix, and one BGP update message carries one or more NLRI prefixes and one routing NLRI prefix.
3. In the embodiment of the present application, the term "EVPN" is a two-layer VPN, where the control plane interacts EVPN routing information through MP-BGP, and the data plane may forward a packet in an MPLS or VXLAN encapsulation manner.
4. In the embodiment of the present application, the term "RT (Route-Target)" is an important attribute carried by a VPNv4 Route, and determines transceiving and filtering of a VPN Route, and a PE (Provider Edge, also called network-side Edge) distinguishes routes between different VPNs depending on the RT attribute, and also becomes a key point in MP-BGP (also called MBGP) testing. And filtering the VPN route by using the RT attribute.
5. In the embodiment of the present application, the term "VRF" (Virtual Routing Forwarding) is provided for identifying different VPN information on an edge side device, and a concept of VRF is proposed. In L3VPN networking, routes between different VPNs are isolated by VRFs. Each VRF may be considered as a virtual PE device, managing individual VPN traffic, and storing routing information. Each VRF contains routing information for routes received directly from the customer edge side and routes received from other network-side edge routers that have acceptable BGP attributes associated with that VRF.
The following briefly introduces the design concept of the embodiments of the present application:
the EVPN route types are divided into various types according to different purposes, wherein 5 types of IP Prefix routes can be used for constructing the L3 VPN. Referring to fig. 1A and 1B, according to the protocol format definition of EVPN IP prefix routing information, where fig. 1A is a format of prefix routing information NLRI of EVPN IPv4 in the related art, and fig. 1B is a format of prefix routing information NLRI of EVPN IPv6 in the related art. Each piece of EVPN IP prefix routing information needs to carry ESI (Ethernet Segment Identifier), E-Tag (Ethernet Tag ID ), GW (Gateway, default Gateway) address and MPLS Tag information, which are actually the same for the same user service, so that the same information is repeatedly carried in each piece of EVPN IP prefix routing information, and the number of routes that can be carried in one BGP update packet (standard BGP update packet is 4096 bytes) is small, and the routing payload rate and the routing information processing efficiency are low.
In addition, the EVPN supports multi-homing, and when the same site accesses the VXLAN network through a plurality of VTEPs, a plurality of paths connecting the site can all forward the traffic so as to improve the utilization rate of the network bandwidth. Because the EVPN supports multiple attributions, the EVPN can be used for redundancy protection of PE devices, when a failure occurs, traffic switching is preferentially performed through a type 1 Ethernet Auto-discovery (Ethernet Auto-discovery route) or a type 4 Ethernet Segment (Ethernet route) route, but all types 5 of IP prefix routing information still need to be notified and cancelled between devices, so that the amount of information interaction and the amount of processing between devices cannot be reduced, and the EVPN protected Ethernet physical link with multiple attributions cannot be converged quickly when a protocol failure or a management configuration is deleted.
In view of this, the present application provides a routing information processing method, which improves the protocol effective carrying rate in the EVPN protocol interaction process and improves the EVPN prefix routing information learning performance by introducing VPN Service (also called Service/user Service, abbreviated as Service) and EVPN Service routing.
Further, the application also provides a route convergence method, which improves the EVPN route convergence performance under the conditions of link failure, protocol failure or configuration change.
The preferred embodiments of the present application will be described below with reference to the accompanying drawings of the specification, it should be understood that the preferred embodiments described herein are merely for illustrating and explaining the present application, and are not intended to limit the present application, and that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
The following detailed description is made for a routing information processing method:
referring to fig. 2, it is a flowchart of an implementation of a routing information processing method provided in this embodiment of the present application, applied to a target network-side edge device, and a specific implementation flow of the method is as follows:
s21: configuring a service index for a related session interface by the edge device at the target network side;
the session interface is an interface of the target network-side edge device and the client-side edge device, and the service index is used for identifying the VPN service to which the public network connected with the client-side edge device belongs.
In this embodiment, the target network-side edge device and the client-side edge device are connected via a session interface, and the service index configured for the session interface is a unique service index in the designated VPN network to identify to which VPN service a session between the target network-side edge device and the client-side edge device belongs.
The device at the edge of the target network side can be used as a distribution end and also can be used as a receiving end. In the embodiment of the present application, for convenience of distinction, a publishing end of the EVPN route is hereinafter referred to as a first network-side edge device, a second network-side edge device is referred to as a receiving end of the EVPN route, and in an actual scenario, two PE devices are generally both a publishing end and a receiving end.
When the target network-side edge device is a first network-side edge device, the other network-side edge devices may be second network-side edge devices, or may be first network-side edge devices other than the target network-side edge device. Similarly, when the target network-side edge device is a second network-side edge device, the other network-side edge devices may be the first network-side edge device, or may be second network-side edge devices other than the target network-side edge device.
Fig. 3A is a diagram of a network topology according to an embodiment of the present application. The CE1 is a client-side edge device, the PE1 and the PE2 are first network-side edge devices, the PE3 is a second network-side edge device, two session links are established between the CE1 and the PE1 through two session interfaces, and one session link is established between the CE1 and the PE2 through one session interface. As shown in fig. 3A, for example, when the target network-side edge device is the first network-side edge device PE1, the other network-side edge devices may be the first network-side edge device PE2 or the second network-side edge device PE 3.
The IP addresses of the public network to which CE1 is connected are: 100.1.1.1/32 ~ 100.1.255.255/32, total 255 IP addresses.
In an optional implementation manner, when configuring a service index for a relevant session interface, the configuration of a first network-side edge device is mainly performed, that is, taking a target network-side edge device as the first network-side edge device as an example, the configuration of the service index may be specifically divided into the following two cases:
in case one, if a plurality of session links exist between the target network-side edge device and the client-side edge device, the same service index is configured for each session interface corresponding to each session link.
Specifically, if a plurality of links exist between a first network-side edge device and a client-side edge device for connection, configuring the same service index on a plurality of session interfaces corresponding to the first network-side edge device; that is, a service index on the first network-side edge device will be bound to multiple session interfaces.
For example, referring to fig. 3A, two session links are established between CE1 and PE1, and there are two corresponding session interfaces, where one session interface is Gi0/0 and the other is Gi0/1, and the same Service index, for example, Service index (Service ID)1, i.e., Service ID 1, is configured for the two session interfaces.
And in case two, if the target network-side edge device is connected to the client-side edge device simultaneously with at least one other target network-side edge device except the target network-side edge device, configuring the same service index for the session interfaces corresponding to the target network-side edge device and the at least one other network-side edge device.
In this case, the other target network-side edge device is the other first network-side edge device.
Specifically, if a plurality of first network-side edge devices are simultaneously connected to one client-side edge device, the same service index is configured on the session interfaces corresponding to the plurality of first network-side edge devices.
For example, referring to fig. 3A, where CE1 establishes session links with PE1 and PE2, respectively, the session interfaces corresponding to PE1 and PE2 are configured with the same Service index, for example, both are Service ID 1.
In addition, the CE2 establishes a session link with the PE3, and at this time, the PE3 serves as a first network-side edge device corresponding to the CE2, and a Service index, for example, Service index 2, that is, Service ID 2, is configured for the session interface corresponding to the PE 3.
Two session links are arranged between the PE1 and the CE1, the PE1 is correspondingly provided with two session interfaces, one session interface is Gi0/0, and the other session interface is Gi 0/1; there is a session link between PE2 and CE1, and PE2 has a session interface Gi0/3, and the same Service index, for example, Service ID 1, is configured for the three session interfaces.
In the embodiment of the application, the protocol session from the CE side and the protocol session between the PE sides are associated through a newly proposed VPN Service structure.
S22: if the VPN service is in an activated state, the target network side edge device generates first service routing information carrying forwarding information according to the service index, and sends the first service routing information to other network side edge devices;
and the forwarding information is used for representing a route forwarding path corresponding to the service index.
In the embodiment of the present application, by using the newly proposed EVPN Service routing information (i.e. the first Service routing information in this document), the forwarding path part of EVPN prefix routing in the related art can be separated, and the interactive forwarding path information is independent of the number of routing prefixes and is only related to VPN Service.
Fig. 3B is a flowchart illustrating an overall interaction between network-side edge devices according to an embodiment of the present application. In the interaction flow of the PE-a and the PE-B, the PE-a splits the prefix route originally carrying the forwarding information into two parts, wherein one part is the Service route carrying the forwarding information (i.e., the first Service route information), and the other part is the prefix route carrying the Service index (i.e., the prefix route information).
In the embodiment of the application, the Service route can be referred by a plurality of prefix routes, and the Service routes are the same for the same user, so the Service route is only required to be sent once by adopting the method of the application without repeated sending, the number of routes which can be carried in a BGP update message is larger, the route payload rate and the route information processing efficiency are improved, and the cost of exchanging forwarding information carried by the prefix routes between devices can be reduced.
S23: the target network side edge device generates each prefix routing information carrying the service index based on each public network connected with the client side edge device, and sends each prefix routing information to other network side edge devices, so that the other network side edge devices construct related routing forwarding table items in a local routing table based on the first service routing information and each prefix routing information, and different prefix routing information corresponds to different public networks.
For example, CE1 is connected to 255 × 255 public networks. PE1 generates 255 × 255 prefix routing information based on the IP addresses of the public networks, where one IP address corresponds to one prefix routing information, and the prefix routing information includes the same Service index, i.e., Service ID 1.
In the embodiment of the application, the target network side edge device firstly generates first service routing information carrying forwarding information according to the service index, and then only needs to send the first service routing information to other network side edge devices; and then, based on each public network connected by the client-side edge device, generating each prefix routing information carrying the service index, and sending each prefix routing information to other network-side edge devices, so that the other network-side edge devices can construct related routing forwarding table entries in the local routing table based on the first service routing information and each prefix routing information. In the application, the first service routing information and the prefix routing information can be associated based on the service index, so that one first service routing information can be referred by a plurality of prefix routing information, the routing payload rate and the routing information processing efficiency are improved, and the learning performance of the EVPN prefix routing is improved.
In an optional implementation manner, after configuring a service index for a relevant session interface, before generating first service routing information carrying forwarding information according to the service index, the state of the VPN service needs to be determined. The method mainly performs the determination based on the first network-side edge device, and the following mainly takes the target network-side edge device as the first network-side edge device as an example, and introduces details of the determination method of the VPN service state.
Specifically, first, a first network-side edge device determines each session link established between itself and a client-side edge device; setting the VPN service to an active state if at least one session link is active.
For example, as shown in fig. 3A, PE1 establishes two OSPF protocol session links (session links for short) with CE1 via session interfaces Gi0/0, Gi 0/1. If at least one session link is in an UP (active) state, for example, the session link established by PE1 with CE1 through session interface Gi0/0 is in an UP state, the corresponding VPN service may be set to an active state.
In this embodiment of the present application, after determining that the VPN service to which the first network-side edge device belongs is in an activated state, the first network-side edge device may generate the first service routing information based on the service index configured in the foregoing process.
In an optional implementation manner, when the first network-side edge device generates the first service routing information carrying the forwarding information according to the service index, the method specifically includes the following steps:
firstly, a first network side edge device allocates an MPLS label for a service index, and an output interface of the allocated MPLS label is an UP output interface bound by the service index; further, first service routing information is generated based on the MPLS label.
Optionally, the NLRL of the first service routing information in this embodiment of the present application includes but is not limited to:
routing specifier, ethernet segment identifier, ethernet label index, service index, default gateway address, MPLS label.
An NLRL format of service routing information in the present application is shown in fig. 4, and specifically includes the following contents:
RD (8 bytes): route distingguisher, Route Distinguisher, is used to distinguish the routes of different VPNs.
Ethernet Segment Identifier (10 bytes): an ethernet segment identifier.
Ethernet Tag ID (4 bytes): the ethernet tag index, the Service route for EVPN prefix route is typically 0.
Service ID (4 bytes): the Service index is the index value of Service, and the Service index value of the Service ID extended community attribute corresponding to the EVPN prefix route.
GW IP Address (4 bytes or 16 bytes): gateway IP address, i.e. default gateway address.
MPLS Label (3 bytes): the MPLS label value.
The following describes a generation process of service routing information in the embodiment of the present application with reference to fig. 5. Referring to fig. 5, it is a flowchart of service routing information generation, and the specific implementation process is as described above, including the following steps:
step 1: distributing MPLS labels for the VPN Service IDs, wherein the output interfaces of the distributed MPLS labels are UP output interfaces bound by the VPN Service IDs;
step 2: generating an EVPN Service route for the VPN Service ID;
and step 3: and the generated EVPN Service route is announced to other PE equipment (such as second network side edge equipment) through a BGP Update message, and the next hop of the announced EVPN Service route is the source address of an EVPN neighbor on the PE-A.
Referring to fig. 6, which is a local routing table on the first network-side edge device PE1, PE1 is connected to the customer-side edge device CE1 through two session interfaces Gi0/0 and Gi0/1, where one iterates to the direct-connection next-hop address 40.1.1.2, the outgoing interface is Gi0/0, the other iterates to the direct-connection next-hop address 50.1.1.2, and the outgoing interface is Gi 0/1.
In addition, the first network-side edge device PE2 may also send some routing information of itself to the PE1, only the routing information corresponding to the two session links related to the PE1 is illustrated in fig. 6, and the routing information related to the PE2 may actually establish a related routing table entry on the local routing table of the PE1, which is not shown in fig. 6, and is not limited herein.
It should be noted that, in the embodiment of the present application, the routes in the routing table local to the first network-side edge device (e.g., PE1, PE2) are from the client-side edge device (e.g., CE1), so that the next hop of the forwarding table seen on the first network-side edge device is the associated CE interface and the next hop. Taking PE1 as an example, since there are two links between PE1 and CE1, there are two outgoing interfaces and next hops, and there are two next hops correspondingly, but these next hops and outgoing interfaces are ordinary IP paths and do not carry MPLS labels. The same is true on PE2, but since there is only 1 link with CE1, there is only one next hop and egress interface. On a second network-side edge device (PE3), the local routing table further carries an MPLS label, as described in more detail below.
In the embodiment of the present application, through a newly proposed VPN Service structure and EVPN Service routing, a forwarding path part of an EVPN prefix routing in the related art is separated, and interactive forwarding path information is independent of the number of routing prefixes and is only related to VPN Service, so that a protocol carrying rate and routing information processing efficiency can be effectively improved, and rapid convergence of routing is facilitated, which will be described in detail below.
Optionally, the NLRI of the prefix routing information in the embodiment of the present application includes but is not limited to:
routing specifier, Ethernet tag index, IP prefix length, IP prefix address.
Referring to fig. 7, an NLRL format of prefix routing information in the embodiment of the present application specifically includes the following contents:
RD: route distingguisher, route distinguisher.
Ethernet Tag ID: the ethernet tag index.
IP Prefix Length: IP prefix length (IPL for short), 1 byte size, in bits. For the IPv4 route, the legal value is 0-32; for IPv6 routes, the legal value is 0-128.
IP Prefix: the IP prefix address, namely the IP address of the public network, is 0-16 bytes in length, and is specifically determined according to the IPL field, and the specific calculation formula is as follows:
Figure BDA0003264587650000201
rounded up, where IPL is the value of IP Prefix Length.
In the above embodiment, the first network-side edge device generates EVPN prefix routes carrying service indexes from the routing information received from the client-side edge device. Taking the original EVPN IPv4 Prefix route shown in fig. 1A as an example, one Prefix route NLRI occupies 34 bytes, while the NLRI of the Prefix route information in the present application only includes RD, Ethernet Tag ID, IP Prefix Length, IP, and IP Prefix, and therefore only occupies 13-17 bytes of bytes; taking the original EVPN IPv6 prefix route shown in fig. 1B as an example, one prefix route NLRI occupies 58 bytes, whereas the NLRI of the prefix route information in the present application only needs to occupy 13-29 bytes. The NLRI of the Service routing information in the application comprises RD, Ethernet Segment Identifier, Ethernet Tag ID, Service ID and GW IP Address MPLS Label, and because the Service routing information in the application only needs to be sent once, the number of bytes of prefix routing information is reduced compared with the number of bytes of original prefix routing information, so that under the condition that the sending times of the prefix routing information are the same, the number of bytes occupied is reduced, a message can carry more routing information, and the routing effective load rate and the routing information processing efficiency are improved.
In the embodiment of the present application, in order to carry the Service ID in the BGP update message, in the embodiment of the present application, a Service ID extended community attribute is newly added to carry the Service ID, and the community attribute is extended through the Service index, so that the prefix route carries the Service index, that is, the prefix route information extends the community attribute carried the Service index based on the preset Service index.
Optionally, the service index extended community attribute lattice includes at least four fields: two type value fields for indicating the extended community attribute type value, a reserved field, and an index field for indicating the service index.
Referring to fig. 8, a schematic diagram of a format of a Service ID extended community attribute in the embodiment of the present application is shown, where the meaning of each field is as follows:
type right, Type low: two type value fields are The type values of The extended group attribute, a Service ID extended group attribute is added in The method, and a corresponding type value needs to be registered to The IANA (Internet Assigned Numbers Authority) during actual implementation;
res: reserved field, 2 bytes long, not used at present, pad 0;
service ID: and the index field, namely Service index, is 4 bytes long and is used for identifying the Service to which the EVPN prefix route belongs.
For example, the PE1 converts the OSPF routes 100.1.1.1/32-100.1.255.255/32 received from the CE1 into EVPN prefix route information and announces the EVPN prefix route information to the PE2 and the PE 3. These EVPN prefix routing information carries RT attributes 100:1 and Service index extended community attributes, which carry Service ID 1. Based on the received service routing information and prefix routing information, PE2 and PE3 may construct related routing forwarding entries.
In the foregoing embodiment, the prefix routing information may extend the community attribute carrying Service index based on the preset Service index, so that the Service routing information may be searched according to the value of the Service ID carried by the prefix routing information, and the corresponding forwarding table entry may be associated.
In an optional implementation manner, before the first network-side edge device configures the service index for the relevant session interface, the following process is further included:
the method comprises the steps of firstly configuring an enabling service routing function for the network side device and the EVPN neighbor, further configuring VPN service for a VPN site of the client side edge device, and appointing protocol related information for the VPN service, so that communication can be carried out between the first network side edge device and the second network side edge device and between the first network side edge device and the client side edge device based on the protocol related information.
Specifically, under the default condition, the EVPN prefix route issued by the EVPN neighbor is still issued and received in the original form, and the EVPN prefix route and the EVPN service route can be issued and received in the method only after the EVPN neighbor enabling service routing function is configured.
For example, a VPN Service is configured for a VPN site of a CE on a PE-a, a user side interface and a protocol are specified for the VPN Service, and a network side protocol type is specified. The user-side protocol type may include an existing IGP protocol, such as OSPF, ISIS, or BGP, and the network-side protocol type is a BGP EVPN protocol.
Fig. 9 is a schematic structural diagram of a network-side edge device according to an embodiment of the present application, including: the system comprises a configuration module, a VPN Service management module, an EVPN route management module and a forwarding table entry management module.
The configuration module is used for realizing basic configuration of network communication, and comprises: the method comprises the steps that an EVPN service-route function is locally configured and enabled on a PE through a configuration module; configuring a service ID for an interface connected with the CE on the PE through a configuration module; and configuring an enabling service routing function for the EVPN neighbor on the PE through a configuration module.
For example, the first network-side edge device PE1 configures and establishes an OSPF protocol with the customer-side edge device CE1 through session interfaces Gi0/0, Gi0/1, and triggers and notifies the VPN Service management module after OSPF protocol sessions of Gi0/0, Gi0/1 on the PE1 are established;
and the VPN Service management module is used for analyzing the state of the VPN Service based on the state of the session link between the PE and the CE.
For example, when the VPN Service management module on PE1 senses that at least one protocol session at the CE end to which VPN Service1 is bound is in the established state, the VPN Service state is updated to the activated state (initially, the activated state).
And the EVPN route management module is used for generating service route information.
For example, the EVPN route management module on PE1 senses that the VPN Service ID 1 is changed from the disconnected state to the activated state, and generates an EVPN Service route, and announces the EVPN Service route to PE2 and PE3 devices through a BGP update message, where the RD value of the EVPN Service route is 100:1, the Ethernet Segment Identifier is 0, the Ethernet Tag ID is 0, the Service ID is 1, the GW IP Address value is 0, and the MPLS Label value is the Label 1000 of VRF VPN1(VPN Service1, 1 is an Identifier), and carries the RT attribute 100:1, and the next hop Address is 1.1.1.1.
And the forwarding table item management module is used for forwarding the message carrying the routing information.
For example, the PE3 receives a BGP update message carrying an EVPN Service route advertised by the PE1, introduces the EVPN Service route into the VRF VPN1, and installs a Service ID forwarding table entry to the FIB forwarding table, where the Service ID is 1, the recursive next hop is 1.1.1.1, and the VPN label is 1000. And iterating the public network tunnel label according to the recursive next hop address 1.1.1.1, wherein the direct connection address is 10.1.1.2, the output interface is Gi0/1, and the tunnel label is 1001.
In an optional implementation manner, if the first network-side edge device determines that each current session link is in a disconnected state, deleting the first service routing information in the local routing table, and retaining each prefix routing information related to the first service routing information; and then sending a first message for indicating to delete the first service routing information to a second network side edge device, wherein the second network side edge device deletes the first service routing information in the local routing table according to the first message.
For example, see fig. 3A, where two session links are established between CE1 and PE 1. When one of the session links between the CE1 and the PE1 is disconnected, the VPN Service management module on the PE1 detects that there is still another established session link in the VPN Service1, and the state of the VPN Service1 is still active.
When both session links between CE1 and PE1 are disconnected, the VPN Service management module on PE1 detects that there is no established session link for VPN Service1, and sets the state of VPN Service1 to the disconnected state. An EVPN route management module on the PE1 senses that the VPN Service ID 1 is changed from an established state to a disconnected state, searches a corresponding EVPN Service route according to VRF VPN1 and ID value 1 to which the VPN Service1 belongs, deletes the EVPN Service route, and announces the EVPN Service route to the PE3 through a BGP update message (first message), and the PE3 receives the BGP update message, searches a corresponding EVPN Service route in a local routing table, and deletes the EVPN Service route.
In the above embodiment, the EVPN route management module on the PE3 receives the BGP update message of the revocation of the EVPN Service route advertised by the PE1, and deletes the EVPN Service route from the PE1 VPN Service1, where only one path from the PE2 remains in the EVPN Service route of the VPN Service 1. The EVPN route management module updates the forwarding table entry of the VPN Service1 to the forwarding module and deletes the path from the PE 1. Because the prefix route is associated to the VPN Service1, the flow for accessing the VPN Service1 can be only drained to the PE2 only by updating the forwarding table entry of the VPN Service1, but not to the PE1, and the whole convergence time is irrelevant to the number of the prefix routes on the VPN Service1, so that the convergence speed is improved, and the convergence time is reduced.
Optionally, if the first network-side edge device determines that all session links between the first network-side edge device and the client-side edge device except the first network-side edge device are in a disconnected state, deleting each prefix routing information; and then sending a second message for indicating deletion of each prefix routing information to a second network side edge device, wherein the second network side edge device deletes each prefix routing information in the local routing table according to the second message and other first service routing information sent by the first network side edge device.
For example, referring to fig. 3A, two session links are established between CE1 and PE1, one session link is established between CE1 and PE2, and when all three session links between CE1 and PE1 and PE2 are disconnected, the VPN Service management module on PE1 detects that there are no established session links between VPN Service1 and VPN Service 2, and sets the states of VPN Service1 and VPN Service 2 to the disconnected state. An EVPN route management module on the PE1 senses that the VPN Service ID 1 and the VPN Service ID 2 are changed from an activated state to a disconnected state, searches and deletes corresponding prefix routes, and announces the prefix routes to the PE3 through BGP update messages (second messages), and the PE3 receives the BGP update messages, searches and deletes corresponding prefix routes and Service routes in a local routing table.
An embodiment of a routing information processing method according to the present application is specifically described below with reference to fig. 3A:
VPN routing for CE 1: 100.1.1.1/32 ~ 100.1.255.255/32, the PEs are adjacent to each other in terms of EVPN.
1. At PE1, PE3 configures evpn service-route (service route) enabling function for VRF vpn1 through configuration module.
PE1(config)#ip vrf vpn1
PE1(config-vrf)#rd 100:1
PE1(config-vrf)#route-target both 100:1 evpn
PE1(config-vrf)#evpn mpls routing enable
PE1(config-vrf)#evpn service-routing enable
2. The EVPN neighbors are configured at PE1 with a Service-enabled routing function via a configuration module.
PE1(config)#router bgp 100
PE1(config-router)#neighbor 2.2.2.2 remote-as 100
PE1(config-router)#neighbor 2.2.2.2 update-source loopback 0
PE1(config-router)#neighbor 3.3.3.3 remote-as 100
PE1(config-router)#neighbor 3.3.3.3 update-source loopback 0
PE1(config-router)#address-family ipv4 vrf vpn1
PE1(config-router)#address-family l2vpn evpn
PE1(config-router-af)#neighbor 2.2.2.2 activate
PE1(config-router-af)#neighbor 2.2.2.2 service-routing
PE1(config-router-af)#neighbor 3.3.3.3 activate
PE1(config-router-af)#neighbor 3.3.3.3 service-routing
Similarly, PE2, PE3 devices are configured similarly to PE1 devices.
3. PE1 establishes OSPF protocol via configuration between interfaces Gi0/0, Gi0/1 and CE 1.
When a customer-side edge device CE1 accesses a first network-side edge device PE1 with two interfaces and accesses a first network-side edge device PE2 with one interface, a service index 1 is configured on PE1 and PE2 for an interface connected to CE1 through a configuration module; another customer-side edge device CE2 accesses the first network-side edge device PE3 with an interface, and configures a service index 2 for the interface connected to the CE2 through a configuration module on PE 3; the VPN route of CE1 is 100.1.1.1/32 ~ 100.1.255.255/32, the configuration of PE1 ~ PE3 is as follows:
PE1(config)#vpn service-id 1 vrf vpn1
PE1(config-vpn-svc)#customer edge
PE1(config-vpn-svc-ce)#route-proto ospf 1
PE1(config-vpn-svc-ce)#xconnect interface gigabitEthernet 0/0
PE1(config-vpn-svc-ce)#xconnect interface gigabitEthernet 0/1
PE1(config-vpn-svc)#provider edge
PE1(config-vpn-svc-pe)#route-proto bgp-evpn
PE2(config)#vpn service-id 1 vrf vpn1
PE2(config-vpn-svc)#customer edge
PE2(config-vpn-svc-ce)#route-proto ospf 1
PE2(config-vpn-svc-ce)#xconnect interface gigabitEthernet 0/0
PE2(config-vpn-svc)#provider edge
PE2(config-vpn-svc-pe)#route-proto bgp-evpn
PE3(config)#vpn service-id 2 vrf vpn1
PE3(config-vpn-svc)#customer edge
PE3(config-vpn-svc-ce)#route-proto ospf 1
PE3(config-vpn-svc-ce)#xconnect interface gigabitEthernet 0/0
PE3(config-vpn-svc)#provider edge
PE3(config-vpn-svc-pe)#route-proto bgp-evpn
4. the PE1 triggers the announcement to the VPN Service management module through OSPF protocol session establishment of interfaces Gi0/0, Gi 0/1.
5. The VPN Service management module of PE1 senses that the CE end protocol session bound by VPN Service1 is in the established state, and then updates the VPN Service state to the established state (initially, disconnected state).
6. An EVPN route management module on the PE1 senses that the VPN Service ID 1 is changed from a disconnected state to an established state, generates an EVPN Service route, and announces the EVPN Service route to the PE2 and PE3 equipment through a BGP update message.
The EVPN Service route RD value is 100:1, the Ethernet Segment Identifier value is 0, the Ethernet Tag ID is 0, the Service ID is 1, the GW IP Address value is 0, the MPLS Label Label value is Label 1000 of VRF vpn1, the Label carries RT attribute 100:1, and the next hop Address is 1.1.1.1.
7. PE3 receives a BGP update message carrying an EVPN Service route announced by PE1, introduces the EVPN Service route into VRF VPN1, and installs a Service ID forwarding table entry to an FIB forwarding table, wherein the Service ID is 1, the recursion next hop is 1.1.1.1, and the VPN label is 1000. And iterating the public network tunnel label according to the recursive next hop address 1.1.1.1, wherein the direct connection address is 10.1.1.2, the output interface is Gi0/1, and the tunnel label is 1001.
8. The PE1 converts the OSPF routes 100.1.1.1/32-100.1.255.255/32 received from the CE1 into EVPN prefix routes and announces the EVPN prefix routes to the PE2 and the PE 3. These EVPN prefix routes carry RT attributes 100:1 and Service ID extended community attributes, which carry Service ID 1.
In addition, PE2 may also announce service routing information and prefix routing information to PE1 and PE3, where PE1 is a target network-side edge device, and when PE2 is another network-side edge device, the service routing information sent by PE2 to PE1 is the service routing information that PE2 generates forwarding information related to PE2 according to a service index, that is, the second service routing information in this embodiment of the present application.
In this embodiment of the present application, the second service routing information is the same as the content represented by the first service routing information in nature, and NLRI thereof includes: specifically, referring to fig. 4, "first" and "second" herein refer to a sender of service routing information, where the sender of the first service routing information is a target network-side edge device, the sender of the second service routing information is another network-side edge device, and repeated parts are not described again.
9. The PE3 receives BGP update messages carrying EVPN prefix routes announced by PE1 and PE2, introduces the EVPN prefix routes into VRF vpn1, and installs prefix route forwarding table entries to the FIB forwarding table. And searching the EVPN Service route forwarding table entry according to the Service ID 1 carried by the EVPN prefix route.
After the above-mentioned route information processing method corresponding to the first network-side edge device is introduced, the following detailed description is made for a route information processing method corresponding to the second network-side edge device:
referring to fig. 10, an implementation flowchart of a routing information processing method provided in the embodiment of the present application is shown, taking a target network-side edge device as a second network-side edge device as an example, and a specific implementation flow of the method is as follows:
s101: the method comprises the steps that a second network side edge device receives first service routing information which is sent by a first network side edge device and carries forwarding information;
the first service routing information is generated according to the service index when the VPN service represented by the service index is in an active state, the service index is configured for the first network-side edge device for a related session interface and is used for identifying the VPN service to which the public network connected to the client-side edge device belongs, the forwarding information is used for representing a routing forwarding path corresponding to the service index, and the session interface is an interface connected between the first network-side edge device and the client-side edge device.
Optionally, after receiving the first service routing information corresponding to the service index sent by the first network-side edge device, the second network-side edge device needs to import the first service routing information into the local routing table, and specifically, in the local routing table, the VPN service and the service index are used as key fields to establish a next hop table entry corresponding to the first service routing information.
The next hop list item comprises an inner layer label, an outer layer label, a next hop address and an outgoing interface; each next hop table entry is established based on the following method:
using the MPLS label distributed by the corresponding first network side edge device for the service index as an inner layer label in the next hop list item; and determining a next hop address, an outer layer label and an outgoing interface according to the next hop information.
Specifically, after receiving the first service routing information sent by the first network-side edge device, the second network-side edge device imports the first service routing information into the local VRF routing table according to the RT attribute carried by the service routing. In VRF, using VRF VPN and service index of service route as key field to build service route table, using BGP next hop as intermediate recursion next hop, and using service route as label in label stack. And then, iterating the IGP/LDP FTN route by using the BGP next hop to obtain a directly-connected next hop address, an outer layer label and an outgoing interface.
For example, the second network-side edge device receives a BGP update message carrying the EVPN Service route, which is advertised by the first network-side edge device, introduces the EVPN Service route to VRF VPN1, and installs a Service ID forwarding table entry to a FIB forwarding table, where the Service index is 1, the recursive next hop is 1.1.1, and the VPN label is 1000. And iterating the public network tunnel label according to the recursive next hop address 1.1.1.1, wherein the direct connection address is 10.1.1.2, the output interface is Gi0/1, and the tunnel label is 1001.
Specifically, when the second network-side edge device receives first service routing information sent by multiple first network-side edge devices, it needs to determine next hop information in the first service routing information sent by each first network-side edge device, that is, different next hop information sent by the multiple first network-side edge devices; and then, in the local routing table, using the VPN service and the service index as key fields, establishing a plurality of next hop table entries corresponding to the first service routing information, wherein different next hop table entries correspond to different next hop information in the first service routing information.
That is, when receiving the service routes of the same service index from multiple first network-side edge devices, the different next hop information in the service routes is used as a set of next hop entries of the service routes, and the generation process of each next hop entry is also as described above.
For example, still taking the network topology shown in fig. 3A as an example, two first network-side edge devices PE1 and PE2 respectively send Service routing information related to VRF vpn1 to a second network-side edge device PE3, where the Service ID is 1. At this time, PE3 needs to import the two pieces of first service routing information into the local routing table, and determine next hop information in each piece of first service routing information, where one BGP next hop is 1.1.1.1, and the other BGP next hop is 2.2.2.2, based on which, two next hop table entries shown in fig. 11 are established, where one BGP next hop is 1.1.1.1, the inner exit label is 100, which iterates to the direct-connection next hop address of 10.1.1.2, the outer exit label is 1000, and the exit interface is Gi 0/0; another BGP next hop is 2.2.2.2, the inner-layer outgoing label is 101, which iterates to the direct next hop address 20.1.1.2, the outer-layer outgoing label is 1001, the outgoing interface is Gi0/1, fig. 11 is a service routing forwarding table entry structure on the PE3 side in this embodiment, and this part of table entry is one level in the routing forwarding table entry on the PE3 side.
S102: the second network side edge device receives each prefix routing information which carries the service index and is sent by the first network side edge device;
the prefix routing information is generated by the first network-side edge device based on each public network connected with the client-side edge device, and different prefix routing information corresponds to different public networks.
For example, CE1 is connected to 255 × 255 public networks. The PE1 generates 255 × 255 prefix routing information based on the IP addresses of the public networks, where one IP address corresponds to one prefix routing information and is sent to the PE3, that is, the PE3 receives the 255 × 255 prefix routing information carrying the Service index Service ID 1 sent by the first network-side edge device PE 1.
S103: and the second network side edge device builds a related routing forwarding table entry in the local routing table based on the first service routing information and each prefix routing information.
Specifically, after receiving the prefix routing information sent by the first network-side edge device, the second network-side edge device imports the prefix routing information into the local VRF routing table according to the RT attribute carried by the prefix routing information, and searches for a corresponding service route in the local VRF routing table according to the carried service index, and associates the corresponding forwarding table entry.
For example, the PE3 receives a BGP update message carrying an EVPN prefix route advertised by the PE1 and PE2, introduces the EVPN prefix route into the VRF vpn1, and installs a prefix route forwarding table entry to the FIB forwarding table. And searching an EVPN Service route forwarding table entry according to the Service index 1 carried by the EVPN prefix route.
Specifically, according to the EVPN prefix route and the EVPN service route learned by the EVPN, forwarding entries are installed to the forwarding plane according to the two routes, and the corresponding forwarding entries are also configured according to the hierarchical structure, as shown in fig. 12, one of the forwarding entries is EVPN prefix routing information, the other is EVPN service routing information, and fig. 12 is simply introduced by taking prefix routing information corresponding to only 3 IP addresses as an example, and actually, a plurality of prefix routing information, that is, 100.1.1/32-100.1.1.3/32, is included, which is only referred to for illustration and is not limited specifically.
Accordingly, after the target network-side edge device receives the second service routing information and each prefix routing information sent by other network-side edge devices, the route forwarding table entry may also be constructed based on the similar method. Specifically, the target network side edge device imports the second service routing information into a routing table; determining different next hop information in second service routing information sent by each other network side edge device; in the routing table, taking the VPN service and the service index as key fields, establishing at least one next hop table item corresponding to the second service routing information, and further searching the corresponding second service routing information in the routing table according to the service index; and cascading the prefix routing information and the next hop forwarding table entry corresponding to the second service routing information to obtain a route forwarding table entry. Wherein, different next hop table entries correspond to different next hop information in the second service routing information.
For example, when PE1 is a target network-side edge device and PE2 is another network-side edge device, PE2 may send second service routing information to PE1, and PE1 may further construct a relevant routing forwarding entry based on the second service routing information.
It should be noted that, the process of the target network-side edge device establishing the relevant route forwarding table entry based on the second service route information and each prefix route information is similar to the process of the second network-side edge device establishing the relevant route forwarding table entry locally, and repeated parts are not described again.
Optionally, before step S101, similar to the first network-side edge device, the second network-side edge device side may also configure an enabling service routing function for itself and the EVPN neighbor; furthermore, a VPN service is configured for a VPN site of the client-side edge device, and protocol-related information is specified for the VPN service, so that communication between the first network-side edge device and the second network-side edge device can be performed based on the protocol-related information.
The forwarding table structure of the EVPN prefix routing cascade EVPN Service routing can meet the requirement that the prefix routing is fast converged along with the EVPN Service routing.
In an optional implementation manner, the second network-side edge device receives a first packet sent by the first network-side edge device and used for instructing to delete the service routing information, then deletes the service routing information in the local routing table according to the first packet, and retains each prefix routing information related to the service routing information.
Specifically, still using the PE1 as the first network-side edge device and the PE3 as the second network-side edge device, when the PE3 receives the first packet sent by the PE1, the PE3 deletes the service routing information in the local routing table according to the first packet, and stores each prefix routing information associated with the service routing information, so as to generate a new forwarding table entry, as shown in fig. 13.
Optionally, the second network-side edge device receives a second packet sent by the first network-side edge device and used for indicating deletion of each prefix routing information related to the service routing information, and deletes each prefix routing information in the local routing table according to the second packet, and service routing information sent by other first network-side edge devices except the first network-side edge device.
Specifically, after receiving the second packet sent by PE1, PE3 deletes each prefix routing information associated with the service routing information in the local routing table, and deletes the service routing information sent by the other first network-side edge device.
In the above embodiment, the second network-side edge device receives the first message or the second message sent by the first network-side edge device, and correspondingly deletes the service routing information in the local routing table or deletes all the service routing information and the prefix routing information, thereby improving the EVPN routing convergence performance under the conditions of link failure, protocol failure, or configuration change.
Correspondingly, the target network-side edge device receives a third packet sent by another network-side edge device and used for instructing to delete the second service routing information, and may also delete the second service routing information in the local routing table according to the third packet and retain each prefix routing information related to the second service routing information in the similar manner as described above.
Similarly, the target network side edge device receives a fourth message which is sent by other network side edge devices and used for indicating to delete each prefix routing information related to the second service routing information; in a similar manner as described above, according to the fourth packet, each prefix routing information and the second service routing information sent by the other network-side edge devices except the network-side edge device (i.e., the other network-side edge devices that send the second service routing information to the target network-side edge device) are deleted in the local routing table, and repeated parts are not described again
Referring to fig. 14, it is a schematic diagram of a route convergence process of a network-side edge device in the embodiment of the present application, and the specific implementation process is as follows:
step S1401: judging whether other paths (namely session links between the PEs and the CEs) exist in the EVPN Service route, if so, executing a step S1402, otherwise, executing a step S1403;
step S1402: updating the routing information of the EVPN Service route to a forwarding module;
step S1403: deleting all EVPN prefix routes associated with the EVPN Service routes;
step S1404: and deleting the EVPN Service route to the forwarding module.
Referring to fig. 15, it is a timing diagram illustrating an interaction procedure between network-side edge devices in an embodiment of the present application, where PE-a is a first network-side edge device and PE-B is a second network-side edge device, and the method specifically includes the following steps:
s1501: an EVPN neighbor enabling Service routing function is configured on the PE-A and the PE-B;
s1502: configuring VPN Service for the VPN site of the CE on the PE-A, and appointing a user side interface and a protocol for the VPN Service, and appointing a network side protocol type;
s1503: when a CE protocol neighbor bound by VPN Service on PE-A equipment is in an UP state (as long as one neighbor processes the UP state), the VPN Service is set to be in an activated state;
s1504: the PE-A equipment generates an EVPN Service route according to the activated VPN Service and announces the EVPN Service route to other PE equipment (PE-B) through EVPN neighbors;
s1505: after receiving the EVPN Service route announced by the PE-A, the PE-B equipment imports the EVPN Service route into a local VRF routing table according to the RT attribute carried by the EVPN Service route;
s1506: the PE-A equipment generates EVPN prefix routing information carrying Service ID from the learned route of the CE equipment, and announces the EVPN prefix routing information to other PE equipment (PE-B) through EVPN neighbors;
s1507: after receiving EVPN prefix routing information announced by PE-A, the PE-B equipment imports the EVPN prefix routing information into a local VRF routing table according to the RT attribute carried by the EVPN prefix routing information, searches a corresponding EVPN Service route in the local VRF according to the carried Service ID, and associates a corresponding forwarding table item.
In addition to the above-mentioned embodiments, the embodiments of the present application provide an association relationship between a VPN Service state and a CE side protocol session state, and when a CE side protocol session is disconnected due to a failure or configuration change, a remote PE can sense the VPN Service state, so as to switch traffic quickly and improve the routing convergence performance under the condition of the failure or configuration change.
The route convergence method in the embodiment of the present application is briefly described below with reference to a first network-side edge device and a second network-side edge device:
referring to fig. 16, which is a flowchart of a route convergence method provided in the present embodiment, applied to a first network-side edge device, specifically including the following steps:
s1601: the first network side edge device determines each session link established between the first network side edge device and the client side edge device;
s1602: if the first network side edge device determines that each session link is in a disconnected state, deleting first service routing information in a local routing table, and reserving prefix routing information related to the first service routing information, wherein the first service routing information is generated according to a service index and carries forwarding information, the forwarding information is used for representing a routing forwarding path corresponding to the service index, and the service index is configured for a session interface connected with the client side edge device and is used for identifying VPN services to which a public network connected with the client side edge device belongs; and the number of the first and second groups,
s1603: the first network side edge device sends a first message used for indicating deletion of first service routing information to a second network side edge device, so that the second network side edge device deletes the first service routing information in a local routing table of the second network side edge device according to the first message, wherein prefix routing information is routing information which is generated based on each public network connected by the client side edge device and carries service indexes, and different prefix routing information corresponds to different public networks.
Optionally, if the first network-side edge device determines that all session links between the first network-side edge device and the client-side edge device except the first network-side edge device are in a disconnected state, deleting each prefix routing information; and sending a second message for indicating deletion of each prefix routing information to the second network-side edge device, so that the second network-side edge device deletes each prefix routing information and the first service routing information sent by other first network-side edge devices except the first network-side edge device in the local routing table of the second network-side edge device according to the second message.
Referring to fig. 17, which is a flowchart of a route convergence method provided in the present embodiment, applied to a second network-side edge device, specifically including the following steps:
s1701: a second network side edge device receives a first message which is sent by a first network side edge device and used for indicating deletion of second service routing information, wherein the first message is sent after the first network side edge device determines that all session links between the first network side edge device and a client side edge device are in a disconnected state, the second service routing information is routing information which is generated and sent by the first network side edge device according to a service index and carries forwarding information, the forwarding information is used for representing a routing forwarding path corresponding to the service index, and the service index is configured for a session interface connected with the client side edge device and is used for identifying VPN services to which a public network connected with the client side edge device belongs;
s1702: and the second network side edge device deletes the second service routing information in the local routing table according to the first message and reserves each prefix routing information related to the second service routing information, wherein the prefix routing information is routing information which is generated and sent by the first network side edge device based on each public network connected with the client side edge device and carries a service index, and different prefix routing information corresponds to different public networks.
Optionally, the second network-side edge device receives a second packet sent by the first network-side edge device and used for instructing to delete each piece of prefix routing information related to the second service routing information, where the second packet is sent when all session links between each first network-side edge device and the client-side edge device are in a disconnected state; and deleting each prefix routing information and second service routing information sent by other first network side edge equipment except the first network side edge equipment in the local routing table according to the second message.
In this embodiment of the present application, if it is determined that each session link established between the first network-side edge device and the client-side edge device is in a disconnected state, the first network-side edge device only needs to delete service routing information associated with the first network-side edge device in the local routing table, and send a first message for indicating deletion of the service routing information to the second network-side edge device, so that the second network-side edge device deletes the service routing information in the local routing table of the second network-side edge device according to the first message, and does not need to delete other service routing information or prefix routing information, thereby improving the EVPN routing convergence performance under the conditions of link failure, protocol failure, or configuration change.
Based on the same inventive concept, the embodiment of the application also provides a routing information processing device. As shown in fig. 18, which is a schematic structural diagram of a routing information processing apparatus 1800 in the embodiment of the present application, a target network-side edge device applied in EVPN may include:
a first configuration unit 1801, configured to configure a service index for a relevant session interface, where the session interface is an interface where a first network-side edge device is connected to a client-side edge device, and the service index is used to identify a VPN service to which a public network connected to the client-side edge device belongs; (ii) a
A first sending unit 1802, configured to generate, according to the service index, first service routing information carrying forwarding information if the VPN service is in an active state, and send the first service routing information to a second network-side edge device, where the forwarding information is used to represent a route forwarding path corresponding to the service index;
a second sending unit 1803, configured to generate prefix routing information carrying service indexes based on public networks connected to the client-side edge device, and send the prefix routing information to the second network-side edge device, so that the second network-side edge device constructs a relevant routing forwarding table entry in a local routing table based on the first service routing information and the prefix routing information, where different prefix routing information corresponds to different public networks.
Optionally, after configuring the service index for the relevant session interface, and before generating the first service routing information carrying the forwarding information according to the service index, the apparatus further includes a first determining unit 1804, configured to:
determining each session link established between the client-side edge device and the client-side edge device;
setting the VPN service to an active state if at least one session link is active.
Optionally, the first configuration unit 1801 may be configured to perform at least one of the following operations:
if a plurality of session links exist between the client side edge device and the client side edge device, configuring the same service index for each session interface corresponding to each session link;
if the client-side edge device is connected with at least one other first network-side edge device except the self, configuring the same service index for the session interfaces corresponding to the self and the at least one other first network-side edge device.
Optionally, the first sending unit 1802 is specifically configured to:
allocating an MPLS label for the service index;
first service routing information is generated based on the MPLS label.
Optionally, the NLRI of the first service routing information includes: a routing specifier, an Ethernet segment identifier, an Ethernet label index, a service index, a default gateway address, and an MPLS label;
the NLRI of the prefix routing information includes: routing specifier, Ethernet tag index, IP prefix length, IP prefix address.
Optionally, the second sending unit 1803 is specifically configured to:
the prefix routing information carries a service index based on a preset service index extended group attribute; wherein the service index extended community attribute comprises at least four fields: two type value fields for indicating the extended community attribute type value, a reserved field, and an index field for indicating the service index.
Optionally, the apparatus further comprises:
a first processing unit 1805, configured to configure an enabling service routing function for itself and an EVPN neighbor before the first configuration unit 1801 configures a service index for a relevant session interface;
the method includes configuring a VPN service for a VPN site of a customer-side edge device and specifying protocol-related information for the VPN service such that communication between a first network-side edge device and a second network-side edge device, between the first network-side edge device and the customer-side edge device, is possible based on the protocol-related information.
Optionally, the apparatus further comprises:
a first receiving unit 1806, configured to receive second service routing information that is sent by a first network-side edge device and carries forwarding information, where the second service routing information is generated according to a service index when a VPN service indicated by the service index is in an active state, the service index is configured for a relevant session interface for the first network-side edge device, and is used to identify a VPN service to which a public network connected to a client-side edge device belongs, the forwarding information is used to characterize a route forwarding path corresponding to the service index, and the session interface is an interface between the first network-side edge device and the client-side edge device;
a second receiving unit 1807, configured to receive prefix routing information, which is sent by a first network-side edge device and carries a service index, where the prefix routing information is generated by the first network-side edge device based on each public network connected to a client-side edge device, and different prefix routing information corresponds to different public networks;
a constructing unit 1808, configured to construct, based on the second service routing information and each prefix routing information, a relevant routing forwarding entry in the local routing table.
Optionally, the apparatus further includes a importing unit 1809, configured to:
if second service routing information corresponding to the service indexes sent by the multiple first network-side edge devices is received, before receiving prefix routing information carrying the service indexes sent by the first network-side edge devices, the method further includes:
importing the second service routing information into a routing table;
and determining different next hop information in the second service routing information sent by each first network side edge device.
Optionally, the next hop table entry includes an inner layer tag, an outer layer tag, a next hop address, and an outgoing interface; each next hop table entry is established based on the following method:
using the MPLS label distributed by the corresponding first network side edge device for the service index as an inner layer label in the next hop list item; and
and determining a next hop address, an outer layer label and an outgoing interface according to the next hop information.
Optionally, the constructing unit 1808 is specifically configured to:
searching corresponding second service routing information in the routing table according to the service index;
and cascading the prefix routing information and the next hop forwarding table entry corresponding to the second service routing information to obtain a route forwarding table entry.
Optionally, the apparatus further comprises:
a second configuring unit 1810, configured to configure, before the first receiving unit 1806 receives the second service routing information sent by the first network-side edge device, a second service routing function for itself and the EVPN neighbor;
the method includes configuring a VPN service for a VPN site of a customer-side edge device and specifying protocol-related information for the VPN service so that communication between a first network-side edge device and a second network-side edge device is possible based on the protocol-related information.
Optionally, the apparatus further comprises:
a second determining unit 1811, configured to determine each session link established between itself and the client-side edge device;
a first deleting unit 1812, configured to delete, if it is determined that each session link is in a disconnected state, first service routing information in a local routing table, and keep each prefix routing information related to the first service routing information, where the first service routing information is routing information that is generated according to a service index and carries forwarding information, the forwarding information is used to represent a route forwarding path corresponding to the service index, and the service index is configured for a session interface connected to a client-side edge device and is used to identify a VPN service to which a public network connected to the client-side edge device belongs;
a third sending unit 1813, configured to send a first packet for instructing to delete the first service routing information to the second network-side edge device, so that the second network-side edge device deletes the first service routing information in the local routing table of the second network-side edge device according to the first packet, where the prefix routing information is routing information that carries a service index and is generated based on each public network connected to the client-side edge device, and different prefix routing information corresponds to different public networks.
Optionally, the apparatus further comprises a second processing unit 1814, configured to:
if all session links between the first network side edge device and the client side edge device except the first network side edge device are determined to be in a disconnected state, deleting each prefix routing information;
and sending a second message for indicating deletion of each prefix routing information to the second network-side edge device, so that the second network-side edge device deletes each prefix routing information and the first service routing information sent by other first network-side edge devices except the first network-side edge device in the local routing table of the second network-side edge device according to the second message.
Optionally, the apparatus further comprises:
a third receiving unit 1815, configured to receive a first packet sent by a first network-side edge device and used to instruct to delete second service routing information, where the first packet is sent after the first network-side edge device determines that all session links between the first network-side edge device and a client-side edge device are in a disconnected state, the second service routing information is routing information that is generated and sent by the first network-side edge device according to a service index and carries forwarding information, the forwarding information is used to represent a routing forwarding path corresponding to the service index, and the service index is configured for a session interface connected to the client-side edge device and is used to identify a VPN service to which a public network connected to the client-side edge device belongs;
a second deleting unit 1816, configured to delete the second service routing information in the local routing table according to the first packet, and reserve prefix routing information related to the second service routing information, where the prefix routing information is routing information that is generated and sent by the first network-side edge device based on each public network connected to the client-side edge device and carries a service index, and different prefix routing information corresponds to different public networks.
Optionally, the apparatus further comprises a third processing unit 1817, configured to:
receiving a second message sent by the first network-side edge device and used for indicating to delete each prefix routing information related to the second service routing information, wherein the second message is sent when all session links between each first network-side edge device and the client-side edge device are in a disconnected state;
and deleting each prefix routing information and second service routing information sent by other first network side edge equipment except the first network side edge equipment in the local routing table according to the second message.
For convenience of description, the above parts are separately described as modules (or units) according to functional division. Of course, the functionality of the various modules (or units) may be implemented in the same one or more pieces of software or hardware when implementing the present application.
As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method or program product. Accordingly, various aspects of the present application may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
The electronic equipment is based on the same inventive concept as the method embodiment, and the embodiment of the application also provides the electronic equipment. In one embodiment, the electronic device may be a first network-side edge device or a second network-side edge device. In this embodiment, the structure of the electronic device may be as shown in fig. 19, including a processor 1901, and a memory 1902.
The processor 1901 may include one or more Central Processing Units (CPUs), a digital processing unit, and the like. The processor 1901 is configured to implement the signal transmission control method when calling a computer program stored in the memory 1902.
A memory 1902 for storing a computer program for execution by the processor 1901. The memory 1902 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, a program required for running an instant messaging function, and the like; the storage data area can store various instant messaging information, operation instruction sets and the like.
The memory 1902 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 1902 may also be a non-volatile memory (non-volatile memory), such as a read-only memory (rom), a flash memory (flash memory), a hard disk (HDD) or a solid-state drive (SSD); or memory 1902 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. Memory 1902 may be a combination of the above.
The specific connection medium between the processor 1901 and the memory 1902 is not limited in this embodiment. In the embodiment of the present application, the processor 1901 and the memory 1902 are connected by a bus in fig. 19, the bus is depicted by a thick line in fig. 19, and the connection manner between other components is only for illustrative purposes and is not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of description, only one thick line is depicted in fig. 19, but only one bus or one type of bus is not depicted.
The memory 1902 stores a computer storage medium having stored therein computer-executable instructions for implementing the routing information processing method of the embodiments of the present application. The processor 1901 is configured to execute one of the routing information processing methods described above, such as the method shown in fig. 2.
In some possible embodiments, various aspects of the routing information processing method provided by the present application may also be implemented in the form of a program product including program code for causing a computer device to perform the steps in the routing information processing method according to various exemplary embodiments of the present application described above in this specification when the program product is run on the computer device, for example, the computer device may perform the steps as shown in fig. 2.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The program product of embodiments of the present application may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a computing device. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with a command execution system, apparatus, or device.
A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with a command execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user computing device, partly on the user equipment, as a stand-alone software package, partly on the user computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such division is merely exemplary and not mandatory. Indeed, the features and functions of two or more units described above may be embodied in one unit, according to embodiments of the application. Conversely, the features and functions of one unit described above may be further divided into embodiments by a plurality of units.
Further, while the operations of the methods of the present application are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (18)

1. A method for processing routing information, the method comprising:
configuring a service index for a session interface, wherein the session interface is an interface of a target network side edge device and a client side edge device, and the service index is used for identifying Virtual Private Network (VPN) service to which a public network connected with the client side edge device belongs;
if the VPN service is in an activated state, generating first service routing information carrying forwarding information according to the service index, and sending the first service routing information to other network side edge devices, wherein the forwarding information is used for representing a routing forwarding path corresponding to the service index;
generating prefix routing information carrying the service index based on each public network connected by the client-side edge device, and sending the prefix routing information to the other network-side edge device, so that the other network-side edge device constructs a related routing forwarding table entry in a local routing table based on the first service routing information and the prefix routing information, wherein different prefix routing information corresponds to different public networks.
2. The method of claim 1, wherein after configuring the service index for the session interface and before generating the first service routing information carrying forwarding information according to the service index, further comprising:
determining respective session links established between the target network-side edge device and the client-side edge device;
and if at least one session link is in an active state, setting the VPN service to be in an active state.
3. The method of claim 1, wherein configuring the service index for the session interface comprises at least one of:
if a plurality of session links exist between the target network side edge device and the client side edge device, configuring the same service index for each session interface corresponding to each session link;
if the client-side edge device is connected to at least one other target network-side edge device except the target network-side edge device, configuring the same service index for the session interfaces corresponding to the target network-side edge device and the at least one other network-side edge device.
4. The method of claim 1, wherein the generating first service routing information carrying forwarding information according to the service index comprises:
distributing a multiprotocol label switching (MPLS) label for the service index;
generating the first service routing information based on the MPLS label.
5. The method of claim 1, wherein the network layer reachability information NLRI of the first service routing information comprises: a routing specifier, an ethernet segment identifier, an ethernet label index, a service index, a default gateway address, and an MPLS label;
the NLRI of the prefix routing information includes: a routing specifier, an ethernet tag index, a protocol IP prefix length and an IP prefix address of the interconnect between the networks.
6. The method of claim 1, wherein the prefix routing information carries the service index based on a preset service index extended community attribute; wherein the service index extended community attribute comprises at least four fields: two type value fields for indicating an extended community attribute type value, a reserved field, and an index field for indicating the service index.
7. The method of any of claims 1 to 6, further comprising, prior to the configuring a service index for a session interface:
configuring an enabling first service routing function for the target network side edge device and the EVPN neighbor;
and configuring the VPN service for the VPN site of the client-side edge device, and specifying protocol related information for the VPN service, so that the target network-side edge device and the other network-side edge devices can communicate based on the protocol related information.
8. The method of claim 1, wherein the method further comprises:
receiving second service routing information which is sent by the other network side edge devices and carries forwarding information;
receiving each prefix routing information which is sent by the other network side edge devices and carries the service index;
and constructing a related routing forwarding table entry in a local routing table based on the second service routing information and the prefix routing information.
9. The method according to claim 8, wherein if second service routing information corresponding to the service index sent by a plurality of other network-side edge devices is received, before receiving prefix routing information carrying the service index sent by the other network-side edge devices, the method further includes:
importing the second service routing information into the routing table;
determining different next hop information in the second service routing information sent by each other network side edge device;
and in the routing table, establishing at least one next hop table entry corresponding to the second service routing information by taking the VPN service and the service index as key fields, wherein different next hop table entries correspond to different next hop information in the second service routing information.
10. The method of claim 9, wherein the next hop table entry comprises an inner label, an outer label, a next hop address, and an egress interface; each next hop table entry is established based on the following method:
using the MPLS label distributed by the corresponding other network side edge device for the service index as the inner layer label in the next hop list item; and
and determining the next hop address, the outer layer label and the outgoing interface according to the next hop information.
11. The method of claim 9, wherein the constructing the associated route forwarding entry in the routing table based on the second service routing information and the respective prefix routing information comprises:
searching corresponding second service routing information in the routing table according to the service index;
and cascading the prefix routing information and a next hop forwarding table entry corresponding to the second service routing information to obtain the route forwarding table entry.
12. The method of claim 1, wherein the method further comprises:
determining respective session links established between the target network-side edge device and the client-side edge device;
if the session links are determined to be in a disconnected state, deleting the first service routing information in a local routing table, and reserving prefix routing information of the service routing information; and the number of the first and second groups,
and sending a first message for indicating to delete the first service routing information to the other network-side edge device, so that the other network-side edge device deletes the service routing information in the local routing table of the other network-side edge device according to the first message.
13. The method of claim 12, wherein the method further comprises:
if all session links between the other target network side edge devices except the target network side edge device and the client side edge device are determined to be in a disconnected state, deleting each prefix routing information;
and sending a second message for indicating deletion of each prefix routing information to the other network-side edge device, so that the other network-side edge device deletes each prefix routing information and first service routing information sent by other target network-side edge devices except the target network-side edge device in the local routing table of the other network-side edge device according to the second message.
14. The method of claim 8, wherein the method further comprises:
receiving a third message which is sent by the other network side edge device and used for indicating to delete the second service routing information;
and deleting the second service routing information in a local routing table according to the third message, and reserving each prefix routing information related to the second service routing information.
15. The method of claim 14, wherein the method further comprises:
receiving a fourth message sent by the other network-side edge device and used for indicating deletion of each prefix routing information related to the second service routing information;
and deleting the prefix routing information and second service routing information sent by the network side edge equipment except the other network side edge equipment in a local routing table according to the fourth message.
16. A routing information processing apparatus applied to a target network-side edge device in EVPN, the apparatus comprising:
a configuration unit, configured to configure a service index for a session interface, where the session interface is an interface between the target network-side edge device and a client-side edge device, and the service index is used to identify a VPN service to which a public network connected to the client-side edge device belongs;
a first sending unit, configured to generate, according to the service index, first service routing information carrying forwarding information if the VPN service is in an activated state, and send the first service routing information to other network-side edge devices, where the forwarding information is used to represent a route forwarding path corresponding to the service index;
a second sending unit, configured to generate, based on each public network connected to the client-side edge device, each prefix routing information carrying the service index, and send each prefix routing information to the other network-side edge device, so that the other network-side edge device constructs a routing forwarding table entry in a local routing table based on the first service routing information and each prefix routing information, where different prefix routing information corresponds to different public networks.
17. An electronic device, comprising a processor and a memory, wherein the memory stores program code which, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1 to 15.
18. A computer-readable storage medium, characterized in that it comprises program code for causing an electronic device to carry out the steps of the method according to any one of claims 1 to 15, when said storage medium is run on said electronic device.
CN202111082501.5A 2021-09-15 2021-09-15 Routing information processing method and device, electronic equipment and storage medium Active CN113904981B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111082501.5A CN113904981B (en) 2021-09-15 2021-09-15 Routing information processing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111082501.5A CN113904981B (en) 2021-09-15 2021-09-15 Routing information processing method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113904981A true CN113904981A (en) 2022-01-07
CN113904981B CN113904981B (en) 2023-11-17

Family

ID=79028380

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111082501.5A Active CN113904981B (en) 2021-09-15 2021-09-15 Routing information processing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113904981B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115277535A (en) * 2022-09-30 2022-11-01 紫光恒越技术有限公司 VPN routing processing method and device, electronic equipment and readable storage medium
CN115396365A (en) * 2022-10-26 2022-11-25 中国人民解放军军事科学院系统工程研究院 Scale-independent fast route convergence method

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006105718A1 (en) * 2005-04-04 2006-10-12 Huawei Technologies Co., Ltd. A method for realizing the mpls-vpn across the hybrid network
CN107222449A (en) * 2016-03-21 2017-09-29 华为技术有限公司 Communication means, equipment and system based on the regular agreement of stream
CN107925613A (en) * 2016-07-01 2018-04-17 华为技术有限公司 It is used for the methods, devices and systems to E-Packet in business function chain SFC
CN108989212A (en) * 2017-05-31 2018-12-11 瞻博网络公司 The Routing Protocol signaling and its relationship of multiple next-hops
CN108989203A (en) * 2017-05-31 2018-12-11 瞻博网络公司 Selected structural path of the notice for the service routing in dummy node
CN110557317A (en) * 2018-06-01 2019-12-10 华为技术有限公司 Method and apparatus for managing virtual private network
CN112559166A (en) * 2019-09-25 2021-03-26 瞻博网络公司 Apparatus, system and method for determining traffic load distribution associated with routing of hierarchical forwarding information bases
WO2021135624A1 (en) * 2019-12-31 2021-07-08 中兴通讯股份有限公司 Virtual circuit-based data packet processing method and forwarding table entry construction method

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006105718A1 (en) * 2005-04-04 2006-10-12 Huawei Technologies Co., Ltd. A method for realizing the mpls-vpn across the hybrid network
CN107222449A (en) * 2016-03-21 2017-09-29 华为技术有限公司 Communication means, equipment and system based on the regular agreement of stream
CN107925613A (en) * 2016-07-01 2018-04-17 华为技术有限公司 It is used for the methods, devices and systems to E-Packet in business function chain SFC
CN111884934A (en) * 2016-07-01 2020-11-03 华为技术有限公司 Method, device and system for forwarding message in Service Function Chain (SFC)
CN108989212A (en) * 2017-05-31 2018-12-11 瞻博网络公司 The Routing Protocol signaling and its relationship of multiple next-hops
CN108989203A (en) * 2017-05-31 2018-12-11 瞻博网络公司 Selected structural path of the notice for the service routing in dummy node
CN110557317A (en) * 2018-06-01 2019-12-10 华为技术有限公司 Method and apparatus for managing virtual private network
CN112559166A (en) * 2019-09-25 2021-03-26 瞻博网络公司 Apparatus, system and method for determining traffic load distribution associated with routing of hierarchical forwarding information bases
WO2021135624A1 (en) * 2019-12-31 2021-07-08 中兴通讯股份有限公司 Virtual circuit-based data packet processing method and forwarding table entry construction method

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115277535A (en) * 2022-09-30 2022-11-01 紫光恒越技术有限公司 VPN routing processing method and device, electronic equipment and readable storage medium
CN115277535B (en) * 2022-09-30 2022-12-16 紫光恒越技术有限公司 VPN routing processing method and device, electronic equipment and readable storage medium
CN115396365A (en) * 2022-10-26 2022-11-25 中国人民解放军军事科学院系统工程研究院 Scale-independent fast route convergence method
CN115396365B (en) * 2022-10-26 2023-04-07 中国人民解放军军事科学院系统工程研究院 Scale-independent fast route convergence method

Also Published As

Publication number Publication date
CN113904981B (en) 2023-11-17

Similar Documents

Publication Publication Date Title
US10757008B2 (en) Flow specification protocol-based communications method, device, and system
WO2020156105A1 (en) Data forwarding method and related device
CN111865796B (en) Path Computation Element Central Controller (PCECC) for network traffic
CN108574630B (en) EVPN message processing method, device and system
CN108574639B (en) EVPN message processing method, device and system
US10484203B2 (en) Method for implementing communication between NVO3 network and MPLS network, and apparatus
US8665887B2 (en) Number automatic routing method, updating method, withdrawing method, router and device
CN111786884B (en) Routing method and routing equipment
WO2018032961A1 (en) Information management method, apparatus and system
CN110050445B (en) Method, device and system for sending and receiving message
WO2018032962A1 (en) Method, device and system for information synchronization
CN112511444A (en) Multicast traffic transmission method, device, communication node and storage medium
CN110417655B (en) Method and device for forwarding data message
CN106850380B (en) Method and system for realizing three-layer virtual special network of multi-protocol label switching
US11362954B2 (en) Tunneling inter-domain stateless internet protocol multicast packets
CN113037527B (en) Network slice creation method, message forwarding method and device thereof
CN113904981B (en) Routing information processing method and device, electronic equipment and storage medium
CN113037883B (en) Method and device for updating MAC address table entries
WO2021052381A1 (en) Message sending method and apparatus
CN112910771B (en) Connection establishment method, device, equipment and storage medium
JP2024027107A (en) Communication methods and related equipment
WO2024036149A1 (en) Automated scaling of network topologies using unique identifiers
CN117278501A (en) Message forwarding method, communication device and system
CN115550252A (en) Method, device, equipment and storage medium for routing publishing and forwarding message

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant