CN113992558B - Method, device, electronic equipment and medium for route publishing - Google Patents

Method, device, electronic equipment and medium for route publishing Download PDF

Info

Publication number
CN113992558B
CN113992558B CN202111249989.6A CN202111249989A CN113992558B CN 113992558 B CN113992558 B CN 113992558B CN 202111249989 A CN202111249989 A CN 202111249989A CN 113992558 B CN113992558 B CN 113992558B
Authority
CN
China
Prior art keywords
domain
locator
sid
route
intra
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.)
Active
Application number
CN202111249989.6A
Other languages
Chinese (zh)
Other versions
CN113992558A (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.)
New H3C Security Technologies Co Ltd
Original Assignee
New H3C Security Technologies 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 New H3C Security Technologies Co Ltd filed Critical New H3C Security Technologies Co Ltd
Priority to CN202111249989.6A priority Critical patent/CN113992558B/en
Publication of CN113992558A publication Critical patent/CN113992558A/en
Application granted granted Critical
Publication of CN113992558B publication Critical patent/CN113992558B/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/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • 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/34—Source routing
    • 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]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application discloses a method, a device, electronic equipment and a medium for route publishing. In the application, when receiving an intra-domain route sending instruction, the first intra-domain Locator may be carried when sending a route to the second PE device, where the intra-domain Locator includes a first SID for implementing intra-domain data forwarding; and when receiving a cross-domain route sending instruction, carrying a first out-of-domain Locator when sending a route to the out-of-domain node equipment, wherein the out-of-domain Locator comprises a second SID for realizing out-of-domain data forwarding. By applying the technical scheme of the application, the Locator containing different SIDs can be allocated to each PE device in an SRv6VPN networking scene, so that the PE device can select the corresponding Locator to perform routing publishing according to whether the publishing object is in the same data domain or not. Therefore, in the multi-homing networking, the remote PE and the home PE can form equivalent load sharing, and the network reliability is improved.

Description

