CN101335689A - Traceroute implementing method and equipment - Google Patents
Traceroute implementing method and equipment Download PDFInfo
- Publication number
- CN101335689A CN101335689A CNA2007101094909A CN200710109490A CN101335689A CN 101335689 A CN101335689 A CN 101335689A CN A2007101094909 A CNA2007101094909 A CN A2007101094909A CN 200710109490 A CN200710109490 A CN 200710109490A CN 101335689 A CN101335689 A CN 101335689A
- Authority
- CN
- China
- Prior art keywords
- node
- response message
- request message
- message
- path
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 60
- 230000002159 abnormal effect Effects 0.000 claims description 17
- 238000001514 detection method Methods 0.000 claims description 8
- 230000005856 abnormality Effects 0.000 claims description 2
- 101100011863 Arabidopsis thaliana ERD15 gene Proteins 0.000 description 24
- 101100338060 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) GTS1 gene Proteins 0.000 description 24
- 101150020450 lsr2 gene Proteins 0.000 description 16
- 101100514575 Arabidopsis thaliana MT1A gene Proteins 0.000 description 14
- 102100024582 Gamma-taxilin Human genes 0.000 description 6
- 101000760789 Homo sapiens Gamma-taxilin Proteins 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000011144 upstream manufacturing Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000003745 diagnosis Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a realizing method for route tracing and equipment. The method concretely comprises the steps that: first, an initial node sends a request message for route tracing; then, after receiving the request message, an intermediate node returns a response message to a node of a higher level and transmits the request message to a node of a lower level until the request message reaches a leaf node; finally, the node of a higher level realizes the operation of route tracing according to the condition of the received response message. The realization proposal for route tracing provided by the embodiment of the invention can effectively reduce the number of response messages received by the initial node such as a root node, etc., solve the problem that the burden of processing the response messages of the initial node such as the root node, etc., in a multicast tree during the process of route tracing, improve the operation deployability of route tracing and can reduce bandwidth resources occupied by the whole tree during the operating process of route tracing.
Description
Technical Field
The present invention relates to the field of network communication technologies, and in particular, to a technical solution for implementing a traceroute operation in a communication network.
Background
With the development of MPLS (multiprotocol label switching) technology, it has been widely used in multicast. In the MPLS-based multicast scheme, a P2MP LSP (point-to-multipoint multi-protocol label switched path) may be established using RSVP-TE (resource reservation protocol-traffic engineering); alternatively, a P2MP LSP may be established using LDP (label distribution protocol).
To ensure the operational reliability of the P2MP LSP as the MPLS forwarding path, it is necessary to timely discover an error of the MPLS forwarding path. MPLS forwarding path errors may be detected and diagnosed using traceroute (traceroute) techniques.
Currently, the error detection and diagnosis process for traceroute for P2MP LSP includes:
(1) a root node of the P2MP LSP sends an MPLS echo request (MPLS reply request) message with TTL (time to live) of 1, and the message contains FEC (equivalent forwarding class) information corresponding to the P2MP LSP;
the root node encapsulates the MPLS echo request message into an MPLS packet corresponding to the FEC, and sends the MPLS packet, where the transport path of the encapsulated MPLS packet is the same as that of the MPLS multicast data packet.
(2) After receiving the MPLS echo request message, the downstream node carries out corresponding processing locally because the TTL value is 1, and sends an MPLS echo response message to the root node;
(3) after receiving each MPLS echo response message which should be received, the root node continues to send MPLS echo request messages with TTL of 2, the corresponding downstream nodes repeat the processing process after receiving the message, and so on, the TTL is added with 1 when the root node sends the MPLS echo request messages in each turn until receiving the MPLS echo response messages or the MPLSecho response messages replied by all the leaf nodes and overtime (namely, not receiving the returned MPLS echo response messages in the preset time);
(4) and the root node performs topology discovery and fault location operation according to the received MPLS echo response message.
It can be seen that, in the above processing procedure, when topology discovery or fault location is performed on the entire P2MP LSP tree from the root node, the root node needs to receive a large number of MPLS echo response messages, which will cause huge processing pressure to the root node, and therefore, a large bandwidth resource needs to be occupied in the process of routing tracing.
In order to solve the above problems to some extent, another implementation scheme of a trace route for topology discovery and fault location is provided in the prior art, where a corresponding processing procedure in the scheme includes:
(1) a root node sends an MPLS echo request message with TTL being N (N is a natural number more than or equal to 1), and the message contains a target leaf node list;
(2) when receiving the MPLS echo request message, the intermediate node checks whether the intermediate node is on a multicast forwarding path reaching a certain leaf node in the target leaf node list, if so, the intermediate node sends an MPLS echo response message to a root node, otherwise, the intermediate node does not respond to the MPLS echo response message to the root node;
in the step, because the response message is sent to the root node only by partial nodes which can reach a certain target leaf node, the number of the response messages received by the root node is reduced;
(3) and the root node performs topology discovery and fault location operation according to the received MPLS echo response message.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
although the processing scheme can reduce the number of response messages received by the root node, the processing scheme is only suitable for the P2MP TE LSP of which the intermediate node can acquire the topological structure of the whole tree, and for the P2MP LDP LSP of which the intermediate node cannot acquire the topological structure of the whole tree, the intermediate node cannot judge whether the intermediate node reaches a multicast forwarding path where a certain target node is located, so that the scheme cannot be applied to realize the operation of tracing the route;
in addition, in this scheme, the root node still receives a large number of response messages, resulting in a large bandwidth occupation of the traceroute process.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for implementing a traceroute, so as to further reduce the number of response messages received by a root node and reduce the bandwidth occupied in the traceroute process.
The embodiment of the invention provides a method for realizing trace routing, which comprises the following steps:
the initial node sends a request message of tracing the route;
after receiving the request message, the intermediate node returns a response message to the previous-level node and processes and forwards the request message to the next-level node until the request message reaches a leaf node;
and the upper-level node realizes the operation of tracking the route according to the condition of receiving the response message.
An embodiment of the present invention provides a node device, including:
the message receiving unit is used for receiving a request message sent by a previous-level node and a response message sent by a next-level node;
the message receiving unit is used for receiving the request message sent by the first node and sending the request message to the second node;
and the trace routing operation unit is used for realizing the trace routing operation according to the condition that the message receiving unit receives the response message.
An embodiment of the present invention provides a node device, including:
a request message sending unit, configured to send a request message to a next-stage node;
a response message receiving unit, configured to receive a response message sent by a next-stage node or an intermediate node or a leaf node that determines that a path is abnormal;
and the trace routing operation unit is used for realizing the trace routing operation according to the condition that the response message receiving unit receives the response message.
The embodiment of the invention provides a method for realizing trace routing, which is used for carrying out the operation of trace routing on a tree comprising a starting node, a middle node and a leaf node, and comprises the following steps:
the initial node sends a request message of tracing the route;
after receiving the request message, the intermediate node adds the node information to the request message and continues to forward the request message until the request message reaches a leaf node;
the leaf node directly returns a response message to the initial node according to the received request message, wherein the response message carries topology information of the whole forwarding path from the initial node to the leaf node;
and the starting node realizes the operation of tracking the route according to the received topology information carried in the response message directly returned by the leaf node.
It can be seen from the technical solutions provided in the embodiments of the present invention that, in the implementation solution for performing traceroute provided in the embodiments of the present invention, the number of response messages received by the start node can be effectively reduced, the problem of excessive burden of the start node of the multicast tree in processing the response messages in the traceroute process is solved, the deployability of the traceroute operation is improved, and bandwidth resources occupied in the traceroute operation process for the whole tree can be reduced.
Drawings
FIG. 1 is a schematic diagram of a process provided by an embodiment of the present invention;
FIG. 2 is a diagram illustrating a first application scenario of an embodiment of the present invention;
FIG. 3 is a diagram illustrating a second application scenario according to an embodiment of the present invention;
fig. 4 is a first schematic structural diagram of a node device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a node device according to an embodiment of the present invention.
Detailed Description
The embodiment of the present invention is used for performing a traceroute operation on a tree including a start node (which may be a root node of the tree or an intermediate node of the tree, etc.), an intermediate node, and a leaf node, where the tree may be a P2MP LSP tree based on MPLS, or may also be a tree based on another protocol.
The implementation scheme that can be specifically adopted in the trace routing operation process provided by the embodiment of the invention comprises the following steps:
(1) the initial node sends a request message of tracing the route;
for example, in the P2MP LSP tree, in the processing process, in order to enable the next node to process the received request packet, the TTL value in the request packet may be set to 1;
(2) after receiving the request message, the intermediate node returns a response message to the previous-level node and processes and forwards the request message to the next-level node until the request message reaches a leaf node; in addition, after receiving the request message, the intermediate node can also forward the request message to the next-level node first and then return a response message to the previous-level node;
in the processing procedure, the response message may include, but is not limited to: a response message for notifying that the path is normal or a response message for notifying that the path is wrong;
in the processing procedure, the specifically adopted operation for processing the request packet may specifically include, but is not limited to: modifying the source address of the request message into the node; or modifying the source address of the request message into the node, and adding the node information into the request message.
(3) The upper-level node realizes the operation of tracking the route according to the condition of receiving the response message;
the treatment process may specifically be: the node judges whether a response message returned by the next-level node is received, if the response message for announcing the path is normal is received, the forwarding path between the node and the next-level node is determined to be normal, if the response message for announcing the path error is received or the response message is not received, the forwarding path between the node and the next-level node is determined to be abnormal, and the initial node is directly informed of the abnormality.
In the embodiment of the present invention, in order to enable the starting node of the multicast tree to collect the topology information of the whole forwarding path, after the leaf node receives the request packet, the topology information of the whole forwarding path from the starting node to the leaf node, which is obtained by the leaf node, can be sent to the starting node through the response packet; or, the leaf node may also judge whether an indication for sending a response packet to the start node is set in the request packet, if so, send the topology information of the whole forwarding path from the start node to the leaf node to the start node through the response packet, otherwise, not send the topology information.
The embodiment of the present invention further provides another implementation scheme for trace routing, which is used to perform a trace routing operation of collecting topology information on a tree including a start node (for example, a root node or an intermediate node of the tree), an intermediate node, and a leaf node, so that the root node or the intermediate node of the tree, which is used as the start node, can collect corresponding topology information, and the implementation scheme specifically includes: firstly, an initial node sends a request message for tracing a route, and after an intermediate node receives the request message, the intermediate node adds the node information into the request message and sets TTL to be 1, and then continuously forwards the request message until the request message reaches a leaf node; then, the leaf node directly returns a response message to the initial node according to the received request message, wherein the response message carries topology information of the whole forwarding path from the initial node to the leaf node; finally, at the start node, it can implement the operation of tracing the route according to the received topology information carried in the response message directly returned by the leaf node, and complete the operation of collecting the topology information.
It can be seen that, if the implementation schemes of the embodiments of the present invention are applied to a P2MPLS tree based on MPLS, the starting node may not be impacted by the MPLS echo response message any more in the process of finding the topology of the whole MPLS P2MP LSP and performing the trace routing operation for locating a fault, that is, the number of MPLS echo response messages received by the starting node does not exceed the number of nodes downstream of the starting node.
For the purpose of facilitating an understanding of the embodiments of the present invention, a detailed description will be given below of specific implementations of the embodiments of the present invention with reference to the accompanying drawings.
The implementation process of traceroute for MPLS P2MP LSP provided in the embodiment of the present invention is shown in fig. 1, and may specifically include:
step 1, a root node sends an MPLS echo request message with TTL of 1 to a downstream node;
after receiving the MPLS echo response message, the MPLS echo response message does not send an MPLSecho req uest message with TTL of 2;
the MPLS echo request packet sent by the root node reaches the leaf node after being processed by one or more downstream nodes, and each downstream node needs to perform substantially the same processing on the MPLS echo request packet, and the processing of the downstream node will be described below:
the upstream node may be a root node, or may also be an intermediate node or a Bud LSR (which is a label switch router of a leaf node and an intermediate node); if the downstream node receives the MPLS echo request message sent by the root node, the corresponding upstream node is the root node, otherwise, the corresponding upstream node is an intermediate node;
in this step, the corresponding processing may mainly include: setting TTL in the message to be 1, modifying the message source address to be the node, adding the node into the message and the like;
similarly, after receiving the MPLS echo response message, the downstream node does not send an MPLS echo request message with TTL of 2;
the method specifically comprises the following steps: if the downstream node does not receive the MPLS echo response message or receives the MPLS echo response message announcing the error, the downstream node determines that the forwarding path between the two nodes has the fault and directly sends an error announcement message to the root node so as to announce the fault reason and position to the root node.
In the above processing procedure, when the downstream node is a leaf node, the MPLSecho request message is not sent any more. After receiving the MPLS echo request message, the leaf node performs corresponding processing according to whether the leaf node set when the root node performs traceroute responds to the message option, which may specifically be: if a response indication (namely an indication for sending a response message to the root node) is set, the leaf node copies the content of the MPLS echo request message to an MPLS echo response message and then sends the MPLS echo response message back to the root node, so that the root node can obtain various information from the messages received by each leaf node, for example, the topological structure information of the whole forwarding path from the root node to the leaf node, the information of whether the leaf node exists or not, and the like; otherwise, namely the root node sets the non-response message, the leaf node does not need to send the topology information to the root node.
When a certain node is a bus LSR, the specific operation of the node is basically the same as that of the intermediate LSR, and the only difference is that the bus LSR needs to set the address as the label of the bus LSR when adding itself into the MPLS echo request message. The root node may know that it is a Bud LSR when it is processing topology information.
After the above processing procedure, the root node can implement the operation of tracing the route according to the content in the message received by itself, for example, collecting the topology structure of the tree, judging the fault location, etc.
The following describes an implementation process of a specific application example of the embodiment of the present invention.
Example one
In this embodiment, a process of collecting topology information of the entire MPLS P2MP LSP by tracing the route is provided, and the topology structure of the entire MPLS P2MP LSP tree is shown in fig. 2. In fig. 2, the MPLS P2MP LSP includes: root node Root, intermediate node LSR1, intermediate node LSR2, leaf node LSR3, leaf node LSR4, and leaf node LSR 5.
Referring to fig. 2, the corresponding process for collecting the P2MP LSP topology information specifically includes the following steps:
step 1, a Root node sends MPLS echo request information with TTL value of 1 to downstream nodes LSR1 and LSR 2;
the Root node sets a flag of a leaf node response message in the MPLS echo request message, and the leaf node needs to respond to the Root node with the message to transmit information of each node.
the Root node receives MPLS echo response messages from an LSR1 node and an LSR2 node respectively, and does not send the MPLS echo request message with the TTL value of 2;
Wherein the processing comprises: the TTL in the message is set to be 1, the message source address is modified to be the node, the local node is added into the message, and the like, and then the LSR1 node and the LSR2 node send the processed message to the respective downstream nodes LSR3, LSR4 and LSR 5.
when receiving the MPLS echo response messages from LSR3, LSR4 and LSR5 respectively, the LSR1 node and LSR2 node do not send the MPLS echo request message with TTL value of 2;
step 5, the LSR3, the LSR4 and the LSR5 process the received MPLS echo request message and send a response message to the root node;
specifically, since the flag of the leaf node response packet is already set in the MPLS echo request packet in step 1, the MPLS echo request packet needs to be processed in this step, and the corresponding processing may include, but is not limited to: setting TTL to 225, modifying message source address to be the node, adding the node into the message, and the like, and then sending the processed MPLS echo request message to the root node;
and 6, after receiving the MPLS echo request message sent by the leaf node, the Root node can obtain the topology information of the whole MPLS P2MP LSP according to the information in the message.
Example two
In this embodiment, the entire process of diagnosing the MPLS P2MP LSP failure point by tracing the route is provided, and in this embodiment, it is assumed that the MPLS P2MP LSP is already known to be problematic by MPLS P2MP Ping (MPLS point-to-multipoint lookup) or other means.
As shown in fig. 3, MPLS P2MP LSP includes: root node Root, intermediate node LSR1, intermediate node LSR2, leaf node LSR3, leaf node LSR4, and leaf node LSR 5. Referring to fig. 3, the process of diagnosing the MPLS P2MP LSP failure point for the topology of the entire MPLS P2MP LSP tree may specifically include:
step 1, a Root node sends an MPLS echo request message with TTL value of 1 to a downstream node;
the flag of the leaf node reply message is not set in the messages sent to the downstream nodes LSR1 and LSR 2.
when the Root node receives MPLS echo response messages respectively from LSR1 and LSR2, the Root node does not send the MPLS echo request message with TTL value of 2;
wherein, the treatment can include but is not limited to: setting TTL in the message to 1, modifying the message source address to the node, adding the node into the message, and the like, and then sending the processed message to the respective downstream nodes LSR3, LSR4 and LSR5 by the LSR1 node and the LSR2 node.
when receiving MPLS echo messages from LSR3 and LSR5, LSR1 and LSR2 do not send MPLS echo request messages with TTL value of 2;
step 5, LSRs 3 and 5 perform some processing on the received MPLS echo request message, including: and setting TTL to be 1, changing the message source address into the TTL, adding the TTL into the message, and the like. Since LSRs 3 and 5 are leaf nodes, they do not send path information packets to the root node according to the flag bits set in the packets.
In the process of executing the above step 4 and step 5, because a forwarding path from the LSR1 node to the LSR4 node has a problem, the LSR1 node cannot reach the LSR4 node with the MPLS echo request packet sent to the LSR4 node (but the LSR1 node does not know whether the packet reaches the LSR4 node). The LSR4 node does not perform the operations of steps 4 and 5 described above because the LSR4 node does not receive the MPLS echo request packet sent by the LSR1 node. This makes the LSR1 node unable to receive the MPLS echo response message from the egress interface to the LSR4 node for a long time, so that the LSR1 node needs to send the MPLS echo response message to the Root node to report the path error information.
The embodiment of the present invention also provides node devices that can be used as a root node and other start nodes and intermediate nodes, and the following will respectively describe specific implementation structures of the two node devices.
Fig. 4 shows a specific implementation structure of a node device that may be used as an intermediate node, which may specifically include the following processing units:
(1) the message receiving unit is used for receiving a request message sent by a previous-level node and receiving a response message sent by a next-level node;
(2) a request message processing unit, configured to return a response message to the previous-stage node after the message receiving unit receives the request message, and further process and forward the request message to the next-stage node, where the process may be to modify a source address of the request message to be the local node, add information of the local node in the request message, and so on;
(3) a trace route operation unit, configured to implement a trace route operation according to a condition that the message receiving unit receives the response message, where the condition includes a condition that the response message is received and a condition that the response message is not received, and the received response message may be a response message for notifying a path error or a response message for notifying a path normal;
further, the traceroute operation unit may specifically include:
the judging and processing unit is used for judging whether a response message returned by the next-stage node is received or not so as to carry out corresponding path detection operation according to a judgment result;
a path detection unit, configured to obtain a determination result of the determination processing unit, determine that a forwarding path between the node and a next-level node is normal if the determination result is that a response packet for notifying that the path is normal is received, and determine that the forwarding path between the node and the next-level node is abnormal if the determination result is that a response packet for notifying that the path is wrong is received or no response packet is received;
and the exception notification unit is used for directly notifying the exception to the starting node after the path detection unit determines that the forwarding path is abnormal, so that the starting node can know the failure condition of the forwarding path in the tree.
Fig. 5 shows a specific implementation structure of a node device that can be used as a start node, which specifically includes the following processing units:
(1) a request message sending unit, configured to send a request message to a next-stage node, where in order to enable the next-stage node to process the request message, a TTL value in the request message may be set to 1;
(2) a response message receiving unit, configured to receive a response message sent by a next-stage node or an intermediate node or a leaf node that determines that a forwarding path is abnormal;
(3) the trace route operation unit is used for realizing the trace route operation according to the condition that the response message receiving unit receives the response message;
further, the traceroute operation unit may specifically include at least one of the following units:
the full-tree path detection unit is used for judging whether each forwarding path of the whole tree is abnormal according to the condition of a response message returned by the next-level node or the intermediate node for determining that the forwarding path is abnormal, which is received by the response message receiving unit; for example, if an application message returned by a next-level node is not received or a response message for notifying a path error returned by the next-level node is received, it is determined that a forwarding path between the starting node and the next-level node is abnormal; for another example, if a response message returned by the intermediate node that determines that the forwarding path is abnormal is received, it may be determined that the forwarding path indicated in the response message is abnormal, and if a response message returned by the intermediate node that determines that the path is abnormal is not received, it is considered that the forwarding path of each downstream node is normal;
and the topology information collection unit is used for determining the topology information of the whole forwarding path from the starting node to the leaf node according to the information carried in the response message returned by the leaf node received by the response message receiving unit.
In the node device that may be an originating node, an indication information sending unit may be further included, configured to send, to the leaf node, an indication that requires the leaf node to send a response packet to the originating node (the indication may be carried in the request packet and sent to the leaf node), so that the leaf node returns, to the originating node, a response packet that includes topology information of an entire forwarding path from the originating node to the leaf node according to the indication.
In summary, when the traceroute scheme proposed by the embodiment of the present invention is used to find the topology of the multicast tree and perform positioning failure, the whole processing process does not cause the impact of the MPLS echo response message to the start node and the intermediate node such as the root node (that is, the number of MPLS echo response messages received by each node is not greater than the number of the downstream nodes), thereby reducing the burden of the start node and the intermediate node such as the root node and reducing the bandwidth resources occupied in the corresponding processing process.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (12)
1. A method for implementing traceroute is characterized in that the method comprises the following steps:
the initial node sends a request message of tracing the route;
after receiving the request message, the intermediate node returns a response message to the previous-level node and processes and forwards the request message to the next-level node until the request message reaches a leaf node;
and the upper-level node realizes the operation of tracking the route according to the condition of receiving the response message.
2. The method of claim 1, wherein the tree is a point-to-multipoint label switched path P2MP LSP tree based on multiprotocol label switching MPLS.
3. The method of claim 1, wherein the response message comprises: a response message for notifying that the path is normal or a response message for notifying that the path is wrong.
4. The method of claim 1, wherein the step of forwarding the request packet to a next-level node processing comprises:
modifying the source address of the request message into the node, and sending the request message to the next-level node;
or,
and modifying the source address of the request message into the node, adding the node information into the request message, and sending the request message to the next-stage node.
5. The method according to any one of claims 1 to 4, wherein the step of implementing traceroute operation according to the condition of receiving the response message comprises:
the node judges whether a response message returned by the next-level node is received, if the response message for announcing the path is normal is received, the forwarding path between the node and the next-level node is determined to be normal, if the response message for announcing the path error is received or the response message is not received, the forwarding path between the node and the next-level node is determined to be abnormal, and the initial node is directly informed of the abnormality.
6. The method of claim 5, wherein after the leaf node receives the request packet, the method further comprises:
the leaf node sends the obtained topology information of the whole forwarding path from the starting node to the leaf node to the starting node through a response message;
or,
the leaf node judges whether an indication for sending a response message to the initial node is set in the request message, if so, the topology information of the whole forwarding path from the initial node to the leaf node is sent to the initial node through the response message, otherwise, the topology information is not sent.
7. A node apparatus, comprising:
the message receiving unit is used for receiving a request message sent by a previous-level node and a response message sent by a next-level node;
the message receiving unit is used for receiving the request message sent by the first node and sending the request message to the second node;
and the trace routing operation unit is used for realizing the trace routing operation according to the condition that the message receiving unit receives the response message.
8. The apparatus according to claim 7, wherein the traceroute operation unit specifically includes:
the judging and processing unit is used for judging whether a response message returned by the next-stage node is received or not;
a path detection unit, configured to obtain a determination result of the determination processing unit, determine that a forwarding path between the node and a next-level node is normal if the determination result is that a response packet for notifying that the path is normal is received, and determine that the forwarding path between the node and the next-level node is abnormal if the determination result is that a response packet for notifying that the path is wrong is received or no response packet is received;
and the exception notification unit is used for directly notifying the exception to the starting node after the path detection unit determines that the forwarding path is abnormal.
9. A node apparatus, comprising:
a request message sending unit, configured to send a request message to a next-stage node;
a response message receiving unit, configured to receive a response message sent by a next-stage node or an intermediate node or a leaf node that determines that a path is abnormal;
and the trace routing operation unit is used for realizing the trace routing operation according to the condition that the response message receiving unit receives the response message.
10. The apparatus according to claim 9, wherein the traceroute operation unit specifically includes:
the full-tree path detection unit is used for judging whether each forwarding path of the whole tree is abnormal according to the condition of a response message returned by the next-level node or the intermediate node for determining that the forwarding path is abnormal, which is received by the response message receiving unit;
and/or
And the topology information collection unit is used for determining the topology information of the whole forwarding path from the starting node to the leaf node according to the information carried in the response message returned by the leaf node received by the response message receiving unit.
11. The apparatus according to claim 9 or 10, wherein the apparatus further comprises an indication information sending unit, configured to send, to the leaf node, an indication that it is required to send the response packet to the originating node.
12. A traceroute implementation method for performing traceroute operation on a tree including a starting node, an intermediate node and a leaf node, the method comprising:
the initial node sends a request message of tracing the route;
after receiving the request message, the intermediate node adds the node information to the request message and continues to forward the request message until the request message reaches a leaf node;
the leaf node directly returns a response message to the initial node according to the received request message, wherein the response message carries topology information of the whole forwarding path from the initial node to the leaf node;
and the starting node realizes the operation of tracking the route according to the received topology information carried in the response message directly returned by the leaf node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101094909A CN101335689B (en) | 2007-06-26 | 2007-06-26 | Traceroute implementing method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101094909A CN101335689B (en) | 2007-06-26 | 2007-06-26 | Traceroute implementing method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101335689A true CN101335689A (en) | 2008-12-31 |
| CN101335689B CN101335689B (en) | 2011-11-02 |
Family
ID=40198015
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101094909A Expired - Fee Related CN101335689B (en) | 2007-06-26 | 2007-06-26 | Traceroute implementing method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101335689B (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101826976A (en) * | 2009-03-03 | 2010-09-08 | 中兴通讯股份有限公司 | Fault indication method in P2MP (Point 2 to Multi-Point) communication and fault indication device of intermediate node and destination node |
| CN101977149A (en) * | 2010-11-02 | 2011-02-16 | 华为技术有限公司 | Router protocol message tracing method, device and system |
| CN102238079A (en) * | 2011-01-18 | 2011-11-09 | 北京中京创原通信技术有限公司 | Method for implementing route backtracking in IP (Internet Protocol) telecommunication network |
| CN102271084A (en) * | 2011-07-13 | 2011-12-07 | 深圳市极限网络科技有限公司 | Technology for locating communication paths of network host |
| CN101621468B (en) * | 2009-08-14 | 2012-01-04 | 清华大学 | Method for establishing protective tunnel router |
| CN102957573A (en) * | 2011-08-24 | 2013-03-06 | 中兴通讯股份有限公司 | Path detection realizing method and node |
| CN103036787A (en) * | 2011-10-09 | 2013-04-10 | 华为技术有限公司 | Network route convergence processing method and network route convergence processing device |
| CN103166852A (en) * | 2013-03-06 | 2013-06-19 | 杭州华三通信技术有限公司 | Traceroute method for label switched paths (LSP) in multi-protocol label switching (MPLS) network and routing equipment |
| CN103490970A (en) * | 2013-09-23 | 2014-01-01 | 华为技术有限公司 | Detection method, device and system of traffic engineering tunnel |
| CN104335538A (en) * | 2012-04-26 | 2015-02-04 | 惠普发展公司，有限责任合伙企业 | Multicast router topology discovery |
| CN106899597A (en) * | 2017-03-02 | 2017-06-27 | 新华三技术有限公司 | A kind of traceroute process method and apparatus |
| CN106998302A (en) * | 2016-01-26 | 2017-08-01 | 华为技术有限公司 | The distribution method and device of a kind of service traffics |
| CN108347384A (en) * | 2018-01-26 | 2018-07-31 | 乐鑫信息科技（上海）有限公司 | A method of being suitable for transmission packet one-to-many in mesh networks |
| CN108667681A (en) * | 2017-03-27 | 2018-10-16 | 丛林网络公司 | Routing for Multi-path route tracks |
| CN110677335A (en) * | 2018-07-03 | 2020-01-10 | 中国电信股份有限公司 | Path tracking method, system, related device and computer readable storage medium |
| CN110875855A (en) * | 2018-08-30 | 2020-03-10 | 北京华为数字技术有限公司 | Method for detecting network link state and network equipment |
| CN113709043A (en) * | 2021-10-28 | 2021-11-26 | 阿里云计算有限公司 | Path tracking method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100407635C (en) * | 2003-09-04 | 2008-07-30 | 华为技术有限公司 | Method for high effectively searching network equipment address in network |
| CN100409646C (en) * | 2003-10-28 | 2008-08-06 | 武汉烽火网络有限责任公司 | Method and apparatus for implementing different internet protocol data packet forwarding using policy flow |
| CN100370748C (en) * | 2005-01-19 | 2008-02-20 | 华为技术有限公司 | Method of implementing synchronization of topology resource information between bearer networks |
-
2007
- 2007-06-26 CN CN2007101094909A patent/CN101335689B/en not_active Expired - Fee Related
Cited By (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101826976B (en) * | 2009-03-03 | 2014-03-12 | 中兴通讯股份有限公司 | Fault indication method in P2MP (Point 2 to Multi-Point) communication and fault indication device of intermediate node and destination node |
| CN101826976A (en) * | 2009-03-03 | 2010-09-08 | 中兴通讯股份有限公司 | Fault indication method in P2MP (Point 2 to Multi-Point) communication and fault indication device of intermediate node and destination node |
| CN101621468B (en) * | 2009-08-14 | 2012-01-04 | 清华大学 | Method for establishing protective tunnel router |
| CN101977149A (en) * | 2010-11-02 | 2011-02-16 | 华为技术有限公司 | Router protocol message tracing method, device and system |
| CN101977149B (en) * | 2010-11-02 | 2013-06-12 | 华为技术有限公司 | Router protocol message tracing method, device and system |
| CN102238079A (en) * | 2011-01-18 | 2011-11-09 | 北京中京创原通信技术有限公司 | Method for implementing route backtracking in IP (Internet Protocol) telecommunication network |
| CN102238079B (en) * | 2011-01-18 | 2015-07-15 | 蒋林涛 | Method for implementing route backtracking in IP (Internet Protocol) telecommunication network |
| CN102271084A (en) * | 2011-07-13 | 2011-12-07 | 深圳市极限网络科技有限公司 | Technology for locating communication paths of network host |
| CN102957573A (en) * | 2011-08-24 | 2013-03-06 | 中兴通讯股份有限公司 | Path detection realizing method and node |
| CN102957573B (en) * | 2011-08-24 | 2017-05-17 | 中兴通讯股份有限公司 | Path detection realizing method and node |
| CN103036787B (en) * | 2011-10-09 | 2016-09-28 | 华为技术有限公司 | A kind of network routing convergence treating method and apparatus |
| CN103036787A (en) * | 2011-10-09 | 2013-04-10 | 华为技术有限公司 | Network route convergence processing method and network route convergence processing device |
| CN104335538A (en) * | 2012-04-26 | 2015-02-04 | 惠普发展公司，有限责任合伙企业 | Multicast router topology discovery |
| CN104335538B (en) * | 2012-04-26 | 2017-12-12 | 慧与发展有限责任合伙企业 | Multicast router topology discovery |
| US9537750B2 (en) | 2012-04-26 | 2017-01-03 | Hewlett Packard Enterprise Development Lp | Multicast router topology discovery |
| CN103166852B (en) * | 2013-03-06 | 2016-03-09 | 杭州华三通信技术有限公司 | The route tracing method of LSP and routing device in MPLS network |
| CN103166852A (en) * | 2013-03-06 | 2013-06-19 | 杭州华三通信技术有限公司 | Traceroute method for label switched paths (LSP) in multi-protocol label switching (MPLS) network and routing equipment |
| CN103490970B (en) * | 2013-09-23 | 2017-09-05 | 华为技术有限公司 | A kind of detection method of traffic engineering tunnel, apparatus and system |
| CN103490970A (en) * | 2013-09-23 | 2014-01-01 | 华为技术有限公司 | Detection method, device and system of traffic engineering tunnel |
| CN106998302A (en) * | 2016-01-26 | 2017-08-01 | 华为技术有限公司 | The distribution method and device of a kind of service traffics |
| US10735323B2 (en) | 2016-01-26 | 2020-08-04 | Huawei Technologies Co., Ltd. | Service traffic allocation method and apparatus |
| CN106899597A (en) * | 2017-03-02 | 2017-06-27 | 新华三技术有限公司 | A kind of traceroute process method and apparatus |
| CN108667681A (en) * | 2017-03-27 | 2018-10-16 | 丛林网络公司 | Routing for Multi-path route tracks |
| CN108347384A (en) * | 2018-01-26 | 2018-07-31 | 乐鑫信息科技（上海）有限公司 | A method of being suitable for transmission packet one-to-many in mesh networks |
| CN110677335A (en) * | 2018-07-03 | 2020-01-10 | 中国电信股份有限公司 | Path tracking method, system, related device and computer readable storage medium |
| CN110677335B (en) * | 2018-07-03 | 2021-12-07 | 中国电信股份有限公司 | Path tracking method, system, related device and computer readable storage medium |
| CN110875855A (en) * | 2018-08-30 | 2020-03-10 | 北京华为数字技术有限公司 | Method for detecting network link state and network equipment |
| CN113709043A (en) * | 2021-10-28 | 2021-11-26 | 阿里云计算有限公司 | Path tracking method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101335689B (en) | 2011-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101335689B (en) | Traceroute implementing method and equipment | |
| EP2395702B1 (en) | Method and device for processing fault | |
| US8902780B1 (en) | Forwarding detection for point-to-multipoint label switched paths | |
| US8879384B2 (en) | Fast upstream source failure detection | |
| CN101953124B (en) | Constructing repair paths around multiple non-available links in a data communications network | |
| US7336615B1 (en) | Detecting data plane livelines in connections such as label-switched paths | |
| CN101335695B (en) | Head node protection method, apparatus and device for point-to-multipoint label switching path | |
| US20090003223A1 (en) | Discovering configured tunnels between nodes on a path in a data communications network | |
| US9059905B2 (en) | Methods and arrangements in an MPLS-TP network | |
| KR101671657B1 (en) | Method and apparatus for checking connection of bi-directional lsp | |
| WO2008028413A1 (en) | Method and system of mpls multicast node and fault location | |
| CN101193052A (en) | Method and system for sub-network connection protection in multi-protocol label switching | |
| CN102571601A (en) | Method for ensuring bidirectional forwarding detection reliability and label switching path equipment | |
| KR20140117993A (en) | Mpls-tp network and method for link failure trace | |
| US8254271B1 (en) | Point-to-multipoint connectivity verification | |
| CN100563140C (en) | The method of a kind of multicast network system and detection multicast network link defective | |
| CN101192990A (en) | A method and device and system for quick rerouting in MPLS network | |
| CN102013990B (en) | End to end notification method and system for multi-segment pseudowire fault | |
| CN101964743A (en) | Multiprotocol label-switched path APS (Active Protection System) protection and management method, equipment and system | |
| CN109787797B (en) | Link fault detection method, device and system | |
| WO2021143524A1 (en) | Fault detection method, and apparatus | |
| CN101924626A (en) | Protection method and system of mixed subnetworks | |
| CN102271064B (en) | Pseudo wire connectivity failure detection method, device and system | |
| CN108521336A (en) | A kind of method and device for controlling routing networking IP address conflict | |
| Chen et al. | Return Path Specified Label Switched Path (LSP) Ping |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20111102 Termination date: 20160626 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |