CN104852848B - A kind of method and apparatus of data transmission - Google Patents
A kind of method and apparatus of data transmission Download PDFInfo
- Publication number
- CN104852848B CN104852848B CN201510187633.2A CN201510187633A CN104852848B CN 104852848 B CN104852848 B CN 104852848B CN 201510187633 A CN201510187633 A CN 201510187633A CN 104852848 B CN104852848 B CN 104852848B
- Authority
- CN
- China
- Prior art keywords
- tunnel
- address
- destination
- source
- equipment
- 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
- 238000000034 method Methods 0.000 title claims abstract description 41
- 230000005540 biological transmission Effects 0.000 title claims abstract description 9
- 238000010586 diagram Methods 0.000 description 4
- 230000006855 networking Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 1
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a kind of methods and apparatus of data transmission, this method comprises: source device generates FRR routing table, the destination address of the FRR routing table is the IP address of purpose equipment, and next hop address includes main next hop address and tunnel incoming interface;The source device, using the destination address of the data and the destination address of FRR routing table, determines the corresponding FRR routing table of data when needing to send data to purpose equipment;When the corresponding link of main next hop address of FRR routing table does not break down, the source device sends the data to purpose equipment by the main next hop address;When the corresponding link of main next hop address of FRR routing table breaks down, the source device sends the data to purpose equipment by the tunnel incoming interface.In the embodiment of the present invention, the loss of flow is avoided, improves the reliability of network.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and a device for data transmission.
Background
FRR (Fast Reroute) is widely applied to various networking, and is used to solve the problem that signaling protocol convergence is slow after a fault occurs in a high-reliability network, and to ensure that traffic is less lost. The forwarding information recorded in the FRR routing table includes: a destination address and a next hop address. To ensure fast switching of traffic after a network failure, the next-hop address includes a primary next-hop address and a standby next-hop address.
As shown in fig. 1, which is a schematic diagram of FRR networking, a destination address in an FRR routing table maintained on a device a is an IP address of a device D, a primary next-hop address is an IP address of a device B, and a standby next-hop address is an IP address routing of a device E. When the traffic among the device A, the device B, the device C and the device D does not fail, the device A sends data to the device D based on the primary next hop address. When traffic between device a-device B-device C-device D fails, device a sends data to device D based on the standby next hop address.
To implement the above process, the address of the standby next hop needs to be learned in the FRR routing table maintained by the device a, and the address of the standby next hop needs to satisfy the loop-free inequality: distance _ opt (N, D) < Distance _ opt (N, S) + Distance _ opt (S, D). The Distance _ opt (N, D) is a cost value from any device to the destination device on the path where the standby next hop address is located, the Distance _ opt (N, S) is a cost value from the device to the source device, and the Distance _ opt (S, D) is a cost value from the source device to the destination device on the path where the primary next hop address is located. Obviously, in the application scenario shown in fig. 1, the cost value from the device F to the device D (i.e., the destination device) is 20, the cost value from the device F to the device a (i.e., the source device) is 2, and the cost value from the device a to the device D on the path where the primary next-hop address is located is 3, so that the device F on the path where the standby next-hop address (the IP address of the device E) is located does not satisfy the loop-free inequality, the IP address of the device E cannot be used as the standby next-hop address, and the IP address of the device E cannot be learned in the routing table as the standby next-hop address.
In summary, the FRR routing table maintained by the device a cannot learn the address of the standby next hop, and when traffic between the device a, the device B, the device C, and the device D fails, the device a cannot send data to the device D based on the address of the standby next hop, thereby causing traffic loss and reducing the reliability of the network.
Disclosure of Invention
The embodiment of the invention provides a data transmission method, which comprises the following steps:
the method comprises the steps that source equipment generates a fast reroute (FRR) routing table, the destination address of the FRR routing table is the IP address of destination equipment, and a next hop address comprises a main next hop address and a tunnel access interface;
when the source equipment needs to send data to destination equipment, determining an FRR routing table corresponding to the data by using a destination address of the data and a destination address of the FRR routing table;
when the link corresponding to the main next hop address of the determined FRR routing table does not fail, the source equipment sends the data to the destination equipment through the main next hop address;
and when the link corresponding to the main next hop address of the determined FRR routing table fails, the source equipment sends the data to the destination equipment through the tunnel entry interface.
The process of the source device generating the FRR routing table whose next hop address includes the main next hop address and the tunnel ingress interface specifically includes:
the source equipment records the IP address and the main next hop address of the destination equipment in an FRR routing table;
if the backup next hop address cannot be learned in the FRR routing table, the source device calculates a backup path between the source device and the destination device after eliminating a main path between the source device and the destination device corresponding to the main next hop address, and obtains address information of each device on the backup path;
and the source equipment generates a tunnel between the source equipment and the destination equipment by utilizing the address information of each equipment, and records a tunnel entry interface of the tunnel in the FRR routing table.
The process of the source device generating a tunnel between the source device and the destination device by using the address information of each device specifically includes:
the source device establishes an IP tunnel between the source device and the destination device by using the backup path, and sends an Internet control message protocol ICMP request message to the destination device through the IP tunnel, wherein the ICMP request message carries a strict source IP route routing option and a recording path option, and the strict source IP route routing option sequentially records address information of each device on the backup path between the source device and the destination device; the source device receives an ICMP response message from the destination device, the ICMP response message sent by the destination device carries a strict source IP route routing option and a recording path option, and the strict source IP route routing option records address information recorded in the recording path option of the ICMP request message; if the address information recorded in the recording path option of the ICMP response message received by the source device is the same as the address information of each device on the backup path between the source device and the destination device, which is calculated by the source device, the source device UP the IP tunnel; if the ICMP response message is not received within the preset time or the address information recorded in the recording path option of the ICMP response message received by the source equipment is different from the address information of each equipment on the backup path between the source equipment and the destination equipment calculated by the source equipment, the source equipment DOWN the IP tunnel;
or, the source device generates a TE tunnel between the source device and the destination device by using the address information of each device as a constraint condition of a traffic engineering TE tunnel.
The process of sending the data to the destination device by the source device through the tunnel entry interface specifically includes: the source equipment inquires an IP tunnel corresponding to the tunnel entrance interface, encapsulates the data by using the IP tunnel, and sends the encapsulated data to the destination equipment through the tunnel entrance interface; or the source device queries a TE tunnel corresponding to the tunnel entry interface, encapsulates the data by using the TE tunnel, and sends the encapsulated data to the destination device through the tunnel entry interface.
The method further comprises: and when the source equipment records a new main next hop address in the FRR routing table, the source equipment sends data to the destination equipment through the new main next hop address, and deletes the tunnel entry interface from the FRR routing table.
An embodiment of the present invention provides a source device, where the source device specifically includes:
the system comprises a generating module, a forwarding module and a forwarding module, wherein the generating module is used for generating an FRR (fast reroute) routing table, a destination address of the FRR routing table is an IP (Internet protocol) address of destination equipment, and a next hop address comprises a main next hop address and a tunnel access interface;
the device comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining an FRR routing table corresponding to data by using a destination address of the data and a destination address of the FRR routing table when the data needs to be sent to destination equipment;
a sending module, configured to send the data to a destination device through a primary next hop address when a link corresponding to the determined primary next hop address of the FRR routing table fails;
and when the link corresponding to the main next hop address of the FRR routing table is determined to be in failure, sending the data to the destination equipment through the tunnel access interface.
The generating module is specifically configured to record an IP address and a primary next hop address of the destination device in the FRR routing table; if the FRR routing table can not learn the standby next hop address, after the main path between the source equipment and the destination equipment corresponding to the main next hop address is eliminated, calculating a backup path between the source equipment and the destination equipment, and obtaining address information of each equipment on the backup path; and generating a tunnel between the source equipment and the destination equipment by using the address information of each equipment, and recording a tunnel entry interface of the tunnel in the FRR routing table.
The generating module is further configured to, in a process of generating a tunnel between the source device and the destination device by using address information of each device, establish an IP tunnel between the source device and the destination device by using the backup path, and send an Internet control message protocol ICMP request message to the destination device through the IP tunnel, where the ICMP request message carries a strict source IP routing option and a recording path option, and address information of each device on the backup path between the source device and the destination device is sequentially recorded in the strict source IP routing option; receiving an ICMP response message from the destination device, wherein the ICMP response message sent by the destination device carries a strict source IP route selection option and a recording path option, and the strict source IP route selection option records address information recorded in the recording path option of the ICMP request message; if the address information recorded in the recording path option of the received ICMP response message is the same as the address information of each device on the backup path between the source device and the destination device, the IP tunnel is UP; if the ICMP response message is not received within the preset time or the address information recorded in the recording path option of the received ICMP response message is different from the calculated address information of each device on the backup path between the source device and the target device, the IP tunnel is DOWN; or, the address information of each device is used as a constraint condition of a traffic engineering TE tunnel, and a TE tunnel between the source device and the destination device is generated.
The sending module is specifically configured to, in a process of sending the data to the destination device through the tunnel entry interface, query an IP tunnel corresponding to the tunnel entry interface, encapsulate the data using the IP tunnel, and send the encapsulated data to the destination device through the tunnel entry interface; or inquiring a TE tunnel corresponding to the tunnel entry interface, encapsulating the data by utilizing the TE tunnel, and sending the encapsulated data to the target equipment through the tunnel entry interface.
The sending module is further configured to send data to the destination device through the new primary next hop address when the new primary next hop address is recorded in the FRR routing table, and delete the tunnel ingress interface from the FRR routing table.
Based on the technical scheme, in the embodiment of the invention, when the source device cannot learn the standby next hop address in the FRR routing table, the tunnel access interface is recorded in the FRR routing table, so that when the link corresponding to the main next hop address fails, data is sent to the destination device through the tunnel access interface to protect the main next hop address, thereby avoiding loss of flow and improving reliability of the network.
Drawings
FIG. 1 is a schematic networking diagram of an FRR;
fig. 2 is a flowchart illustrating a method for data transmission according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a source device according to an embodiment of the present invention.
Detailed Description
In view of the problems in the prior art, the embodiments of the present invention provide a method for data transmission, which is applied in an FRR network including a source device and a destination device. Fig. 1 is a schematic view of an application scenario of the embodiment of the present invention, where a source device is a device a and a destination device is a device D. In the application scenario, as shown in fig. 2, the data transmission method may specifically include the following steps:
in step 201, the source device generates an FRR routing table. The destination address of the FRR routing table is the IP address of the destination device, and the next hop address includes a main next hop address and a tunnel entry interface.
In this embodiment of the present invention, the process of generating, by the source device, the FRR routing table whose next hop address includes the main next hop address and the tunnel ingress interface may specifically include, but is not limited to, the following manners: the source device records the IP address of the destination device and the primary next hop address in the FRR routing table. Further, if the backup next hop address cannot be learned in the FRR routing table, the source device calculates a backup path between the source device and the destination device after excluding the main path between the source device and the destination device corresponding to the main next hop address, and obtains address information of each device on the backup path. The source device generates a tunnel between the source device and the destination device by using the address information of each device, and records the tunnel entry interface of the tunnel in the FRR routing table.
As shown in fig. 1, for the FRR routing table of device D, device a records the destination address as the IP address of device D in the FRR routing table, and the primary next-hop address is the IP address of device B. Since the IP address of the device E does not satisfy the loop-free inequality as the alternate next hop address, the alternate next hop address cannot be learned in the FRR routing table. In this case, after the device a excludes the main path (i.e., path device a-device B-device C-device D) between the device a and the device D corresponding to the main next hop address, the device a calculates the backup path (i.e., path device a-device E-device F-device D) between the device a and the device D, and obtains address information of each device on the backup path, that is, the IP address (ingress interface IP address) of the device E, the IP address (ingress interface IP address) of the device F, and the IP address (ingress interface IP address) of the device D.
In the process of excluding the primary Path between the device a and the device D corresponding to the primary next hop address and calculating the backup Path between the device a and the device D, the device a may calculate the backup Path between the device a and the device D (i.e., Path device a-device E-device F-device D) through a PCE (Path Computation Element) technique. Further, after obtaining the backup path based on the PCE technology, the device a may obtain address information of each device on the backup path.
In this embodiment of the present invention, the tunnel between the source device and the destination device may specifically include, but is not limited to, an IP tunnel or a TE (Traffic Engineering) tunnel, and the process of the source device generating the tunnel between the source device and the destination device by using address information of each device specifically includes, but is not limited to:
in the first case, a source device establishes an IP tunnel between the source device and a destination device by using a backup path, and sends an ICMP (Internet Control Message Protocol) request Message to the destination device through the IP tunnel, where the ICMP request Message carries a strict source IP route selection item and a record path selection item, and address information of each device on the backup path between the source device and the destination device is sequentially recorded in the strict source IP route selection item. The equipment receiving the ICMP request message records the address information of the equipment in the recording path option, and sends the ICMP request message by using the address information recorded in the strict source IP routing option. After receiving the ICMP request message, the destination device sends an ICMP response message carrying a strict source IP route routing option and a recording path option to the source device, wherein the strict source IP route routing option records address information recorded in the recording path option of the ICMP request message. The equipment receiving ICMP response message records the address information of the equipment in the recording path option and sends the ICMP response message by using the address information recorded in the strict source IP routing option. The source device receives an ICMP response message from the destination device, the ICMP response message sent by the destination device carries a strict source IP route routing option and a recording path option, and address information recorded in the recording path option of the ICMP request message is recorded in the strict source IP route routing option. If the address information recorded in the recording path option of the ICMP response message received by the source device is the same as the address information of each device on the backup path between the source device and the destination device calculated by the source device, the source device UP (normal) the IP tunnel. If the address information recorded in the recording path option of the ICMP response message received by the source device or the ICMP response message not received within the preset time is different from the address information of each device on the backup path between the source device and the destination device calculated by the source device, the source device will DOWN the IP tunnel.
As shown in fig. 1, device a establishes an IP tunnel between device a and device D, the tunnel name of which is IP _ FRR _ Bypass _ tunnel. The device a sends an ICMP request message to the device D through the IP tunnel, where the ICMP request message carries a strict source IP routing option and a recording path option, and the strict source IP routing option sequentially records address information of each device on a backup path between the device a and the device D, that is, an IP address of the device E, an IP address of the device F, and an IP address of the device D, and the recording path option records the IP address of the device a. After receiving the ICMP request message, the device E records the IP address of the device E in the recording path option, deletes the IP address of the device E from the strict source IP routing option, and sends the ICMP request message to the device F based on the IP address of the device F recorded in the strict source IP routing option. After receiving the ICMP request message, the device F records the IP address of the device F in the recording path option, deletes the IP address of the device F from the strict source IP routing option, and sends the ICMP request message to the device D based on the IP address of the device D recorded in the strict source IP routing option. After receiving the ICMP request message, the device D records the IP address of the device D in the recording path option, and deletes the IP address of the device D from the strict source IP routing option. Since the device D is a destination device of the ICMP request message, the device D sends an ICMP response message carrying a strict source IP routing option and a recording path option to the device a, where the strict source IP routing option sequentially records an IP address of the device F, an IP address of the device E, and an IP address of the device a (obtained from the recording path option of the ICMP request message), and the recording path option records the IP address of the device D. After receiving the ICMP response message, the device F records the IP address of the device F in the recording path option, deletes the IP address of the device F from the strict source IP routing option, and sends the ICMP response message to the device E based on the IP address of the device E recorded in the strict source IP routing option. After receiving the ICMP response message, the equipment E records the IP address of the equipment E in the recording path option, deletes the IP address of the equipment E from the strict source IP routing option, and sends the ICMP response message to the equipment A based on the IP address of the equipment A recorded in the strict source IP routing option. After receiving the ICMP response message, the device a records that the address information (the IP address of the device D, the IP address of the device F, and the IP address of the device E) in the path option is the same as the address information (the IP address of the device D, the IP address of the device F, and the IP address of the device E) of each device on the backup path between the device a and the device D calculated by the device a, and thus, the IP tunnel is UP.
When the device a sends the ICMP request message to the device D through the IP tunnel, the destination IP address of the ICMP request message may be a specific IP address (e.g. 127.0.0.1), and the specific IP address is used to discard the ICMP request message. Based on this, if the equipment receiving the ICMP request message supports sending the ICMP request message according to the IP address recorded in the strict source IP routing option, the equipment sends the ICMP request message according to the IP address recorded in the strict source IP routing option; if the ICMP request message is not supported to be sent according to the IP address recorded in the strict source IP routing selection option, the ICMP request message is directly discarded because the destination IP address is the specific IP address, so as to prevent the ICMP request message from being transmitted to wrong equipment. Further, if the destination IP address of the ICMP request message is not a specific IP address, when the device receiving the ICMP request message does not support sending the ICMP request message according to the IP address recorded in the strict source IP routing option, the device sends the ICMP request message according to the destination IP address, so that the ICMP request message is transmitted to the wrong device.
When the device a sends an ICMP request message to the device D through the IP tunnel, the device a may send a plurality of ICMP request messages periodically, so as to avoid a problem that a tunnel cannot be established between the device a and the device D due to loss of the ICMP request message.
And in the second case, the source device generates a TE tunnel between the source device and the destination device by using the address information of each device as a constraint condition of the TE tunnel, and the generation manner of the TE tunnel is not described in detail herein.
As shown in fig. 1, the device a generates a TE tunnel between the device a and the device D by using the IP address of the device E, the IP address of the device F, and the IP address of the device D as constraints of the TE tunnel.
Step 202, when the source device needs to send data to the destination device, the source device determines the FRR routing table corresponding to the data by using the destination address of the data and the destination address of the FRR routing table. When the link corresponding to the main next hop address of the determined FRR routing table does not fail, executing step 203; when the link corresponding to the primary next-hop address of the determined FRR routing table fails, step 204 is executed.
In step 203, the source device sends data to the destination device via the primary next hop address.
Step 204, the source device sends data to the destination device through the tunnel entry interface.
As shown in fig. 1, when the device a needs to transmit data to the device D, the device a determines an FRR routing table (i.e., an FRR routing table for the device D) corresponding to the data by using a destination address of the data (i.e., an IP address of the device D) and a destination address of the FRR routing table. When the link corresponding to the primary next hop address of the FRR routing table (i.e., device a-device B-device C-device D) does not fail, device a sends data to device D based on the IP address of device B. When a link corresponding to the primary next hop address of the FRR routing table fails, the device a sends data to the device D based on the tunnel entry interface (i.e., the tunnel entry interface of the IP tunnel or the tunnel entry interface of the TE tunnel, i.e., the interface of the device a connected to the device E).
In the embodiment of the present invention, a process of sending data to a destination device by a source device through a tunnel entry interface specifically includes, but is not limited to, the following modes: and the source equipment inquires the IP tunnel corresponding to the tunnel entry interface, encapsulates the data by using the IP tunnel and sends the encapsulated data to the destination equipment through the tunnel entry interface. Or, the source device queries the TE tunnel corresponding to the tunnel entry interface, encapsulates the data by using the TE tunnel, and sends the encapsulated data to the destination device through the tunnel entry interface.
In the process that the device A encapsulates data by using the IP tunnel, the device A encapsulates a new IP head outside the data, the destination IP address of the IP head is the IP address of the device D, the IP head carries a strict source IP route routing option, and the strict source IP route routing option records the IP address of the device E, the IP address of the device F and the IP address of the device D. The process of encapsulating data by using the TE tunnel of the device a is similar to the existing process of encapsulating data by using the TE tunnel, and is not described herein again.
In the embodiment of the invention, when the source device records the new main next hop address in the FRR routing table, the source device can send data to the destination device through the new main next hop address, and can delete the tunnel entry interface from the FRR routing table.
When the link corresponding to the primary next-hop address of the FRR routing table fails, the device a learns the primary next-hop address of the FRR routing table again, that is, the routing converges again. As shown in fig. 1, device a learns the FRR routing table again that the primary next hop address is device E's IP address. At this time, device a records the new primary next-hop address (IP address of device E) in the FRR routing table, and can send data to device D through the new primary next-hop address (IP address of device E), i.e., the data is seamlessly switched from the tunnel ingress interface to the new primary next-hop address. After the handover is completed, the device a deletes the tunnel ingress interface from the FRR routing table. Further, when a new main next hop address is learned, the device a recalculates the standby next hop address, and records the standby next hop address in the FRR routing table after the calculation is successful.
Based on the technical scheme, in the embodiment of the invention, when the source device cannot learn the standby next hop address in the FRR routing table, the tunnel access interface is recorded in the FRR routing table, so that when the link corresponding to the main next hop address fails, data is sent to the destination device through the tunnel access interface to protect the main next hop address, thereby avoiding loss of flow and improving reliability of the network.
Based on the same inventive concept as the above method, an embodiment of the present invention further provides a source device, as shown in fig. 3, where the source device specifically includes:
a generating module 11, configured to generate an FRR routing table, where a destination address of the FRR routing table is an IP address of a destination device, and a next hop address includes a main next hop address and a tunnel ingress interface;
a determining module 12, configured to determine, when data needs to be sent to a destination device, an FRR routing table corresponding to the data by using a destination address of the data and a destination address of the FRR routing table;
a sending module 13, configured to send the data to a destination device through a primary next hop address when a link corresponding to the determined primary next hop address of the FRR routing table fails;
and when the link corresponding to the main next hop address of the FRR routing table is determined to be in failure, sending the data to the destination equipment through the tunnel access interface.
The generating module 11 is specifically configured to record an IP address and a main next hop address of a destination device in the FRR routing table; if the FRR routing table can not learn the standby next hop address, after the main path between the source equipment and the destination equipment corresponding to the main next hop address is eliminated, calculating a backup path between the source equipment and the destination equipment, and obtaining address information of each equipment on the backup path; and generating a tunnel between the source equipment and the destination equipment by using the address information of each equipment, and recording a tunnel entry interface of the tunnel in the FRR routing table.
The generating module 11 is further configured to, in a process of generating a tunnel between the source device and the destination device by using address information of each device, establish an IP tunnel between the source device and the destination device by using the backup path, and send an Internet control message protocol ICMP request message to the destination device through the IP tunnel, where the ICMP request message carries a strict source IP routing option and a recording path option, and address information of each device on the backup path between the source device and the destination device is sequentially recorded in the strict source IP routing option; receiving an ICMP response message from the destination device, wherein the ICMP response message sent by the destination device carries a strict source IP route selection option and a recording path option, and the strict source IP route selection option records address information recorded in the recording path option of the ICMP request message; if the address information recorded in the recording path option of the received ICMP response message is the same as the address information of each device on the backup path between the source device and the destination device, the IP tunnel is UP; if the ICMP response message is not received within the preset time or the address information recorded in the recording path option of the received ICMP response message is different from the calculated address information of each device on the backup path between the source device and the target device, the IP tunnel is DOWN; or, the address information of each device is used as a constraint condition of a traffic engineering TE tunnel, and a TE tunnel between the source device and the destination device is generated.
The sending module 13 is specifically configured to, in a process of sending the data to the destination device through the tunnel entry interface, query an IP tunnel corresponding to the tunnel entry interface, encapsulate the data by using the IP tunnel, and send the encapsulated data to the destination device through the tunnel entry interface; or inquiring a TE tunnel corresponding to the tunnel entry interface, encapsulating the data by utilizing the TE tunnel, and sending the encapsulated data to the target equipment through the tunnel entry interface.
The sending module 13 is further configured to send data to the destination device through the new primary next hop address when the new primary next hop address is recorded in the FRR routing table, and delete the tunnel ingress interface from the FRR routing table.
The modules of the device can be integrated into a whole or can be separately deployed. The modules can be combined into one module, and can also be further split into a plurality of sub-modules.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention. Those skilled in the art will appreciate that the drawings are merely schematic representations of one preferred embodiment and that the blocks or flow diagrams in the drawings are not necessarily required to practice the present invention. Those skilled in the art will appreciate that the modules in the devices in the embodiments may be distributed in the devices in the embodiments according to the description of the embodiments, and may be correspondingly changed in one or more devices different from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules. The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments. The above disclosure is only for a few specific embodiments of the present invention, but the present invention is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present invention.
Claims (8)
1. A method of data transmission, the method comprising the steps of:
the method comprises the steps that source equipment generates a fast reroute (FRR) routing table, the destination address of the FRR routing table is the IP address of destination equipment, and a next hop address comprises a main next hop address and a tunnel access interface; the tunnel entrance interface is a tunnel entrance interface of a tunnel between the source device and the destination device;
when the source equipment needs to send data to destination equipment, determining an FRR routing table corresponding to the data by using a destination address of the data and a destination address of the FRR routing table;
when the link corresponding to the main next hop address of the determined FRR routing table does not fail, the source equipment sends the data to the destination equipment through the main next hop address;
when the link corresponding to the main next hop address of the determined FRR routing table fails, the source device sends the data to the destination device through the tunnel access interface;
the process of sending the data to the destination device by the source device through the tunnel entry interface specifically includes:
the source equipment inquires an IP tunnel corresponding to the tunnel entrance interface, encapsulates the data by using the IP tunnel, and sends the encapsulated data to the destination equipment through the tunnel entrance interface; or,
and the source equipment inquires a TE tunnel corresponding to the tunnel access interface, encapsulates the data by utilizing the TE tunnel, and sends the encapsulated data to the destination equipment through the tunnel access interface.
2. The method of claim 1, wherein the process of the source device generating the next hop address including the primary next hop address and the FRR routing table of the tunnel-in interface includes:
the source equipment records the IP address and the main next hop address of the destination equipment in an FRR routing table;
if the backup next hop address cannot be learned in the FRR routing table, the source device calculates a backup path between the source device and the destination device after eliminating a main path between the source device and the destination device corresponding to the main next hop address, and obtains address information of each device on the backup path;
and the source equipment generates a tunnel between the source equipment and the destination equipment by utilizing the address information of each equipment, and records a tunnel entry interface of the tunnel in the FRR routing table.
3. The method according to claim 2, wherein the process of the source device generating the tunnel between the source device and the destination device by using the address information of each device specifically includes:
the source device establishes an IP tunnel between the source device and the destination device by using the backup path, and sends an Internet control message protocol ICMP request message to the destination device through the IP tunnel, wherein the ICMP request message carries a strict source IP route routing option and a recording path option, and the strict source IP route routing option sequentially records address information of each device on the backup path between the source device and the destination device; the source device receives an ICMP response message from the destination device, the ICMP response message sent by the destination device carries a strict source IP route routing option and a recording path option, and the strict source IP route routing option records address information recorded in the recording path option of the ICMP request message; if the address information recorded in the recording path option of the ICMP response message received by the source device is the same as the address information of each device on the backup path between the source device and the destination device, which is calculated by the source device, the source device UP the IP tunnel; if the ICMP response message is not received within the preset time or the address information recorded in the recording path option of the ICMP response message received by the source equipment is different from the address information of each equipment on the backup path between the source equipment and the destination equipment calculated by the source equipment, the source equipment DOWN the IP tunnel;
or, the source device generates a TE tunnel between the source device and the destination device by using the address information of each device as a constraint condition of a traffic engineering TE tunnel.
4. The method of claim 1, wherein the method further comprises:
and when the source equipment records a new main next hop address in the FRR routing table, the source equipment sends data to the destination equipment through the new main next hop address, and deletes the tunnel entry interface from the FRR routing table.
5. A source device, characterized in that the source device specifically comprises:
the system comprises a generating module, a forwarding module and a forwarding module, wherein the generating module is used for generating an FRR (fast reroute) routing table, a destination address of the FRR routing table is an IP (Internet protocol) address of destination equipment, and a next hop address comprises a main next hop address and a tunnel access interface; the tunnel entrance interface is a tunnel entrance interface of a tunnel between the source device and the destination device;
the device comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining an FRR routing table corresponding to data by using a destination address of the data and a destination address of the FRR routing table when the data needs to be sent to destination equipment;
a sending module, configured to send the data to a destination device through a primary next hop address when a link corresponding to the determined primary next hop address of the FRR routing table fails;
when the link corresponding to the main next hop address of the FRR routing table is determined to be in failure, the data is sent to the destination equipment through the tunnel access interface;
the sending module is specifically configured to, in a process of sending the data to the destination device through the tunnel entry interface, query an IP tunnel corresponding to the tunnel entry interface, encapsulate the data using the IP tunnel, and send the encapsulated data to the destination device through the tunnel entry interface; or inquiring a TE tunnel corresponding to the tunnel entry interface, encapsulating the data by utilizing the TE tunnel, and sending the encapsulated data to the target equipment through the tunnel entry interface.
6. The apparatus of claim 5,
the generating module is specifically configured to record an IP address and a primary next hop address of the destination device in the FRR routing table; if the FRR routing table can not learn the standby next hop address, after the main path between the source equipment and the destination equipment corresponding to the main next hop address is eliminated, calculating a backup path between the source equipment and the destination equipment, and obtaining address information of each equipment on the backup path; and generating a tunnel between the source equipment and the destination equipment by using the address information of each equipment, and recording a tunnel entry interface of the tunnel in the FRR routing table.
7. The apparatus of claim 6,
the generating module is further configured to, in a process of generating a tunnel between the source device and the destination device by using address information of each device, establish an IP tunnel between the source device and the destination device by using the backup path, and send an Internet control message protocol ICMP request message to the destination device through the IP tunnel, where the ICMP request message carries a strict source IP routing option and a recording path option, and address information of each device on the backup path between the source device and the destination device is sequentially recorded in the strict source IP routing option; receiving an ICMP response message from the destination device, wherein the ICMP response message sent by the destination device carries a strict source IP route selection option and a recording path option, and the strict source IP route selection option records address information recorded in the recording path option of the ICMP request message; if the address information recorded in the recording path option of the received ICMP response message is the same as the address information of each device on the backup path between the source device and the destination device, the IP tunnel is UP; if the ICMP response message is not received within the preset time or the address information recorded in the recording path option of the received ICMP response message is different from the calculated address information of each device on the backup path between the source device and the target device, the IP tunnel is DOWN; or, the address information of each device is used as a constraint condition of a traffic engineering TE tunnel, and a TE tunnel between the source device and the destination device is generated.
8. The apparatus of claim 5,
the sending module is further configured to send data to the destination device through the new primary next hop address when the new primary next hop address is recorded in the FRR routing table, and delete the tunnel ingress interface from the FRR routing table.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510187633.2A CN104852848B (en) | 2015-04-20 | 2015-04-20 | A kind of method and apparatus of data transmission |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510187633.2A CN104852848B (en) | 2015-04-20 | 2015-04-20 | A kind of method and apparatus of data transmission |
Publications (2)
Publication Number | Publication Date |
---|---|
CN104852848A CN104852848A (en) | 2015-08-19 |
CN104852848B true CN104852848B (en) | 2019-04-09 |
Family
ID=53852213
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201510187633.2A Active CN104852848B (en) | 2015-04-20 | 2015-04-20 | A kind of method and apparatus of data transmission |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN104852848B (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107864091B (en) * | 2017-10-31 | 2020-04-03 | 新华三技术有限公司 | Link failure processing method and device |
CN113132250B (en) * | 2019-12-31 | 2023-05-05 | 奇安信科技集团股份有限公司 | Data packet transmission method, device, electronic equipment and medium |
US20210273880A1 (en) * | 2020-02-28 | 2021-09-02 | Carrier Corporation | Single node multiple forwarding paths |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101262407A (en) * | 2008-04-14 | 2008-09-10 | 中兴通讯股份有限公司 | A method for virtual router to establish tunnel |
CN101299722A (en) * | 2008-07-02 | 2008-11-05 | 杭州华三通信技术有限公司 | Improved quick rerouting method and network equipment |
CN101572645A (en) * | 2009-06-12 | 2009-11-04 | 杭州华三通信技术有限公司 | Method for establishing tunnel and device thereof |
CN101621444A (en) * | 2008-07-04 | 2010-01-06 | 华为技术有限公司 | Constructing method and equipment of side road tunnel |
CN101651566A (en) * | 2009-09-15 | 2010-02-17 | 清华大学 | Method for solving inter-domain link fault |
CN101815106A (en) * | 2010-04-16 | 2010-08-25 | 杭州华三通信技术有限公司 | Method and equipment for establishing dynamic GRE (Generic Routing Encapsulation) tunnel |
CN102594785A (en) * | 2011-01-14 | 2012-07-18 | 华为技术有限公司 | Internet protocol (IP) security tunnel establishing method and device |
CN105830403A (en) * | 2013-10-11 | 2016-08-03 | 瑞典爱立信有限公司 | High performance LFA path algorithms |
-
2015
- 2015-04-20 CN CN201510187633.2A patent/CN104852848B/en active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101262407A (en) * | 2008-04-14 | 2008-09-10 | 中兴通讯股份有限公司 | A method for virtual router to establish tunnel |
CN101299722A (en) * | 2008-07-02 | 2008-11-05 | 杭州华三通信技术有限公司 | Improved quick rerouting method and network equipment |
CN101621444A (en) * | 2008-07-04 | 2010-01-06 | 华为技术有限公司 | Constructing method and equipment of side road tunnel |
CN101572645A (en) * | 2009-06-12 | 2009-11-04 | 杭州华三通信技术有限公司 | Method for establishing tunnel and device thereof |
CN101651566A (en) * | 2009-09-15 | 2010-02-17 | 清华大学 | Method for solving inter-domain link fault |
CN101815106A (en) * | 2010-04-16 | 2010-08-25 | 杭州华三通信技术有限公司 | Method and equipment for establishing dynamic GRE (Generic Routing Encapsulation) tunnel |
CN102594785A (en) * | 2011-01-14 | 2012-07-18 | 华为技术有限公司 | Internet protocol (IP) security tunnel establishing method and device |
CN105830403A (en) * | 2013-10-11 | 2016-08-03 | 瑞典爱立信有限公司 | High performance LFA path algorithms |
Non-Patent Citations (2)
Title |
---|
"Remote Loop-Free Alternate Fast Re-Route draft-ietf-rtgwg-remote-lfa-10";S.Bryant.et;《Network Working Group Internet-Draft Intended status:Standards Track》;20150106;第3章 |
"基于rLFA技术的性能优化及重路由选择算法研究";王明鸣,孟相如,徐有,崔文岩;《计算机科学》;20150115;48-51页 |
Also Published As
Publication number | Publication date |
---|---|
CN104852848A (en) | 2015-08-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8134917B2 (en) | Automatic protection switching using link-level redundancy supporting multi-protocol label switching | |
US7707307B2 (en) | Method and apparatus for constructing a backup route in a data communications network | |
US10397044B2 (en) | Network function virtualization (“NFV”) based communications network resilience | |
CN107547383A (en) | Path detection method and device | |
CN103888351B (en) | The method and device of multiple sessions is managed in the network based on Multi-path route | |
US20150016245A1 (en) | Method and apparatus for protection switching in packet transport system | |
CN103944828A (en) | Method and equipment for transmitting protocol messages | |
CN103139075B (en) | A kind of message transmitting method and equipment | |
CN102957573A (en) | Path detection realizing method and node | |
CN103188153B (en) | BFD file transmitting method and equipment on a kind of broadcasting network link | |
CN104852848B (en) | A kind of method and apparatus of data transmission | |
CN112367252B (en) | Method and device for realizing disaster recovery backup | |
CN112104557A (en) | Method and device for detecting link | |
CN104702498A (en) | Method and device for reducing the number of optical connections through coordination protection | |
CN102769552A (en) | Method and apparatus for transmitting BFD (bidirectional forwarding detection) message during LSP (label switched path) detection by BFD | |
CN106375212B (en) | A kind of RSVP message treatment method and device | |
US9998807B2 (en) | Method and apparatus for establishing trail network | |
CN107347034B (en) | Link information processing method, device and system | |
US10887207B2 (en) | System and method for determining branch gateway device availability in computer networks | |
EP2573977A1 (en) | Subnet protection method and device for transport multi-protocol label switching (tmpls) network | |
CN115333994B (en) | Method and device for realizing VPN route rapid convergence and electronic equipment | |
US20220094486A1 (en) | Link bit error-based processing method and apparatus | |
CN103023783B (en) | A kind of data transmission method and equipment based on DVPN | |
WO2021093477A1 (en) | Path planning method and device, and data transmission system | |
WO2014205843A1 (en) | Multi-domain network protection method and system, and node |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
CB02 | Change of applicant information | ||
GR01 | Patent grant | ||
GR01 | Patent grant |