Method, device, electronic equipment and medium for route publishing
Technical Field
The present application relates to data communication technologies, and in particular, to a method, an apparatus, an electronic device, and a medium for route distribution.
Background
SRv6 is a network forwarding technology, in which SRv6 SID (Segment Identifier) is in IPv6 address form, and SRv6 SID is composed of two parts, namely, locator and Function, and the format is Locator: function, in which Locator occupies the high bits of IPv6 address, and Function occupies the rest of IPv6 address.
Furthermore, the Locator has a positioning function, and after the node configures the Locator, the system generates a Locator network segment route and diffuses in the SR domain through IGP. Other nodes in the network can be positioned to the node through the Locator network segment route, and simultaneously, all SRv6 SIDs configured by the node can also reach through the Locator network segment route.
However, in the current SRv6VPN networking scenario, a node device can only associate with one Locator, and each Locator only allocates one SID to each VPN, so that both the intra-domain node device routing and the cross-domain node device routing can only carry the same SID, that is, only routes of the same link can be used. This may result in a route that is more stressed.
Disclosure of Invention
The embodiment of the application provides a method, a device, electronic equipment and a medium for route distribution, and is used for solving the problem that route distribution cannot be performed in a multi-domain scene due to the fact that only one same SID can be carried when routes are sent between node equipment in an SRv6VPN networking scene in the related technology.
According to an aspect of the embodiments of the present application, a method for routing and publishing is provided, where the method is applied to a first PE device in an SRv6VPN networking scenario, where the first PE device is configured with a first intra-domain Locator and a first out-of-domain Locator, and the method includes:
when receiving an intra-domain route sending instruction, carrying the first intra-domain Locator when sending a route to second PE equipment, wherein the intra-domain Locator comprises a first SID for realizing intra-domain data forwarding;
and when receiving a cross-domain route sending instruction, carrying the first out-of-domain Locator when sending a route to out-of-domain node equipment, wherein the out-of-domain Locator contains a second SID for realizing out-of-domain data forwarding.
Optionally, in another embodiment of the present application, before determining that the intra-domain routing transmission instruction is received, the method further includes:
receiving a first configuration instruction, where the first configuration instruction is used to configure the first intra-domain Locator and the first out-of-domain Locator for the first PE device;
configuring a first SID under a target VPN on the first intra-domain Locator, and generating an intra-domain Local SID table according to the first SID; and the number of the first and second groups,
and configuring a second SID under multiple VPNs on the first out-of-domain Locator, and generating an out-of-domain Local SID table according to the second SID.
Optionally, in another embodiment of the present application, after generating the out-of-domain Local SID table, the method further includes:
receiving an association instruction, wherein the association instruction is used for associating the first out-of-domain Locator with the out-of-domain node device;
sending the second SID to the out-of-domain node device; receiving the SID of the out-of-domain node sent by the out-of-domain node equipment;
and when the cross-domain route sending instruction is received, sending a route to the outside-domain node equipment according to the outside-domain node SID.
Optionally, in another embodiment of the present application, the out-of-domain Locator is an anycast Locator, and the in-domain Locator is a unicast Locator.
According to an aspect of the embodiments of the present application, a method for routing is provided, where the method is applied to a second PE device in an SRv6VPN networking scenario, and a second intra-domain Locator and a second out-of-domain Locator are configured on the first PE device, including:
when receiving an intra-domain route sending instruction, receiving a route and a first intra-domain Locator sent by first PE equipment;
and when receiving a cross-domain route sending instruction, carrying the second out-of-domain Locator when sending a route to out-of-domain node equipment, wherein the out-of-domain Locator contains a second SID for realizing out-of-domain data forwarding.
Optionally, in another embodiment of the present application, after receiving the routing information and the location in the first domain sent by the first PE device, the method further includes:
extracting a first SID carried by a Locator in the first domain;
and establishing a corresponding relation between the first SID information and the route and then adding the first SID information and the route into a local routing table.
Optionally, in another embodiment of the present application, before receiving the intra-domain routing transmission instruction, the method further includes:
receiving a second configuration instruction, where the second configuration instruction is used to configure the second intra-domain Locator and the second out-of-domain Locator for the second PE device;
configuring a third SID of the target VPN domain on the second intra-domain Locator, and generating an intra-domain Local SID table according to the third SID; and the number of the first and second groups,
and configuring a fourth SID of the multiple VPN domains on the first out-of-domain Locator, and generating an out-of-domain Local SID table according to the fourth SID.
According to an aspect of the embodiments of the present application, an apparatus for route publishing is applied to a first PE device in an SRv6VPN networking scenario, where the first PE device is configured with a first intra-domain Locator and a first out-of-domain Locator, and the apparatus includes:
the first receiving module is configured to carry the first intra-domain Locator when a route is sent to the second PE device when receiving an intra-domain route sending instruction, where the intra-domain Locator includes a first SID for implementing intra-domain data forwarding;
the first sending module is configured to carry the first out-of-domain Locator when sending a route to an out-of-domain node device when receiving a cross-domain route sending instruction, where the out-of-domain Locator includes a second SID for implementing out-of-domain data forwarding.
According to an aspect of the embodiments of the present application, an apparatus for routing a publication is applied to a second PE device in an SRv6VPN networking scenario, where the first PE device is configured with a Locator in a second domain and a Locator outside the second domain, and the apparatus includes:
the second receiving module is configured to receive the route and the first intra-domain Locator sent by the first PE device when receiving the intra-domain route sending instruction;
and the second sending module is configured to carry a second out-of-domain Locator when sending a route to an out-of-domain node device when receiving a cross-domain route sending instruction, wherein the out-of-domain Locator contains a second SID for realizing out-of-domain data forwarding.
According to another aspect of the embodiments of the present application, there is provided an electronic device including:
a memory for storing executable instructions; and
a display for displaying with the memory to execute the executable instructions to perform the operations of any of the above-described methods of routing issues.
According to yet another aspect of the embodiments of the present application, a computer-readable storage medium is provided for storing computer-readable instructions, which when executed perform the operations of any of the above-mentioned route distribution methods.
In the application, when receiving an intra-domain route sending instruction, the first intra-domain Locator may be carried when sending a route to the second PE device, where the intra-domain Locator includes a first SID for implementing intra-domain data forwarding; and when receiving a cross-domain route sending instruction, carrying a first out-of-domain Locator when sending a route to the out-of-domain node equipment, wherein the out-of-domain Locator comprises a second SID for realizing out-of-domain data forwarding. By applying the technical scheme of the application, the Locator containing different SIDs can be allocated to each PE device in an SRv6VPN networking scene, so that the PE device can select the corresponding Locator to perform routing publishing according to whether the publishing object is in the same data domain or not. Therefore, in the multi-homing networking, the remote PE and the home PE can form equivalent load sharing, and the network reliability is improved.
The technical solution of the present application is further described in detail by the accompanying drawings and examples.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description, serve to explain the principles of the application.
The present application may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:
fig. 1 is a schematic diagram of a method for route distribution according to the present application;
fig. 2 is a schematic diagram of an SRV6 networking architecture proposed in the present application;
fig. 3 is a schematic diagram of a DT4 SID under SRV6 networking proposed in the present application;
fig. 4 is a schematic diagram of a DT6 SID under SRV6 networking proposed in the present application;
fig. 5 is a schematic flow chart of a system for routing distribution according to the present application;
fig. 6 is a schematic structural diagram of an electronic device for routing distribution proposed in the present application;
fig. 7 is a schematic structural diagram of an electronic device for routing distribution according to the present application.
Detailed Description
Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present application unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the application, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
In addition, technical solutions between the various embodiments of the present application may be combined with each other, but it must be based on the realization of the technical solutions by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination of technical solutions should be considered to be absent and not within the protection scope of the present application.
It should be noted that all directional indicators (such as up, down, left, right, front, back, ...) in the embodiments of the present application are only used to explain the relative positional relationship between the components, the motion situation, etc. in a specific posture (as shown in the drawings), and if the specific posture is changed, the directional indicator is changed accordingly.
A method for performing route publication according to an exemplary embodiment of the present application is described below in conjunction with fig. 1-5. It should be noted that the following application scenarios are merely illustrated for the convenience of understanding the spirit and principles of the present application, and the embodiments of the present application are not limited in this respect. Rather, embodiments of the present application may be applied to any scenario where applicable.
Further, the application also provides a method, a device, an electronic device and a medium for route publishing.
Fig. 1 schematically shows a flowchart of a method for route distribution according to an embodiment of the present application. As shown in fig. 1, the method is applied to a first PE device in an SRv6VPN networking scenario, where the first PE device is configured with a first intra-domain Locator and a first out-of-domain Locator, and includes:
s101, when receiving an intra-domain route sending instruction, sending a route to a second PE device, wherein the route carries a first intra-domain Locator, and the intra-domain Locator comprises a first SID for realizing intra-domain data forwarding.
In the related art, SRv6 Segment is in the form of IPv6 address, and may also be referred to as SRv6 SID (Segment Identifier), for a total of 128 bits. The SRv6 SID is composed of a Locator and a Function, and the format is Locator: function, wherein the Locator occupies the high bit of the IPv6 address, and the Function occupies the rest part of the IPv6 address.
Among them, the Locator has a positioning function, so it is generally unique in SR domain, but in some special scenarios, such as the Anycast protection scenario, multiple devices may configure the same Locator. After the node configures the Locator, the system generates a Locator network segment route and diffuses in the SR domain through IGP. Other nodes in the network can be positioned to the node through the Locator network segment route, and all SRv6 SIDs issued by the node can also reach through the Locator network segment route.
The Function represents instructions (Instruction) of the device, which are preset by the device, and the Function part is used for instructing a generation node of the SRv6 SID to perform corresponding Function operation.
In addition, the Function part can also be divided into an optional parameter section (extensions), at this time, the format of the SRv6 SID is changed into a Locator, the Function: extensions occupies the low bit of the IPv6 address, and information such as the flow and service of some messages can be defined through the extensions field. The current important application is the CE multi-homing scene of the EVPN VPLS, and when BUM flow is forwarded, horizontal segmentation is realized by utilizing arrows.
Further, there are many types of SRv6 SIDs, and different types of SRv6 SIDs represent different functions. For example, for an End SID, it represents an Endpoint SID that identifies a certain destination Node (Node) in the network. And the End SID is diffused to other network elements through an IGP protocol, and is globally visible and locally effective.
In one approach, as shown in fig. 2, the End SID may be an end.dt4 SID. And the end.DT4 SID represents the Endpoint SID of the PE type and is used for identifying a certain IPv4 VPN instance in the network. Further, the forwarding action corresponding to the end.DT4 SID is decapsulating the packet and looking up the IPv4 VPN instance routing table for forwarding. End.dt4 SID is used in the L3VPNv4 scenario, equivalent to the label of IPv4 VPN. End.dt4 SID may also be used to identify a public network instance.
Optionally, the end.dt4 SID may be generated through static configuration, or may be automatically allocated within the dynamic SID range of the Locator through BGP.
In another way, as shown in fig. 3, the End SID may also be an end.dt6 SID, where the end.dt6 SID may represent an Endpoint SID of PE type, used to identify a certain IPv 6VPN instance in the network. And the forwarding action corresponding to the end.DT6 SID is to decapsulate the message and look up the IPv 6VPN instance routing table for forwarding. End.dt6 SID is used in the L3VPNv6 scenario, equivalent to the label of IPv6 VPN. End.dt6 SID may also be used to identify a public network instance.
Optionally, the end.dt6 SID may be generated through static configuration, or may be automatically allocated within the dynamic SID range of the Locator through BGP.
Further, in the current SRv6VPN networking scenario, each node device can only associate with one Locator, and each Locator only allocates one SID to each VPN, so that both the intra-domain node device transmission route and the cross-domain node device transmission route can only carry the same SID, that is, only the same link route can be used between multiple node devices. This may result in a route that is more stressed. The purpose of load sharing cannot be achieved.
Further, this is because in the SRv6VPN networking scenario, each node of SRv6 needs to maintain a Local SID (Local SID) table, which contains all SRv6 Segment information generated at this node, and a forwarding table (FIB) of SRv6 can be generated according to this table.
In order to solve the existing problems, in the embodiment of the present application, two locators may be allocated to each PE device. I.e., one intra-domain Locator for intra-domain route distribution and one extra-domain Locator for extra-domain route distribution. In the subsequent process of route release, the PE device can select to carry correspondingly different Locator according to the difference of the release object. Thereby realizing the load balancing function among multiple routing selections.
In one mode, for example, when receiving an intra-domain route sending instruction, the first PE device may send a route to the second PE device, where the route carries a first intra-domain Locator used for intra-domain route issue, and it should be noted that the first intra-domain Locator includes a first SID used for implementing intra-domain data forwarding. And enabling the PE device of the opposite end to complete the route distribution to the first PE device according to the first SID.
S102, when receiving a cross-domain route sending instruction, carrying a first out-of-domain Locator when sending a route to an out-of-domain node device, wherein the out-of-domain Locator comprises a second SID for realizing out-of-domain data forwarding.
In one mode, for example, when receiving a sending instruction of an out-of-domain route, the first PE device may send a route to an out-of-domain node device of an opposite end, where the route carries a first out-of-domain Locator used for issuing an out-of-domain route, and it needs to be noted that the first out-of-domain Locator includes a second SID used for forwarding out-of-domain data. And enabling the PE device of the opposite end to complete the routing issue of the first PE device according to the second SID.
Further, the embodiment of the present application is described by taking an example in which the first out-of-domain Locator is carried when the route is sent to the out-of-domain node device, and a specific flow thereof is as follows:
the method comprises the following steps: the first out-of-domain Locator needs to be configured on the first PE device in advance. And the first PE device distributes the SID of the corresponding multi-VPN instance in the scope of the Locator outside the first domain, and generates a LocalSID table according to the SID.
Step two: the first PE device needs to associate the first out-of-domain Locator with the out-of-domain node device outside the AS domain, where the association may be by exchanging SRv6 SID information of the two locators in a unicast routing manner. That is, the first PE device propagates the second SID to the out-of-domain node device. The unicast routing manner may be VPNv4, VPNv6, IPv4 unicast, IPv6 unicast, or the like.
Step three: when the first PE device (and other PE devices in the same domain) sends a route to the out-of-domain node device outside the AS domain, the route carries the first out-of-domain Locator (which includes the second SID information). When receiving the routes sent by the first PE device and other PE devices in the same domain, the outside-domain node device may issue equivalent routes to the corresponding PE devices according to the SIDs. The next hops are the first PE device and the other PE devices, respectively.
In the application, when receiving an intra-domain route sending instruction, the first intra-domain Locator may be carried when sending a route to the second PE device, where the intra-domain Locator includes a first SID for implementing intra-domain data forwarding; and when receiving a cross-domain route sending instruction, carrying a first out-of-domain Locator when sending a route to the out-of-domain node equipment, wherein the out-of-domain Locator comprises a second SID for realizing out-of-domain data forwarding. By applying the technical scheme of the application, the Locator containing different SIDs can be allocated to each PE device in an SRv6VPN networking scene, so that the PE device can select the corresponding Locator to perform routing publishing according to whether the publishing object is in the same data domain or not. Therefore, in the multi-homing networking, the remote PE and the home PE can form equivalent load sharing, and the network reliability is improved.
Optionally, in a possible implementation manner of the present application, before determining that the intra-domain routing transmission instruction is received, the method further includes:
receiving a first configuration instruction, wherein the first configuration instruction is used for configuring a first intra-domain Locator and a first out-of-domain Locator for the first PE device;
configuring a first SID under a target VPN on a first intra-domain Locator, and generating an intra-domain Local SID table according to the first SID; and the number of the first and second groups,
and configuring a second SID under multiple VPNs on the first out-of-domain Locator, and generating an out-of-domain Local SID table according to the second SID.
Further, in the present application, first, a Locator configuration needs to be performed on each PE in the networking, and specifically, for the first PE device, an intra-domain Locator (i.e., a first intra-domain Locator) and an out-of-domain Locator (i.e., a first out-of-domain Locator) need to be configured for the first PE device.
Then, the first PE device also needs to allocate the SID of a unique VPN instance in the first out-of-domain Locator range, and generate a corresponding in-domain Local SID table. And the first PE device configures SIDs of multiple VPN instances in the scope of the out-of-domain Locator, and generates a corresponding out-of-domain Local SID table. So as to issue the route according to the Local SID table in the data transmission process.
Further, the embodiment of the present application is described by way of example that the route is sent to the intra-domain node device and carries a Locator in the first domain, where the specific flow is as follows:
the method comprises the following steps: the first PE device is configured with a first intra-domain Locator, and the first intra-domain Locator generates a corresponding SID.
Step two: the first PE device carries the Locator in the first domain when sending the route to the second PE device through the IGP protocol, wherein the Locator in the first domain contains the first SID.
Step three: and after receiving the Locator in the first domain, the second PE equipment issues the network segment route corresponding to the first SID to the first PE equipment. Such that the first PE device installs the route into its routing table.
It should be noted that, when the routing interaction is performed between the first PE device and the second PE device, the end.dt46 SID of the out-of-domain Locator cannot be used, because a Local SID entry corresponding to the out-of-domain Locator exists locally in each PE device, and because Local priority is given, the received PE device routing cannot form load sharing, and cannot automatically specify different SIDs.
Optionally, in a possible implementation manner of the present application, after generating the out-of-domain Local SID table, the method further includes:
receiving an association instruction, wherein the association instruction is used for associating a first out-of-domain Locator with the out-of-domain node equipment;
sending a second SID to the out-of-domain node device; receiving the SID of the out-of-domain node sent by the out-of-domain node equipment;
and when receiving a cross-domain route sending instruction, sending a route to the node equipment outside the domain according to the SID of the node outside the domain.
When the first PE device (and the second PE device within the group network) sends a route to the AS out-of-domain node device, all the first PE device and the second PE device need to carry the same SID information of the out-of-domain Locator. After receiving the plurality of SID information, the outside-domain node device routes the received SID information to form an equivalent, and the next hops are the first PE device and the second PE device, respectively.
It should be noted that, in the present application, the first PE device also needs to carry SID information of the intra-domain Locator when sending the route to the second PE device. Thus, the routing on the second PE device forms an equivalent down-route and forwarding table, and the next hops are the first PE device and the CE device, respectively.
Optionally, in one possible embodiment of the present application, the out-of-domain Locator is an anycast Locator, and the in-domain Locator is a unicast Locator.
Fig. 4 schematically shows a flowchart of a method for route distribution according to an embodiment of the present application. As shown in fig. 4, the method is applied to a second PE device in an SRv6VPN networking scenario, where the first PE device is configured with a second in-domain Locator and a second out-of-domain Locator, and includes:
s201, when receiving the intra-domain route sending instruction, receiving the route and the first intra-domain Locator sent by the first PE device.
S202, when receiving the cross-domain route sending instruction, the route is sent to the node equipment outside the domain, and the route carries a second outside-domain Locator, wherein the outside-domain Locator comprises a second SID for realizing data forwarding outside the domain.
Furthermore, when the second PE device in the networking receives the intra-domain route transmission instruction, the route and the first intra-domain Locator transmitted by the first PE device may be received.
It can be understood that the second PE device needs to extract the first SID in the Locator in the first domain, and add the first SID information to the local routing table after establishing the corresponding relationship with the route issued by the first PE device. And subsequently issuing a route to the first PE device according to the first SID.
In addition, when receiving the cross-domain route sending instruction, the second out-of-domain Locator carrying the second SID when sending the route to the out-of-domain node device may be used. Specifically, the second PE device may associate the second out-of-domain Locator with the out-of-domain node device outside the AS domain in advance, where the association may be by exchanging SRv6 SID information of the two locators in a unicast routing manner. I.e., the second PE device propagates the second SID to the out-of-domain node device. The unicast routing manner may be VPNv4, VPNv6, IPv4 unicast, IPv6 unicast, or the like.
Further, the second PE device may carry the second out-of-domain Locator (including the second SID information) when sending the route to the out-of-domain node device outside the AS domain. When receiving the routes sent by the second PE device and other PE devices in the same domain, the outside-domain node device may issue equivalent routes to the corresponding PE devices according to the SIDs. The next hop is the second PE device and the other PE devices in the same domain, respectively.
Optionally, in a possible implementation manner of the present application, after receiving the routing information and the Locator in the first domain sent by the first PE device, the method further includes:
extracting a first SID carried by a Locator in a first domain;
and establishing a corresponding relation between the first SID information and the route and then adding the first SID information and the route into a local routing table.
In this embodiment of the present application, after receiving the routing information and the Locator in the first domain sent by the first PE device, the second PE device may extract the first SID therein, store the correspondence between the first SID information and the route, and add the correspondence to the local routing table. So that communication with the first PE device can be subsequently performed according to the correspondence. In addition, after the second PE device receives the Locator in the first domain, the network segment route corresponding to the first SID may be issued to the first PE device. Such that the first PE device installs the route into its routing table.
Optionally, in a possible implementation manner of the present application, before receiving the intra-domain routing sending instruction, the method further includes:
receiving a second configuration instruction, wherein the second configuration instruction is used for configuring a second intra-domain Locator and a second out-of-domain Locator for the second PE device;
configuring a third SID of the target VPN domain on a Locator in the second domain, and generating an intra-domain Local SID table according to the third SID; and the number of the first and second groups,
and configuring a fourth SID of the multiple VPN domains on the first out-of-domain Locator, and generating an out-of-domain Local SID table according to the fourth SID.
Further, the present application also needs to configure a Locator for the second PE in the network, and specifically, for the second PE device, it first needs to configure an intra-domain Locator (i.e., a second intra-domain Locator) and an out-of-domain Locator (i.e., a second out-of-domain Locator).
Then, the second PE device also needs to allocate the SID of a unique VPN instance in the second out-of-domain Locator range, and generate a corresponding in-domain Local SID table. And the second PE device configures SIDs of multiple VPN instances in the domain outside Locator range, and generates a corresponding domain outside Local SID table. So as to issue the route according to the Local SID table in the data transmission process.
Furthermore, the second PE device also needs to associate the second out-of-domain Locator with the out-of-domain node device outside the AS domain, where the association may be by exchanging SRv6 SID information of the two locators through a unicast routing manner. I.e., the second PE device propagates the second SID to the out-of-domain node device. The unicast routing manner may be VPNv4, VPNv6, IPv4 unicast, IPv6 unicast, or the like.
Furthermore, the second PE device (and other PE devices in the same domain) carries the second out-of-domain Locator (including the second SID information) when sending the route to the out-of-domain node device outside the AS domain. When receiving the routes sent by the second PE device and other PE devices in the same domain, the outside-domain node device may issue equivalent routes to the corresponding PE devices according to the SIDs. The next hops are the first PE device and the other PE devices, respectively.
In an optional embodiment, as shown in fig. 5, a schematic flow diagram for performing routing distribution on a first PE device and a second PE device provided in this application is shown, where the schematic flow diagram includes:
for the first PE, it may receive a first configuration instruction for configuring a first intra-domain Locator and a first out-of-domain Locator for the first PE device, configure a first SID of a unique data domain on the first intra-domain Locator, and generate an intra-domain Local SID table according to the first SID; and configuring a second SID of the multiple data domains on the first out-of-domain Locator, and generating an out-of-domain Local SID table according to the second SID.
Further, after the intra-domain route sending instruction is determined to be received, the first intra-domain Locator is used for sending route information to the second PE device, and the second PE device is configured with a second intra-domain Locator and a second out-of-domain Locator, wherein the intra-domain Locator is used for realizing intra-domain data forwarding, and the out-of-domain Locator is used for realizing cross-domain data forwarding. And after determining that the cross-domain routing sending instruction is received, sending routing information to the node equipment outside the domain by using the first out-of-domain Locator.
Optionally, for the second PE device, it may receive a second configuration instruction for configuring a second intra-domain Locator and a second out-of-domain Locator for the second PE device, configure a third SID of the target VPN domain on the second intra-domain Locator, and generate an intra-domain Local SID table according to the third SID; and configuring a fourth SID of the multiple VPN domains on the first out-of-domain Locator, and generating an out-of-domain LocalSID table according to the fourth SID.
Further, after the second PE device determines that the intra-domain route transmission instruction is received, when the intra-domain route transmission instruction is received, the route and the first intra-domain Locator transmitted by the first PE device are received;
and when the second PE device receives the cross-domain route sending instruction, the second PE device carries a second out-of-domain Locator when sending the route to the out-of-domain node device, wherein the out-of-domain Locator comprises a second SID for realizing out-of-domain data forwarding.
By applying the technical scheme of the application, the Locator containing different SIDs can be allocated to each PE device in an SRv6VPN networking scene, so that the PE device can select the corresponding Locator to perform routing publishing according to whether the publishing object is in the same data domain or not. Therefore, in the multi-homing networking, the remote PE and the home PE can form equivalent load sharing, and the network reliability is improved.
In another embodiment of the present application, as shown in fig. 6, the present application further provides a device for routing distribution. The device is applied to a first PE device in an SRv6VPN networking scene, wherein the first PE device is configured with a first intra-domain Locator and a first out-of-domain Locator, and the device comprises:
a first receiving module 301, configured to, when receiving an intra-domain route sending instruction, carry a first intra-domain Locator when sending a route to a second PE device, where the intra-domain Locator includes a first SID for implementing intra-domain data forwarding;
the first sending module 302 is configured to, when receiving a cross-domain route sending instruction, carry the first out-of-domain Locator when sending a route to an out-of-domain node device, where the out-of-domain Locator includes a second SID for implementing out-of-domain data forwarding.
In the application, when receiving an intra-domain route sending instruction, the first intra-domain Locator may be carried when sending a route to the second PE device, where the intra-domain Locator includes a first SID for implementing intra-domain data forwarding; and when receiving a cross-domain route sending instruction, carrying a first out-of-domain Locator when sending a route to the out-of-domain node equipment, wherein the out-of-domain Locator comprises a second SID for realizing out-of-domain data forwarding. By applying the technical scheme of the application, the Locator containing different SIDs can be allocated to each PE device in an SRv6VPN networking scene, so that the PE device can select the corresponding Locator to perform routing publishing according to whether the publishing object is in the same data domain or not. Therefore, in the multi-homing networking, the remote PE and the home PE can form equivalent load sharing, and the network reliability is improved.
In another embodiment of the present application, the first receiving module 301 further includes:
a first receiving module 301, configured to receive a first configuration instruction, where the first configuration instruction is used to configure the first intra-domain Locator and the first out-of-domain Locator for the first PE device;
a first receiving module 301, configured to configure a first SID in a target VPN in the first domain Locator, and generate a domain Local SID table according to the first SID; and the number of the first and second groups,
the first receiving module 301 is configured to configure a second SID under multiple VPNs on the first out-of-domain Locator, and generate an out-of-domain Local SID table according to the second SID.
In another embodiment of the present application, the first receiving module 301 further includes:
a first receiving module 301, configured to receive an association instruction, where the association instruction is used to associate the first out-of-domain Locator with the out-of-domain node device;
a first receiving module 301 configured to send the second SID to the out-of-domain node device; receiving the SID of the out-of-domain node sent by the out-of-domain node equipment;
a first receiving module 301, configured to send a route to the out-of-domain node device according to the out-of-domain node SID when receiving the cross-domain route sending instruction.
In another embodiment of the present application, the out-of-domain Locator is an anycast Locator, and the in-domain Locator is a unicast Locator.
In another embodiment of the present application, as shown in fig. 6, the present application further provides a device for routing distribution. The device is applied to a second PE device in an SRv6VPN networking scene, wherein a second intra-domain Locator and a second out-of-domain Locator are configured on the first PE device, and the device comprises:
a second receiving module 303, configured to receive, when receiving the intra-domain route sending instruction, a route and a first intra-domain Locator sent by the first PE device;
the second sending module 304 is configured to, when receiving the cross-domain route sending instruction, carry the second out-of-domain Locator when sending the route to the out-of-domain node device, where the out-of-domain Locator includes a second SID for implementing out-of-domain data forwarding.
In another embodiment of the present application, the second receiving module 303 further includes:
a second receiving module 303, configured to extract a first SID carried by a Locator in the first domain;
the second receiving module 303 is configured to add the first SID information to a local routing table after establishing a corresponding relationship with the route.
In another embodiment of the present application, the second receiving module 303 further includes:
a second receiving module 303, configured to receive a second configuration instruction, where the second configuration instruction is used to configure the second intra-domain Locator and the second out-of-domain Locator for the second PE device;
a second receiving module 303, configured to configure a third SID of the target VPN domain on the second domain Locator, and generate an intra-domain Local SID table according to the third SID; and the number of the first and second groups,
the second receiving module 303 is configured to configure a fourth SID of the multiple VPN domains on the first out-of-domain Locator, and generate an out-of-domain Local SID table according to the fourth SID.
Fig. 7 is a block diagram illustrating a logical structure of an electronic device in accordance with an exemplary embodiment. For example, the electronic device 400 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
In an exemplary embodiment, there is also provided a non-transitory computer readable storage medium, such as a memory, including instructions executable by an electronic device processor to perform the method of network monitoring described above, the method comprising: when receiving an intra-domain route sending instruction, carrying the first intra-domain Locator when sending a route to second PE equipment, wherein the intra-domain Locator comprises a first SID for realizing intra-domain data forwarding; and when receiving a cross-domain route sending instruction, carrying the first out-of-domain Locator when sending a route to out-of-domain node equipment, wherein the out-of-domain Locator contains a second SID for realizing out-of-domain data forwarding. Optionally, the instructions may also be executable by a processor of the electronic device to perform other steps involved in the exemplary embodiments described above. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, there is also provided an application/computer program product including one or more instructions executable by a processor of an electronic device to perform the above-described method of network monitoring, the method comprising: when receiving an intra-domain route sending instruction, carrying the first intra-domain Locator when sending a route to second PE equipment, wherein the intra-domain Locator comprises a first SID for realizing intra-domain data forwarding; and when receiving a cross-domain route sending instruction, carrying the first out-of-domain Locator when sending a route to out-of-domain node equipment, wherein the out-of-domain Locator contains a second SID for realizing out-of-domain data forwarding. Optionally, the instructions may also be executable by a processor of the electronic device to perform other steps involved in the exemplary embodiments described above.
Fig. 7 is an exemplary diagram of an electronic device 400. Those skilled in the art will appreciate that the schematic diagram 7 is merely an example of the electronic device 400 and does not constitute a limitation of the electronic device 400 and may include more or less components than those shown, or combine certain components, or different components, e.g., the electronic device 400 may also include input-output devices, network access devices, buses, etc.
The Processor 402 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor 402 may be any conventional processor or the like, the processor 402 being the control center for the electronic device 400 and various interfaces and lines connecting the various parts of the overall electronic device 400.
Memory 401 may be used to store computer readable instructions 403 and processor 402 may implement various functions of electronic device 400 by executing or executing computer readable instructions or modules stored in memory 401 and by invoking data stored in memory 401. The memory 401 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to the use of the electronic device 400, and the like. In addition, the Memory 401 may include a hard disk, a Memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Memory Card (Flash Card), at least one disk storage device, a Flash Memory device, a Read-Only Memory (ROM), a Random Access Memory (RAM), or other non-volatile/volatile storage devices.
The modules integrated by the electronic device 400 may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by hardware related to computer readable instructions, which may be stored in a computer readable storage medium, and when the computer readable instructions are executed by a processor, the steps of the method embodiments may be implemented.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (10)

1. A method for route release is applied to a first PE device in an SRv6VPN networking scene, wherein the first PE device is configured with a first intra-domain Locator and a first out-of-domain Locator, and the method comprises the following steps:
when receiving an intra-domain route sending instruction, carrying the first intra-domain Locator when sending a route to second PE equipment, wherein the intra-domain Locator comprises a first SID for realizing intra-domain data forwarding;
and when receiving a cross-domain route sending instruction, carrying the first out-of-domain Locator when sending a route to out-of-domain node equipment, wherein the out-of-domain Locator contains a second SID for realizing out-of-domain data forwarding.
2. The method of claim 1, wherein prior to said receiving an intra-domain routing instruction, further comprising:
receiving a first configuration instruction, where the first configuration instruction is used to configure the first intra-domain Locator and the first out-of-domain Locator for the first PE device;
configuring a first SID under a target VPN on the first intra-domain Locator, and generating an intra-domain Local SID table according to the first SID; and the number of the first and second groups,
and configuring a second SID under multiple VPNs on the first out-of-domain Locator, and generating an out-of-domain Local SID table according to the second SID.
3. The method of claim 2, wherein after the generating the out-of-domain Local SID table, further comprising:
receiving an association instruction, wherein the association instruction is used for associating the first out-of-domain Locator with the out-of-domain node device;
sending the second SID to the out-of-domain node device; receiving the SID of the out-of-domain node sent by the out-of-domain node equipment;
and when the cross-domain route sending instruction is received, sending a route to the outside-domain node equipment according to the outside-domain node SID.
4. The method of any of claims 1-3, wherein the out-of-domain Locator is an anycast Locator and the in-domain Locator is a unicast Locator.
5. A method for releasing a route is characterized in that the method is applied to a second PE device in an SRv6VPN networking scene, and a second intra-domain Locator and a second extra-domain Locator are configured on the first PE device, and the method comprises the following steps:
when receiving an intra-domain route sending instruction, receiving a route and a first intra-domain Locator sent by first PE equipment;
and when receiving a cross-domain route sending instruction, carrying the second out-of-domain Locator when sending a route to out-of-domain node equipment, wherein the out-of-domain Locator contains a second SID for realizing out-of-domain data forwarding.
6. The method of claim 5, wherein after receiving the routing information and the first intra-domain Locator sent by the first PE device, further comprising:
extracting a first SID carried by a Locator in the first domain;
and establishing a corresponding relation between the first SID information and the route and then adding the first SID information and the route into a local routing table.
7. The method of claim 6, prior to said receiving an intra-domain routing instruction, further comprising:
receiving a second configuration instruction, where the second configuration instruction is used to configure the second intra-domain Locator and the second out-of-domain Locator for the second PE device;
configuring a third SID of the target VPN domain on the second intra-domain Locator, and generating an intra-domain Local SID table according to the third SID; and the number of the first and second groups,
and configuring a fourth SID of the multiple VPN domains on the first out-of-domain Locator, and generating an out-of-domain Local SID table according to the fourth SID.
8. The device for route distribution is applied to a first PE device in an SRv6VPN networking scenario, where the first PE device is configured with a first intra-domain Locator and a first out-of-domain Locator, and includes:
the first receiving module is configured to carry the first intra-domain Locator when a route is sent to the second PE device when receiving an intra-domain route sending instruction, where the intra-domain Locator includes a first SID for implementing intra-domain data forwarding;
the first sending module is configured to carry the first out-of-domain Locator when sending a route to an out-of-domain node device when receiving a cross-domain route sending instruction, where the out-of-domain Locator includes a second SID for implementing out-of-domain data forwarding.
9. The device for route publishing is applied to a second PE device in an SRv6VPN networking scene, wherein a second intra-domain Locator and a second extra-domain Locator are configured on a first PE device, and the device comprises:
the second receiving module is configured to receive the route and the first intra-domain Locator sent by the first PE device when receiving the intra-domain route sending instruction;
and the second sending module is configured to carry a second out-of-domain Locator when sending a route to an out-of-domain node device when receiving a cross-domain route sending instruction, wherein the out-of-domain Locator contains a second SID for realizing out-of-domain data forwarding.
10. An electronic device, comprising:
a memory for storing executable instructions; and the number of the first and second groups,
a processor for display with the memory to execute the executable instructions to perform the operations of the method of routing an advertisement of any of claims 1-7.
CN202111249989.6A 2021-10-26 2021-10-26 Method, device, electronic equipment and medium for route publishing Active CN113992558B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111249989.6A CN113992558B (en) 2021-10-26 2021-10-26 Method, device, electronic equipment and medium for route publishing

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111249989.6A CN113992558B (en) 2021-10-26 2021-10-26 Method, device, electronic equipment and medium for route publishing

