CN109802888B - Method and device based on anycast address protection - Google Patents
Method and device based on anycast address protection Download PDFInfo
- Publication number
- CN109802888B CN109802888B CN201711135592.8A CN201711135592A CN109802888B CN 109802888 B CN109802888 B CN 109802888B CN 201711135592 A CN201711135592 A CN 201711135592A CN 109802888 B CN109802888 B CN 109802888B
- Authority
- CN
- China
- Prior art keywords
- domain boundary
- anycast address
- boundary node
- node
- forwarding information
- 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
Links
Images
Abstract
The invention discloses a method and a device based on anycast address protection, wherein the method comprises the following steps: configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node; after receiving the anycast address and the anycast address field label, the neighbor nodes adjacent to the domain boundary node respectively create forwarding information containing the forwarding information to each domain boundary node, and set the forwarding information of one main domain boundary node as an active state and the forwarding information to the standby domain boundary node as an inactive state; and during message forwarding, if the neighbor node detects that the forwarding information to the main domain boundary node is invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
Description
Technical Field
The present invention relates to the field of data communication technologies, and in particular, to a method and an apparatus for protecting based on an anycast address.
Background
draft-ietf-spring-Segment-Routing-12 describes the structure of SR (Segment Routing), and the Segment Routing technology enables a node to specify its forwarding path for a specific packet, instead of forwarding according to the general shortest path, and by adding information related to Segment List composed of Segment IDs in the packet, it is not necessary to maintain state information of each path on an intermediate node. The Segment routing mainly extends IGP (Interior Gateway Protocol)/BGP (Border Gateway Protocol) to support advertisement and learning Segment ID, and generally, in a network in which the Segment routing is deployed, it is no longer necessary to deploy LDP (Label Distribution Protocol) and RSVP-TE (Resource ReSerVation Protocol-Traffic Engineering, Resource ReSerVation Protocol based on Traffic Engineering extension) protocols. In a Segment Routing network, an SR-TE (Segment Routing-Traffic Engineering) tunnel can not only deploy end-to-end path detection and protection, but also benefit from a local protection technology provided by IGP/BGP, so that protection is more comprehensive.
In a segment routing network, a known Local protection technology is TI-LFA (Topology Independent Loop-free backup), which is defined in draft-bandwidth-rtwg-segment-routing-TI-LFA-01, and may be used to perform Local protection in area, and when a PLR (Point of Local Repair node) detects a failure of a primary link or a primary next-hop node, the traffic may be quickly switched to a backup path, where the backup path may be as simple as including only a single link or a single node, or as complex as including a segment list. However, TI-LFA is not suitable for redundant protection of domain border nodes in cross-domain scenarios, for which known methods are:
1) draft-ietf-spring-segment-routing-12 describes how to make slow convergence protection by means of anycast segment. The disadvantage is that the flow is slow to converge after the failure occurs.
2) draft-ietf-spring-segment-routing-12 describes mirror protection by the mirror segment, and similar mirror protection examples are also described in draft-powers-spring-biasing-lsps-with-sr-01 and draft-help-spring-node-protection-for-sr-te-routes-00. The disadvantage of the mirror protection is that the tag table entry of the specific context space needs to be maintained on the mirror node, which is complex to implement.
3) draft-ietf-spring-segment-routing-central-epe-06 describes redundant protection of a peer node on an egress PE by a peer-set segment. But this approach does not address redundant protection of the egress PE itself.
Disclosure of Invention
The technical problem solved by the scheme provided by the embodiment of the invention is that the existing domain boundary node redundancy protection technology in the cross-domain scene is various and complex and cannot achieve rapid convergence of traffic.
The method based on the anycast address protection provided by the embodiment of the invention comprises the following steps:
configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node;
after receiving the anycast address and the anycast address field label, the neighbor nodes adjacent to the domain boundary node respectively create forwarding information containing the forwarding information to each domain boundary node, and set the forwarding information of one main domain boundary node as an active state and the forwarding information to the standby domain boundary node as an inactive state;
and during message forwarding, if the neighbor node detects that the forwarding information to the main domain boundary node is invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
Preferably, the notifying, by the domain border node, the anycast address and the anycast address segment tag to the neighbor nodes of the domain border node includes:
and the domain boundary node advertises the anycast address containing the anycast group mark and the anycast address field label to a neighbor node in the domain of the domain boundary node through an Interior Gateway Protocol (IGP).
Preferably, the setting, by the neighbor node, of the forwarding information to the border node of the main domain to an active state, and the setting, by the neighbor node, of the forwarding information to the border node of the standby domain to an inactive state includes:
and the neighbor node takes the directly connected downstream domain boundary node as a main domain boundary node and takes the non-directly connected downstream domain boundary node as a standby domain boundary node.
Preferably, the method further comprises the following steps: and in the message forwarding period, if the neighbor node detects that the forwarding information of the main domain boundary node is effective, the forwarding information of the main domain boundary node is used for forwarding the message.
The device based on the anycast address protection provided by the embodiment of the invention comprises:
the configuration and notification module is used for configuring the same anycast address and anycast address field label for each domain boundary node which mutually forms redundancy protection, and notifying the anycast address and the anycast address field label to the neighbor node of the domain boundary node;
a creating module, configured to respectively create forwarding information including information to each domain border node after receiving the anycast address and the anycast address segment tag, and set the forwarding information of one main domain border node to an active state, and set the forwarding information to a standby domain border node to an inactive state;
and the message forwarding module is used for activating the forwarding information of the standby domain boundary node into an active state so as to forward the message by using the forwarding information of the standby domain boundary node if the forwarding information of the main domain boundary node is detected to be invalid during message forwarding.
Preferably, the configuration and notification module comprises:
the configuration unit is used for configuring the same anycast address and the same anycast address field label for each domain boundary node which mutually forms redundancy protection;
and the notification unit is used for notifying the anycast address containing the anycast group mark and the anycast address field label to the neighbor node in the domain of the anycast address field label through an interior gateway protocol IGP.
Preferably, the creating module is specifically configured to use the domain border node directly connected to the downstream as a master domain border node, and use the domain border node not directly connected to the downstream as a standby domain border node.
Preferably, the packet forwarding module is further specifically configured to, during packet forwarding, forward a packet using the forwarding information to the home domain border node if it is detected that the forwarding information to the home domain border node is valid.
According to an embodiment of the present invention, an apparatus for protecting based on anycast address, the apparatus includes: a processor, and a memory coupled to the processor; the memory having stored thereon a program for anycast address protection executable on the processor, the program for anycast address protection when executed by the processor implementing:
configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node;
after receiving the anycast address and the anycast address field label, respectively creating forwarding information including forwarding information to each domain boundary node, setting the forwarding information of one main domain boundary node as an active state, and setting the forwarding information to a standby domain boundary node as an inactive state;
and during message forwarding, if the forwarding information to the main domain boundary node is detected to be invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
According to an embodiment of the present invention, there is provided a computer storage medium storing a program based on anycast address protection, the program based on anycast address protection being implemented by a processor to include:
configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node;
after receiving the anycast address and the anycast address field label, respectively creating forwarding information including forwarding information to each domain boundary node, setting the forwarding information of one main domain boundary node as an active state, and setting the forwarding information to a standby domain boundary node as an inactive state;
and during message forwarding, if the forwarding information to the main domain boundary node is detected to be invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
According to the scheme provided by the embodiment of the invention, the domain boundary node redundancy protection mechanism based on the anycast address is simpler, can quickly converge the flow and is applied to a specific scene.
Drawings
Fig. 1 is a flowchart of a method for anycast address protection according to an embodiment of the present invention;
fig. 2 is a schematic diagram of an apparatus for anycast address protection according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a Prefix-SID (Segment ID, Segment tag) Sub-TLV (type, length, value, type, length, value) provided by an embodiment of the present invention;
fig. 4 is a network topology diagram based on anycast address protection according to an embodiment of the present invention.
Detailed Description
The preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings, and it should be understood that the preferred embodiments described below are only for the purpose of illustrating and explaining the present invention, and are not to be construed as limiting the present invention.
Fig. 1 is a flowchart of a method for protecting based on anycast address according to an embodiment of the present invention, as shown in fig. 1, including:
step S101: configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node;
step S102: after receiving the anycast address and the anycast address field label, the neighbor nodes adjacent to the domain boundary node respectively create forwarding information containing the forwarding information to each domain boundary node, and set the forwarding information of one main domain boundary node as an active state and the forwarding information to the standby domain boundary node as an inactive state;
step S103: and during message forwarding, if the neighbor node detects that the forwarding information to the main domain boundary node is invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
Wherein the notifying, by the domain border node, the anycast address and the anycast address segment tag to the neighbor nodes of the domain border node comprises: and the domain boundary node advertises the anycast address containing the anycast group mark and the anycast address field label to a neighbor node in the domain of the domain boundary node through an Interior Gateway Protocol (IGP).
The setting of the forwarding information to the standby domain boundary node to be in an inactive state includes: and the neighbor node takes the directly connected downstream domain boundary node as a main domain boundary node and takes the non-directly connected downstream domain boundary node as a standby domain boundary node.
The embodiment of the invention also comprises the following steps: and in the message forwarding period, if the neighbor node detects that the forwarding information of the main domain boundary node is effective, the forwarding information of the main domain boundary node is used for forwarding the message.
Fig. 2 is a schematic diagram of an apparatus for protecting based on anycast address according to an embodiment of the present invention, as shown in fig. 2, including: a configuration and notification module 201, configured to configure the same anycast address and anycast address segment tag for each domain border node forming redundancy protection with each other, and notify the anycast address and the anycast address segment tag to a neighboring node of the domain border node; a creating module 202, configured to respectively create forwarding information including information to each domain border node after receiving the anycast address and the anycast address segment tag, and set the forwarding information of one main domain border node as an active state, and set the forwarding information to a standby domain border node as an inactive state; the message forwarding module 203 is configured to activate forwarding information of the standby domain boundary node to an active state during message forwarding if it is detected that the forwarding information to the primary domain boundary node is invalid, so as to forward a message with the forwarding information to the standby domain boundary node.
Wherein, the configuration and notification module 201 includes: the configuration unit is used for configuring the same anycast address and the same anycast address field label for each domain boundary node which mutually forms redundancy protection; and the notification unit is used for notifying the anycast address containing the anycast group mark and the anycast address field label to the neighbor node in the domain of the anycast address field label through an interior gateway protocol IGP.
The creating module 202 is specifically configured to use a domain border node directly connected to the downstream as a primary domain border node, and use a domain border node not directly connected to the downstream as a backup domain border node.
The message forwarding module 203 is further specifically configured to, during message forwarding, forward a message by using the forwarding information to the home domain border node if it is detected that the forwarding information to the home domain border node is valid.
An apparatus for protecting based on anycast address provided in an embodiment of the present invention includes: a processor, and a memory coupled to the processor; the memory having stored thereon a program for anycast address protection executable on the processor, the program for anycast address protection when executed by the processor implementing:
configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node;
after receiving the anycast address and the anycast address field label, respectively creating forwarding information including forwarding information to each domain boundary node, setting the forwarding information of one main domain boundary node as an active state, and setting the forwarding information to a standby domain boundary node as an inactive state;
and during message forwarding, if the forwarding information to the main domain boundary node is detected to be invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
The computer storage medium provided by the embodiment of the invention stores a program based on the anycast address protection, and when the program based on the anycast address protection is executed by a processor, the program comprises the following steps:
configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node;
after receiving the anycast address and the anycast address field label, respectively creating forwarding information including forwarding information to each domain boundary node, setting the forwarding information of one main domain boundary node as an active state, and setting the forwarding information to a standby domain boundary node as an inactive state;
and during message forwarding, if the forwarding information to the main domain boundary node is detected to be invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
The invention adopts the following technical scheme: configuring the same anycast address and its prefix-sid (Segment ID, prefix Segment label) on a group of domain border nodes forming redundancy protection with each other, where the prefix-sid of the anycast address can be advertised in area by IGP or advertised between ASs (Autonomous System) by BGP, and when advertising, an anycast-group flag is set to indicate that these border nodes are in the same anycast group. After receiving the anycast address prefix-sid announcement, all neighbor nodes (without the boundary nodes) of the boundary nodes establish corresponding anycast-group table entries, wherein the table entries comprise forwarding information to a plurality of boundary nodes, only the forwarding information to a certain boundary node is in a current active state and can be used for forwarding, and the forwarding information to other boundary nodes is in an inactive state. And if the forwarding information to a certain boundary node in the current active state fails, the effective forwarding information to other certain boundary nodes is reselected to be activated for forwarding.
The invention discloses a protection method based on an anycast address, which comprises the following steps:
the first step is that the same anycast address and its prefix-sid are configured on a group of domain boundary nodes forming redundancy protection with each other, and the anycast-group flag is enabled during prefix-sid configuration. The prefix-sid can be announced to the neighbor by IGP or BGP, and an anycast-group mark is marked when the announcement is made.
Secondly, after receiving the anycast address prefix-sid announcement, all neighboring nodes (without the boundary nodes) of the boundary nodes can additionally establish corresponding anycast-group table entries, wherein the table entries comprise forwarding information to a plurality of boundary nodes, only the forwarding information to a certain boundary node is in a current active state and can be used for forwarding, and the forwarding information to other boundary nodes is in an inactive state.
Specifically, each neighbor node generally attempts to select the forwarding information of the direct connection downstream border node with the minimum metric from the possible established anycast-group entries as the active state. If the boundary node exists, establishing an anycast-group table item, wherein a label forwarding table item corresponding to anycast prefix-sid points to the anycast-group table item, and then giving forwarding information of an active state by the anycast-group table item; if no direct connection downstream boundary node with the minimum metric exists, the anycast-group entry itself does not need to be created, and the label forwarding entry corresponding to the anycast prefix-sid directly contains shortest path forwarding information to the corresponding anycast route.
And thirdly, if the forwarding surface of each neighbor node detects that the forwarding information to a certain directly connected downstream boundary node in the current active state in the anycast-group list item is invalid, the forwarding surface of each neighbor node reselects the effective forwarding information to other certain boundary nodes to activate and forward the forwarding information, preferentially selects other directly connected downstream boundary nodes, and if other directly connected downstream boundary nodes do not exist, selects other non-directly connected boundary nodes to forward the forwarding information according to the shortest path.
Fig. 3 is a schematic diagram of a Prefix-SID (Segment ID, Segment tag) Sub-TLV (type, length, value) provided by an embodiment of the present invention, as shown in fig. 3, for ISIS (Intermediate system to Intermediate system) advertisement Prefix-SID, which is basically the same as that defined in draft-ietf-is-Segment-routing-extensions-13, except that a flag bit is newly added in a Flags field of the present patent, as follows:
AG: the Anycast Group flag bit indicates that the prefix-sid is an Anycast prefix-sid and it is desired that the recipient attempt to establish an Anycast-Group entry.
Similarly, the flag bit may also be added to a prefix-sid advertisement message of OSPF (Open Shortest Path First) or BGP for the same purpose, which is not described again.
Fig. 4 is a network topology diagram based on anycast address protection according to an embodiment of the present invention, as shown in fig. 4, a 1-A8 access to a core network core through a GW (GateWay), and prefix-sid of each node is as shown in the figure, where GW11 and GW12 configure the same anycast address anycast-ip1 and allocate the same anycast prefix-sid 16001, and GW21 and GW22 configure the same anycast address anycast-ip2 and allocate the same anycast prefix-sid 16002. The method comprises the following specific steps:
in step 401, GW11 and GW12 both configure the same anycast address anycast-ip1 and assign the same prefix-sid 16001 (also called prefix-sid 16001) to the anycast address, and enable the prefix-group flag at the same time when configuring the prefix-sid.
In step 402, GW11 and GW12 carry AG (analog-group) flag in the message of the IGP area to which it belongs flooding its analog prefix-sid by ISIS, respectively.
In step 403, for example, a1-a 5 will receive the aforementioned anycast prefix-sid 16001 notified by GW11 and GW12, a1-a 5 will try to create a corresponding anycast-group entry locally, and the anycast-group entry will include two members, namely { GW11, GW12 }. The method specifically comprises the following steps:
the anycast-group entry described above will not be created at a1 because the shortest path next hop from a1 to member GW11 is assumed to be a2, i.e., member GW11 is not a directly connected downstream node of a1, and the shortest path next hop from a1 to member GW12 is assumed to be a4, i.e., member GW12 is not a directly connected downstream node of a 1. The label forwarding entry created for prefix-sid 16001 at a1 will contain the shortest path next hop to anycast-ip1, such as a2 (or a 4).
The anycast-group entries will not be created on a2 and a4 for the same reason. The label forwarding entry created for prefix-sid 16001 at a2 will contain the shortest path next hop A3 to anycast-ip 1. The label forwarding entry created for prefix-sid 16001 at a4 will contain the shortest path next hop a5 to anycast-ip 1.
The anycast-group table entry is created on A3, because the next hop of the shortest path from A3 to member GW11 is GW11, i.e. member GW11 is the direct-connected downstream node of a1, and the condition for creating the anycast-group table entry is satisfied. Further assume that the shortest path next hop from A3 to member GW12 is a 4. The label forwarding table entry created for prefix-sid 16001 on A3 points to the aforementioned created anycast-group table entry, and then the currently active forwarding information given in the anycast-group table entry is shortest path forwarding information to member GW11 (i.e., the next hop is GW11), and the inactive forwarding information is shortest path forwarding information to member GW12 (i.e., the next hop is a 4).
The anycast-group table entry will be created on a5, because the next hop of the shortest path from a5 to GW12 is GW12, i.e. member GW12 is the direct-connected downstream node of a5, which meets the condition of creating the anycast-group table entry. Further assume that the shortest path next hop from a5 to member GW11 is a 2. The label forwarding table entry created for prefix-sid 16001 on a5 points to the aforementioned created anycast-group table entry, and then the currently active forwarding information given in the anycast-group table entry is shortest path forwarding information to member GW12 (i.e., the next hop is GW12), and the inactive forwarding information is shortest path forwarding information to member GW11 (i.e., the next hop is a 2).
In step 404, now assume that there exists an SR TE path { anycast-ip1, anycast-ip2, A8} on a1, and the corresponding SID list is {16001,16002,18008 }. Assuming that the next hop of the shortest path from a1 to anycast-ip1 is a2 and the next hop of the shortest path from GW11 to anycast-ip2 is C1, the actual complete path traversed by the message forwarded according to the SR TE path is: A1-A2-A3-GW11-C1-GW21-A6-A8, namely, the message is forwarded to GW11 according to the shortest path, then forwarded to GW21 according to the shortest path, and then forwarded to A8 according to the shortest path.
In step 405, now, assuming that the node GW11 is considered to be out of service, in the use of the existing anycast service, the existing anycast service waits for the ISIS routing protocol to re-converge, for example, the next hop to the shortest path of anycast-ip1 on a1 is re-converged to a4, and such slow convergence will result in a long packet loss time.
After the method described in this patent is applied, an upstream node A3 of GW11 will directly detect a GW11 fault on a forwarding level, and then trigger a corresponding anycast-group entry { to GW11 (the next hop is GW11), to GW12 (the next hop is a4) } to make a fast switch, that is, the current active entry is fast switched from "to GW11 (the next hop is GW 11)" to GW12 (the next hop is a4) ". Then the packet with top-level SID 16001 forwarded by segment routing will be forwarded to next hop a4 when it reaches A3; a4, after receiving the message, continuing to send the message to GW12 according to the shortest path; after receiving the message, GW12 pops up top SID 16001, and if the new top SID is 16002, the message is continuously sent to GW22 according to the shortest path; after receiving the message, GW22 pops up top SID 16002, and if the new top SID is 18008, it continues to send the message to a8 according to the shortest path. In the above process, the packet loss time caused by fast handover is very short, generally within 50 ms.
Step 406, later, after the routing protocol on the control plane is re-converged, for example, when a next hop to the shortest path of anycast-ip1 on a1 is re-converged to a4, the actual complete path experienced by the packet forwarded according to SID list {16001,16002,18008} is: A1-A4-A5-GW12-C2-GW22-A7-A8, namely, the message is forwarded to GW12 according to the shortest path, then forwarded to GW22 according to the shortest path, and then forwarded to A8 according to the shortest path.
According to the scheme provided by the embodiment of the invention, the energy can be quickly converged by a domain boundary node redundancy protection mechanism based on the anycast address.
Although the present invention has been described in detail hereinabove, the present invention is not limited thereto, and various modifications can be made by those skilled in the art in light of the principle of the present invention. Thus, modifications made in accordance with the principles of the present invention should be understood to fall within the scope of the present invention.
Claims (8)
1. A method of anycast address based protection, comprising:
configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node;
after receiving the anycast address and the anycast address field label, neighbor nodes adjacent to the domain boundary node respectively create forwarding information containing forwarding information to each domain boundary node, and set the forwarding information of a main domain boundary node to be in an active state, and set the forwarding information to a standby domain boundary node to be in an inactive state, wherein the domain boundary node directly connected downstream is used as the main domain boundary node, and the domain boundary node not directly connected downstream is used as the standby domain boundary node;
and during message forwarding, if the neighbor node detects that the forwarding information to the main domain boundary node is invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
2. The method of claim 1, the domain border node advertising the anycast address and anycast address segment label to neighboring nodes of the domain border node comprising:
and the domain boundary node advertises the anycast address containing the anycast group mark and the anycast address field label to a neighbor node in the domain of the domain boundary node through an Interior Gateway Protocol (IGP).
3. The method of claim 1, further comprising: and in the message forwarding period, if the neighbor node detects that the forwarding information of the main domain boundary node is effective, the forwarding information of the main domain boundary node is used for forwarding the message.
4. An apparatus for anycast address protection, comprising:
the configuration and notification module is used for configuring the same anycast address and anycast address field label for each domain boundary node which mutually forms redundancy protection, and notifying the anycast address and the anycast address field label to the neighbor node of the domain boundary node;
a creating module, configured to respectively create forwarding information including information to each domain border node after receiving the anycast address and the anycast address segment tag, and set the forwarding information of one main domain border node to an active state, and set the forwarding information to a standby domain border node to an inactive state; the creating module is specifically configured to use a domain boundary node directly connected to a downstream as a primary domain boundary node, and use a domain boundary node not directly connected to the downstream as a backup domain boundary node;
and the message forwarding module is used for activating the forwarding information of the standby domain boundary node into an active state so as to forward the message by using the forwarding information of the standby domain boundary node if the forwarding information of the main domain boundary node is detected to be invalid during message forwarding.
5. The device of claim 4, the configuration and advertisement module comprising:
the configuration unit is used for configuring the same anycast address and the same anycast address field label for each domain boundary node which mutually forms redundancy protection;
and the notification unit is used for notifying the anycast address containing the anycast group mark and the anycast address field label to the neighbor node in the domain of the anycast address field label through an interior gateway protocol IGP.
6. The apparatus according to claim 4, wherein the packet forwarding module is further specifically configured to forward the packet with the forwarding information to the home domain border node during packet forwarding if it is detected that the forwarding information to the home domain border node is valid.
7. An apparatus for anycast address protection, the apparatus comprising: a processor, and a memory coupled to the processor; the memory having stored thereon a program for anycast address protection executable on the processor, the program for anycast address protection when executed by the processor implementing:
configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node;
after receiving the anycast address and the anycast address field label, respectively creating forwarding information including forwarding information to each domain boundary node, setting the forwarding information of one main domain boundary node as an active state, and setting the forwarding information to a standby domain boundary node as an inactive state, wherein the domain boundary nodes directly connected downstream are used as the main domain boundary nodes, and the domain boundary nodes not directly connected downstream are used as the standby domain boundary nodes;
and during message forwarding, if the forwarding information to the main domain boundary node is detected to be invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
8. A computer storage medium storing a program for anycast address protection, the program for anycast address protection when executed by a processor implementing comprising:
configuring the same anycast address and an anycast address field label for each domain boundary node forming redundancy protection with each other, and announcing the anycast address and the anycast address field label to a neighbor node of the domain boundary node;
after receiving the anycast address and the anycast address field label, respectively creating forwarding information including forwarding information to each domain boundary node, setting the forwarding information of one main domain boundary node as an active state, and setting the forwarding information to a standby domain boundary node as an inactive state, wherein the domain boundary nodes directly connected downstream are used as the main domain boundary nodes, and the domain boundary nodes not directly connected downstream are used as the standby domain boundary nodes;
and during message forwarding, if the forwarding information to the main domain boundary node is detected to be invalid, activating the forwarding information to the standby domain boundary node to be in an active state so as to forward the message by using the forwarding information to the standby domain boundary node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711135592.8A CN109802888B (en) | 2017-11-16 | 2017-11-16 | Method and device based on anycast address protection |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711135592.8A CN109802888B (en) | 2017-11-16 | 2017-11-16 | Method and device based on anycast address protection |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109802888A CN109802888A (en) | 2019-05-24 |
| CN109802888B true CN109802888B (en) | 2021-11-09 |
Family
ID=66555409
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711135592.8A Active CN109802888B (en) | 2017-11-16 | 2017-11-16 | Method and device based on anycast address protection |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109802888B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112702263B (en) * | 2019-10-22 | 2023-12-19 | 华为技术有限公司 | Method and device for forwarding message |
| CN113132229B (en) * | 2019-12-30 | 2022-10-28 | 华为技术有限公司 | Segment identifier determination method and device |
| US11271854B2 (en) * | 2020-02-21 | 2022-03-08 | Ciena Corporation | Resolving label depth and protection in segment routing |
| CN113300949B (en) * | 2020-02-24 | 2022-12-06 | 华为技术有限公司 | Method for forwarding message, method, device and system for releasing routing information |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103825815A (en) * | 2012-11-16 | 2014-05-28 | 中兴通讯股份有限公司 | Method, device and system for carrying out redundant backup among network virtual edge devices |
| CN105119828A (en) * | 2015-09-08 | 2015-12-02 | 常熟理工学院 | Fast wireless network routing achievement method |
| CN106330714A (en) * | 2015-07-02 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for realizing business function chain |
| CN107276784A (en) * | 2016-03-30 | 2017-10-20 | 丛林网络公司 | The fault handling method and PE of movable standby redundancy in EVPN DCI |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9942053B2 (en) * | 2013-09-17 | 2018-04-10 | Cisco Technology, Inc. | Bit indexed explicit replication using internet protocol version 6 |
| US10171338B2 (en) * | 2016-02-08 | 2019-01-01 | Cisco Technology, Inc. | On-demand next-hop resolution |
-
2017
- 2017-11-16 CN CN201711135592.8A patent/CN109802888B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103825815A (en) * | 2012-11-16 | 2014-05-28 | 中兴通讯股份有限公司 | Method, device and system for carrying out redundant backup among network virtual edge devices |
| CN106330714A (en) * | 2015-07-02 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for realizing business function chain |
| CN105119828A (en) * | 2015-09-08 | 2015-12-02 | 常熟理工学院 | Fast wireless network routing achievement method |
| CN107276784A (en) * | 2016-03-30 | 2017-10-20 | 丛林网络公司 | The fault handling method and PE of movable standby redundancy in EVPN DCI |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109802888A (en) | 2019-05-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109802888B (en) | Method and device based on anycast address protection | |
| US9178798B2 (en) | Fast reroute using loop free alternate next hops for multipoint label switched paths | |
| US7551551B2 (en) | Fast reroute (FRR) protection at the edge of a RFC 2547 network | |
| US9525619B2 (en) | Scalable edge node protection using segment routing | |
| US7855953B2 (en) | Method and apparatus for managing forwarding of data in an autonomous system | |
| US9444677B2 (en) | Scalable edge node protection using IPv6 segment routing extension header | |
| US7864669B2 (en) | Method of constructing a backup path in an autonomous system | |
| US7539131B2 (en) | Nexthop fast rerouter for IP and MPLS | |
| WO2019120042A1 (en) | Method and node for transmitting packet in network | |
| TWI499237B (en) | Ldp igp synchronization for broadcast networks | |
| JP5759637B2 (en) | Method for creating label switch path of ring network, related device, and communication system | |
| CN109218197B (en) | Conflict resolution method in segmented routing and router | |
| US20070091794A1 (en) | Method of constructing a backup path in an autonomous system | |
| US7936667B2 (en) | Building backup tunnels for fast reroute in communications networks | |
| CN101120552A (en) | Loop prevention technique for mpls using service labels | |
| JP2014510475A (en) | MPLS fast rerouting using LDP (LDP-FRR) | |
| JP5625121B2 (en) | Prioritizing routing information updates | |
| CN113228572A (en) | Interior Gateway Protocol (IGP) for Segment Routing (SR) proxy Segment Identification (SID) | |
| EP3127276A1 (en) | Apparatus and method for establishing a repair path | |
| EP1946499B1 (en) | Constructing and implementing backup paths in autonomous systems | |
| CN113285876A (en) | Routing method, routing device and computer readable storage medium | |
| CN101374106A (en) | Method for forwarding data packet on MPLS LSP, network node and system | |
| EP2075981A1 (en) | A method and device for avoiding label collision when pbt is controlled by gmpls | |
| WO2009106012A1 (en) | Method, system and device for advertising ds-te information of remote network domain | |
| JP3780987B2 (en) | Route control method and apparatus, route control program, and storage medium storing route control program |
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 |