Publications (2)

Publication Number Publication Date
CN113992558A CN113992558A (en) 2022-01-28
CN113992558B true CN113992558B (en) 2023-04-18

Family

ID=79741813

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111249989.6A Active CN113992558B (en) 2021-10-26 2021-10-26 Method, device, electronic equipment and medium for route publishing

Country Status (1)

Country Link
CN (1) CN113992558B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111669330A (en) * 2019-03-08 2020-09-15 华为技术有限公司 BIER message sending method and device

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109873760B (en) * 2017-12-01 2020-08-07 华为技术有限公司 Method and device for processing route, and method and device for data transmission
CN110830352B (en) * 2018-08-07 2022-09-23 中兴通讯股份有限公司 Method and device for realizing VPN cross-domain and boundary node
CN113162849A (en) * 2020-01-22 2021-07-23 华为技术有限公司 Message processing method, device and system
CN113300949B (en) * 2020-02-24 2022-12-06 华为技术有限公司 Method for forwarding message, method, device and system for releasing routing information
CN113381932B (en) * 2020-03-09 2022-12-27 华为技术有限公司 Method and network equipment for generating segment identifier SID
CN113382452B (en) * 2020-03-09 2023-04-07 中国移动通信有限公司研究院 Path establishing method, data transmission method, device, network node and storage medium
CN112511428A (en) * 2020-03-10 2021-03-16 中兴通讯股份有限公司 Message encapsulation method, message forwarding method, notification method, electronic device, and storage medium
CN113438161B (en) * 2020-03-23 2022-10-04 华为技术有限公司 Method and network device for generating segment identification SID

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111669330A (en) * 2019-03-08 2020-09-15 华为技术有限公司 BIER message sending method and device

Also Published As

Publication number Publication date
CN113992558A (en) 2022-01-28

Similar Documents

Publication Publication Date Title
CN112087386B (en) Message processing method, device and system
CN109729012B (en) Unicast message transmission method and device
CN108965092B (en) Data message transmission method and device
CN103095546A (en) Method, device and data center network for processing messages
CN107181812B (en) Acceleration agent device, acceleration agent method and content management system
CN108494701B (en) Load sharing method and device
CN109412926B (en) Tunnel establishment method and device
CN110730133B (en) Route notification method and system
CN108600074A (en) The retransmission method and device of multicast data message
CN108259379B (en) Flow forwarding method and device
CN107547665A (en) A kind of method, equipment and the system of dhcp address distribution
CN113726654A (en) Message forwarding method and device of SRV6 protocol, electronic equipment and medium
CN109412949A (en) A kind of data message transmission method and device
CN113660164A (en) Message forwarding method and network equipment
CN108322376B (en) Route synchronization method, device and machine-readable storage medium
EP4236245A1 (en) Route advertisement method, apparatus, and system
CN109728926B (en) Communication method and network device
CN111464443B (en) Message forwarding method, device, equipment and storage medium based on service function chain
CN113992558B (en) Method, device, electronic equipment and medium for route publishing
CN105939262B (en) Label distribution method and device
CN111130978B (en) Network traffic forwarding method and device, electronic equipment and machine-readable storage medium
CN107294857B (en) Multicast distribution processing method, device and system
CN105610717B (en) A kind of route issuing method and device across SDN network
CN113132505A (en) Method, device, computing equipment and storage medium for sending response message
CN108471374B (en) Data message forwarding method and device

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