CN101325584A - Method for tracing route, MPLS network system and entry node thereof - Google Patents
Method for tracing route, MPLS network system and entry node thereof Download PDFInfo
- Publication number
- CN101325584A CN101325584A CNA2007101067598A CN200710106759A CN101325584A CN 101325584 A CN101325584 A CN 101325584A CN A2007101067598 A CNA2007101067598 A CN A2007101067598A CN 200710106759 A CN200710106759 A CN 200710106759A CN 101325584 A CN101325584 A CN 101325584A
- Authority
- CN
- China
- Prior art keywords
- response message
- node
- information
- message
- mpls network
- 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
Images
Abstract
The present invention provides a routing tracking method used for MPLS network, MPLS network system and entrance nodes thereof. The method includes that: an entrance node initiates routing tracking by transmitting a reply request message; an intermediate node, after receiving a reply request message, forwards the reply request message to all of its directly downstream nodes, and adopts a reply response message to answer the entrance node, wherein the reply response message includes a tag information itself, its directly upstream node information and all directly downstream nodes information; an export node adopts the reply response message to answer the entrance node, wherein the reply response message includes a tag information itself and its directly upstream node information; the entrance node continuously receives the reply response message until receiving the reply response message of all nodes in the MPLS network, or overtime finishes while not receiving the expectant reply response; the entrance node uses the information of the received reply response message to form the tag exchange routing information of the MPLS network.
Description
Technical field
The present invention relates to the communications field, more specifically, relate to a kind of route and follow the tracks of (traceroute) method, a kind of MPLS network system and Ingress node thereof.
Background technology
Transmit difference with traditional based on IP (Internet Protocol, Internet protocol) destination address, MPLS (Multi-Protocol Label Switching, multi protocol label switching protocol) technology is transmitted based on the label of regular length.Data message can be assigned with a label according to the message corresponding data flow when entering the MPLS network, this label is encapsulated between the link layer head and IP head of data message with the form of MPLS head, in the MPLS network, only use label to transmit, when data message left the MPLS network, this label was removed from this message.
MPLS adopts OAM (Operation and Maintenance, Operation and Maintenance) mechanism is monitored LSP (Label Switched Path, label switched path) connectedness, detection failure etc., IETF (Internet Engineering Task Force, the Internet engineering duty group) has MPLS Ping and MPLS Traceroute etc. for the OAM mechanism of MPLS exploitation.
Fig. 1 shows the schematic diagram according to the Traceroute of prior art.R1 among the figure, R2, R3 etc. are LSR (Label Switched Router, LSRs.In the MPLS of this example Traceroute process, LSP Ingress node (Ingress) is that R1 initiates MPLS Traceroute, send TTL=1, the MPLS Echo Request message of Seq=1 is to R2, R2 returns MPLS Echo Reply message to R1, distance between Ingress node and the LSR is controlled by the TTL (Time to Live, lifetime) in the MPLS head; Then R1 increase TTL and Seq (Sequence number, sequence number) promptly send TTL=2, and the MPLS Echo Request message of Seq=2 is to R4, and R4 returns MPLS Echo Reply (response) message to R1; Then R1 increase TTL and Seq promptly send TTL=3, the MPLS Echo Request message of Seq=3 is R5 to the Egress node, R5 returns MPLS Echo Reply message to R1, MPLS Traceroute EO, then R1 obtained at the connective situation of this LSP promptly this LSP datum plane topology for R1-＞R2-＞R4-＞R5 and be communicated with fault-free.
In realizing process of the present invention, the inventor finds that there are the following problems at least in the prior art: many ECMP (Equal Cost Multi-Path is being arranged, the equivalence multipath) under the situation in path, specify corresponding FEC (the FORWARDINGEQUIVALENCE CLASS of LSP by traceroute, forwarding equivalence class) various objectives address, though might cover all paths on the statistics, can not guarantee to travel through all ECMP nodes.If LSP is by LDP (the LABEL DISTRIBUTIONPROTOCOL that supports label aggregation, label distribution protocol) sets up, and no matter be on IP route or LSP, all to have the ECMP topology, then this moment, MPLS Traceroute only can select a paths to carry out detection of connectivity at random, can not cover all ECMP paths.Therefore, traceroute method shown in Figure 1 can't travel through all paths at Ingress node, can't obtain the ECMP path topology, says nothing of disposable the acquisition.If need obtain network topology and detect connective by MPLS Traceroute at Ingress node in this case, then can only repeated multiple times use MPLS Traceroute to attempt to obtain different paths as much as possible, and can not cover all paths fully by a MPLS Traceroute operation, cause this scheme efficient lower.
Summary of the invention
The embodiment of the invention aims to provide a kind of method for tracing route, a kind of MPLS network and Ingress node thereof, when with realization the MPLS network system with ECMP being followed the tracks of, can cover all paths.
One embodiment of the present of invention provide a kind of method for tracing route of the MPLS of being used for network, comprising: the Ingress node of MPLS network is followed the tracks of to initiate route by sending the acknowledges requests message; The intermediate node of MPLS network is after receiving the acknowledges requests message, all direct downstream nodes are transmitted the acknowledges requests message to it, and adopt the response message to respond Ingress node, comprise label information, its direct upstream node information and all the direct downstream node information of oneself in the response message; The Egress node of MPLS network adopts the response message to respond Ingress node after receiving the acknowledges requests message, comprises label information and its direct upstream node information of oneself in the response message; Ingress node constantly receives the response message, and the response message of all nodes in having received the MPLS network perhaps can not receive the response message of expectation and overtime end; Ingress node uses the information of the response message that receives to form the label switched path information of MPLS network.
Another embodiment of the present invention provides a kind of MPLS network system, comprising: Ingress node, and it comprises initiation module, is used to send the acknowledges requests message and follows the tracks of to initiate route; Receiver module is used for constantly receiving the response message, and the response message of all nodes in having received the MPLS network perhaps can not receive the response message of expectation and overtime end; And analysis module, be used to use the information of the response message of reception to form the label switched path information of MPLS network; Intermediate node, be used for after receiving the acknowledges requests message, all direct downstream nodes are transmitted the acknowledges requests message to it, and adopt the response message to respond Ingress node, comprise label information, its direct upstream node information and all direct downstream node information of intermediate node in the response message; Egress node is used to adopt the response message to respond Ingress node, comprises label information and its direct upstream node information of oneself in the response message.
Another embodiment of the present invention provides the Ingress node in a kind of MPLS network, comprising: initiation module is used to send the acknowledges requests message and follows the tracks of to initiate route; Receiver module is used for constantly receiving the response message, and the response message of all nodes in having received the MPLS network perhaps can not receive the response message of expectation and overtime end; And analysis module, be used to use the information of the response message of reception to form the label switched path information of MPLS network.
By technique scheme, the present invention has realized covering all paths to the Traceroute of MPLS network system with ECMP, and can disposable location path fault.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 shows the schematic diagram according to the Traceroute of prior art;
Fig. 2 shows the flow chart according to the method for tracing route of the embodiment of the invention;
Fig. 3 shows the structure chart of the ECMP TLV (TYPE-LENGTH-VALUE, type-length-value) according to the embodiment of the invention;
Fig. 4 shows the flow chart according to the reception response message of the embodiment of the invention;
Fig. 5 to Fig. 9 shows each state of Traceroute of the MPLS that has ECMP according to an embodiment of the invention;
Figure 10 to Figure 14 shows each state of the trace table in the Traceroute process of Fig. 5 to Fig. 9;
Figure 15 shows the schematic diagram that breaks down in ECMP path according to another embodiment of the present invention;
Figure 16 shows the state of the trace table in the Traceroute process of Figure 15;
Figure 17 shows the block diagram of Ingress node according to an embodiment of the invention.
Embodiment
Below with reference to the accompanying drawings and in conjunction with the embodiments, describe the present invention in detail.
Fig. 2 shows the flow chart according to the method for tracing route of the embodiment of the invention, and it may further comprise the steps:
S10, the Ingress node of MPLS network is followed the tracks of to initiate route by sending MPLS Echo Request message;
S20, the intermediate node of MPLS network is after receiving MPLS Echo Request message, all direct downstream nodes are transmitted MPLS Echo Request message to it, and adopt MPLS Echo Reply message to respond Ingress node, comprise label information, its direct upstream node information and all the direct downstream node information of oneself in the MPLS Echo Reply message;
S30, the Egress node of MPLS network adopt MPLS Echo Reply message to respond Ingress node after receiving MPLS Echo Request message, comprise label information and its direct upstream node information of oneself in MPLS Echo Reply message;
S40, Ingress node constantly receive MPLS Echo Reply message, and the MPLS Echo Reply message of all nodes in having received the MPLS network perhaps can not receive the MPLS Echo Reply message of expectation and overtime end;
S50, Ingress node use the information of the MPLS Echo Reply message that receives to form the LSP information of MPLS network.
Propose on ECMP LSR, to duplicate MPLS Echo Request message in the foregoing description, and in the MPLS Echo Reply message that each node returns, carry direct upstream and all direct downstream node information of this intermediate node, thereby the acquisition network topology has solved the covering fully in MPLS Traceroute path under the ECMP situation.
In addition, prior art is because can't travel through all ECMP paths, if the path failure of ECMP just occurs on the path of not passing by, then this path failure detect less than, so traceroute method shown in Figure 1 differs and detects the ECMP path failure surely, say nothing of the disposable ECMP of detecting path failure.And in the MPLS Echo Reply message that each node returns, carried all direct downstream node information of intermediate node according to the traceroute method of the embodiment of the invention, can disposable location path fault by time-out information, the path failure that has solved prior art detects problem.
Intermediate node can be searched and transmit by duplicating MPLS Echo Request message, obtains its all lower exit label, to know the information of its all direct downstream nodes.
Directly upstream node information can be the IP address of the direct upstream node of intermediate node, the IP address of all direct downstream nodes that all direct downstream node information can be intermediate nodes.
Can in the TLV field of MPLS Echo Reply message, carry label information, its direct upstream node information and all direct downstream node information of intermediate node.
Also can in MPLS Echo Reply message, mark be set, be used for of the support of this MPLSTraceroute method of mark ECMP.This sign can realize by the TLV that expands existing MPLS Echo Reply message.
Fig. 3 shows the structure chart according to the ECMP TLV of the embodiment of the invention, and as shown in the figure, the upstream and downstream address of increase node and upstream node arrive label of this node and the label that this node arrives downstream node in the ECMP TLV of expansion.ECMP after expansion can comprise following field: Upstream number (upstream number) field, Upstream IP Address (IP address, upstream) field, Upstream Label (upper tag) field, DownstreamIP Address (IP address, downstream) field, Downstream Label (downstream label) field, Downstream IP Address Lists (downstream IP address list), DownstreamLabel Lists downstream list of labels etc.Fig. 3 has provided byte number that has exemplified these fields etc.
If Ingress node is received MPLS Echo Reply message, then judge to be the MPLS Echo Reply message of Egress node, not then to continue to receive MPLS Echo Reply message; If the MPLS Echo Reply message of receiving is the MPLS EchoReply message of Egress node, then judged whether to receive the MPLS Echo Reply message of all nodes among the LSP, if then finish this reception; Do not receive MPLS EchoReply message then finish this reception if surpass the scheduled time, and regard as overtime.Ingress node can judge that judgement is overtime by timer is set.
Fig. 4 shows the flow chart according to the reception response message of this embodiment, may further comprise the steps:
Step S402, Ingress initiate the Traceroute order, specify and adopt the ECMP form.
Step S404, Ingress receives MPLS Echo Reply message, if do not receive the MPLS Echo Reply of expectation, then step S410 checks that the MPLS Echo Reply that whether also has expectation is (after Ingress receives MPLS Echo Reply message, because message carries the address in direct downstream, so Ingress has just known the node of the MPLSEcho Reply message that expectation receives), if having, return the MPLS EchoReply that receives expectation, otherwise overtime end.
Step S406 if receive the MPLS Echo Reply of expectation, sees to be the MPLS Echo Reply of Egress, is not then to return the MPLS Echo Reply that receives expectation.
Step S408, if the MPLS Echo Reply of Egress then checks whether traveled through whole LSP, if traveled through then finished, otherwise, return the MPLSEcho Reply that receives expectation.
The processing procedure of the intermediate node of this MPLS network system is, receive MPLSEcho Request message after, the upstream and downstream address of oneself is filled in the ECMP TLV, be placed in the MPLS Echo Reply message and return Ingress.Then, duplicate MPLS EchoRequest message, search and transmit, obtain all lower exit labels, mail to all downstream nodes.
The processing procedure of the Egress of this MPLS network system is, after receiving MPLS EchoRequest message, the address, downstream is made as NULL, then the upstream and downstream address of oneself is filled in the ECMP TLV, be placed in the MPLS Echo Reply message and return Ingress.
According to the Traceroute method that the foregoing description provides, the embodiment of the invention provides a kind of MPLS network system, and it comprises:
Ingress node, being used to send MPLS Echo Request message follows the tracks of to initiate route, constantly receive MPLS Echo Reply message, the MPLS Echo Reply message of all nodes in having received the MPLS network, perhaps can not receive the MPLS Echo Reply message of expectation and overtime end, and use the information of the MPLS Echo Reply message that receives to form the LSP information of MPLS network;
Intermediate node, be used for after receiving MPLS Echo Request message, all direct downstream nodes are transmitted MPLS Echo Request message to it, and adopt MPLS EchoReply message to respond Ingress node, comprise label information, its direct upstream node information and all direct downstream node information of intermediate node in the MPLS Echo Reply message; And
Egress node is used to adopt MPLS Echo Reply message to respond Ingress node, comprises label information and its direct upstream node information of oneself in MPLS Echo Reply message.
Figure 17 shows the block diagram of Ingress node according to an embodiment of the invention.Specifically, Ingress node can comprise:
Wherein, receiver module can comprise:
The 3rd judge module 206 is not received MPLS EchoReply message then is finished this reception if be used for surpassing the scheduled time, and regards as overtime.
Fig. 5 shows the Traceroute state one according to the MPLS with ECMP of the embodiment of the invention, and wherein, LSP sets up, and R1 is Ingress, and R5 is Egress, and R2 is the ECMP node.
Fig. 6 shows the Traceroute state two according to the MPLS with ECMP of the embodiment of the invention, and wherein Ingress sends MPLS Echo Request, and R2 handles.
Ingress sends MPLS Echo Request message, and the trace table is set up in this locality, waits for the MPLS Echo Reply of the R2 of expectation.Receive the R2 node of MPLS Echo Request message, at first send and have the MPLS Echo Reply message of upstream and downstream address information to Ingress, then look into and transmit, going into label is L1, outgoing label L2, L3, duplicate MPLS Echo Request message, respectively label is changed into L2, L3, send out from different ports.After Ingress receives the MPLS Echo Reply of R2 of expectation, upgrade the trace table, at this moment wait for the MPLS Echo Reply of R3, the R4 of expectation.At this moment the table of Ingress as shown in figure 10, after Figure 10 shows the R2 node and returns, the structure of trace table in the Ingress.
Fig. 7 shows the Traceroute state three according to the MPLS with ECMP of the embodiment of the invention, and wherein, intermediate node R3 handles.
The R3 that receives MPLS Echo Request message at first send have the upstream and downstream address information MPLS Echo Reply message to Ingress, then look into and transmit, going into label is L2, outgoing label L4, duplicate MPLS Echo Request message, label is changed into L4, send out from port.After Ingress receives the MPLS Echo Reply of R3 of expectation, upgrade the trace table, at this moment wait for the MPLS Echo Reply of 2 R4 of expectation.At this moment the trace of Ingress table as shown in figure 11, after Figure 11 shows the R3 node and returns, the structure of trace table in the Ingress.
Fig. 8 shows the Traceroute state four according to the MPLS with ECMP of the embodiment of the invention, and wherein, intermediate node R4 handles.
The R4 that receives MPLS Echo Request message at first send have the upstream and downstream address information MPLS Echo Reply message to Ingress.If receiving that first part of MPLS Echo Request (according to checking and verifying of sequence number Seq#) then looks into transmits, duplicate MPLS Echo Request message, label is changed into outlet label L5, send out from port.The MPLS Echo Request that receives subsequently is owing to have identical Seq#, and R4 abandons this message after this request is replied automatically, has not sent out downstream, and promptly R4 only can send out a MPLS Echo Request message downstream.After Ingress receives the MPLS Echo Reply of 2 R4 of expectation, upgrade the trace table, at this moment wait for the MPLS Echo Reply of the R5 of expectation.At this moment the table of Ingress as shown in figure 12, after Figure 12 shows the R4 node and returns, the structure of trace table in the Ingress.
This trace table can be simplified to structure shown in Figure 13, after Figure 13 shows the R4 node and returns, and the structure of the trace table of simplifying in the Ingress.
Fig. 9 shows the Traceroute state five according to the MPLS with ECMP of the embodiment of the invention, and wherein, Egress node R 5 is handled.
The R5 that receives MPLS Echo Request message at first puts NULL to the address, downstream, sends then to have the MPLS Echo Reply message of upstream and downstream address information to Ingress.At this moment the table of Ingress as shown in figure 14, after Figure 14 shows Eress R5 node and returns, the structure of trace table in the Ingress.
Because received the MPLS Echo Reply that contains address, NULL downstream, Ingress knows has Egress to return, traversal trace table, find that all nodes have all returned MPLSEcho Reply, promptly f=1 does not have the MPLS Echo Reply that expects, be that traceroute finishes, do not have fault, and obtained all topological paths of this LSP, see Figure 14.
Figure 15 shows the schematic diagram that breaks down in ECMP path according to another embodiment of the present invention, and wherein, break down in the ECMP path between R3 and the R4.
Because the ECMP between R3 and the R4 breaks down, the MPLS EchoRequest message of R3 can not arrive R4, so R4 has only returned the MPLS Echo Reply message that a upstream node is R2.Ingress after the MPLSEcho Reply of the R4 in the R3 downstream of waiting for expectation is overtime, the trace table that obtains as shown in figure 16, after Figure 16 shows the EgressR5 node and returns, the structure of trace table in the Ingress.
Ingress is by Figure 16, is easy to learn that the upstream is that the R4 of R3 does not return MPLSEcho Reply, and path fails between R3 and the R4 under this situation, also can obtain the path topology of LSP.
By above two examples, can be clearly seen that this invention has solved the problem that all standing of ECMP path and ECMP path failure can't detect under traditional Traceroute.
As can be seen from the above description, the above embodiments of the present invention have realized following technique effect:
1). the present invention uses a disposable topology and the connectivity of obtaining ECMP LSP of traceroute at Ingress node when ECMP LSP fault-free;
2). when the present invention has fault at ECMP LSP, use the disposable fault location of traceroute at Ingress node.
Obviously, those skilled in the art should be understood that, above-mentioned each module of the present invention or each step can realize with the general calculation device, they can concentrate on the single calculation element, perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in the storage device and carry out by calculation element, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.Should be understood that the variation in these concrete enforcements is conspicuous for a person skilled in the art, do not break away from spiritual protection range of the present invention.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (14)
1. a method for tracing route that is used for the MPLS network is characterized in that, comprising:
The Ingress node of described MPLS network is followed the tracks of to initiate route by sending the acknowledges requests message;
The intermediate node of described MPLS network is after receiving the acknowledges requests message, all direct downstream nodes are transmitted the acknowledges requests message to it, and adopt the response message to respond described Ingress node, comprise label information, its direct upstream node information and all the direct downstream node information of oneself in the described response message;
The Egress node of described MPLS network adopts the response message to respond described Ingress node after receiving described acknowledges requests message, comprises label information and its direct upstream node information of oneself in described response message;
Described Ingress node constantly receives the response message, and the response message of all nodes in having received described MPLS network perhaps can not receive the response message of expectation and overtime end;
Described Ingress node uses the information of the response message that receives to form the label switched path information of described MPLS network.
2. method for tracing route according to claim 1 is characterized in that, described intermediate node is searched and transmitted by the duplicate acknowledgement request message, obtains its all lower exit label, to know the information of its all direct downstream nodes.
3. method for tracing route according to claim 1, it is characterized in that, described direct upstream node information comprises the IP address of the direct upstream node of described intermediate node, and described all direct downstream node information comprise the IP address of all direct downstream nodes of described intermediate node.
4. method for tracing route according to claim 1 is characterized in that, carries label information, its direct upstream node information and all direct downstream node information of described intermediate node in the type-length-value field of described response message.
5. method for tracing route according to claim 1, it is characterized in that described Ingress node constantly receives the response message, the response message of all nodes in having received described MPLS network, perhaps can not receive the response message and overtime, specifically comprise:
If described Ingress node is received the response message, then judge to be the response message of Egress node, not then to continue to receive the response message;
If the response message of receiving is the response message of described Egress node, then whether traveled through by checking that all nodes have judged whether to receive the response message of all nodes in the described MPLS network in the described MPLS network, if then finish this reception;
Do not receive the response message of expectation then finish this reception if surpass the scheduled time, and regard as overtime.
6. according to the described method for tracing route of claim 1 to 5, it is characterized in that, also comprise:
In the response message, mark is set, is used to represent that described method for tracing route can be used in the MPLS network with equivalent multipath.
7. method for tracing route according to claim 6 is characterized in that, in the type-length-value field of described response message described mark is set.
8. a MPLS network system is characterized in that, comprising:
Ingress node, it comprises:
Initiation module is used to send the acknowledges requests message and follows the tracks of to initiate route;
Receiver module is used for constantly receiving the response message, and the response message of all nodes in having received described MPLS network perhaps can not receive the response message of expectation and overtime end; And
Analysis module is used to use the information of the response message of reception to form the label switched path information of described MPLS network.；
Intermediate node, be used for after receiving the acknowledges requests message, all direct downstream nodes are transmitted the acknowledges requests message to it, and adopt the response message to respond described Ingress node, comprise label information, its direct upstream node information and all direct downstream node information of described intermediate node in the described response message;
Egress node is used to adopt the response message to respond described Ingress node, comprises label information and its direct upstream node information of oneself in described response message.
9. network system according to claim 8 is characterized in that, described intermediate node is searched and transmitted by the duplicate acknowledgement request message, obtains its all lower exit label, to know its all direct downstream node information.
10. network system according to claim 8, it is characterized in that, described direct upstream node information comprises the IP address of the direct upstream node of described intermediate node, and all direct downstream node information comprise the IP address of all direct downstream nodes of described intermediate node.
11. network system according to claim 8 is characterized in that, carries label information, its direct upstream node information and all direct downstream node information of described intermediate node in the type-length-value field of response message.
12. network system according to claim 8 is characterized in that, described receiver module comprises:
First judge module if be used for receiving the response message, then judges to be the response message of Egress node, is not then to continue to receive the response message;
Second judge module, if the response message that is used for receiving is the response message of described Egress node, then whether traveled through by checking that all nodes have judged whether to receive the response message of all nodes in the described MPLS network in the described MPLS network, if then finish this reception;
The 3rd judge module is not received the response message then is finished this reception if be used for surpassing the scheduled time, and regards as overtime.
13. the Ingress node in the MPLS network is characterized in that, comprising:
Initiation module is used to send the acknowledges requests message and follows the tracks of to initiate route;
Receiver module is used for constantly receiving the response message, and the response message of all nodes in having received described MPLS network perhaps can not receive the response message of expectation and overtime end; And
Analysis module is used to use the information of the response message of reception to form the label switched path information of described MPLS network.
14. Ingress node according to claim 13 is characterized in that, described receiver module comprises:
First judge module if be used for receiving the response message, then judges to be the response message of Egress node, is not then to continue to receive the response message;
Second judge module, if the response message that is used for receiving is the response message of described Egress node, then whether traveled through by checking that all nodes have judged whether to receive the response message of all nodes in the described MPLS network in the described MPLS network, if then finish this reception;
The 3rd judge module is not received the response message then is finished this reception if be used for surpassing the scheduled time, and regards as overtime.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710106759A CN101325584B (en) | 2007-06-15 | 2007-06-15 | Method for tracing route, MPLS network system and entry node thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710106759A CN101325584B (en) | 2007-06-15 | 2007-06-15 | Method for tracing route, MPLS network system and entry node thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101325584A true CN101325584A (en) | 2008-12-17 |
| CN101325584B CN101325584B (en) | 2012-08-29 |
Family
ID=40188913
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710106759A Active CN101325584B (en) | 2007-06-15 | 2007-06-15 | Method for tracing route, MPLS network system and entry node thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101325584B (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101924670A (en) * | 2010-09-25 | 2010-12-22 | 杭州华三通信技术有限公司 | Method and equipment for detecting label switched path (LSP) |
| CN102347850A (en) * | 2010-07-28 | 2012-02-08 | 中兴通讯股份有限公司 | Fault positioning method and system for point 2 multiple point (P2MP) path |
| CN102594582A (en) * | 2011-01-14 | 2012-07-18 | 中兴通讯股份有限公司 | Looping back method and system of message |
| CN102598588A (en) * | 2009-10-15 | 2012-07-18 | 瑞典爱立信有限公司 | Network connection segment monitoring |
| WO2012159316A1 (en) * | 2011-07-06 | 2012-11-29 | 华为技术有限公司 | Method, network device and system for determining equal-cost paths in network |
| WO2013026336A1 (en) * | 2011-08-24 | 2013-02-28 | 中兴通讯股份有限公司 | Method for path detection and node |
| CN103490970A (en) * | 2013-09-23 | 2014-01-01 | 华为技术有限公司 | Detection method, device and system of traffic engineering tunnel |
| WO2015184687A1 (en) * | 2014-06-05 | 2015-12-10 | 中兴通讯股份有限公司 | Packet transmission method, node, path management server and storage medium |
| WO2017050198A1 (en) * | 2015-09-25 | 2017-03-30 | 华为技术有限公司 | Path detection method and device |
| CN107317691A (en) * | 2016-04-26 | 2017-11-03 | 华为技术有限公司 | A kind of Fault Locating Method and equipment |
| WO2018010560A1 (en) * | 2016-07-15 | 2018-01-18 | 中兴通讯股份有限公司 | Method, apparatus, and system for detecting and processing multi-protocol label switching |
| CN108400934A (en) * | 2017-02-08 | 2018-08-14 | 南宁富桂精密工业有限公司 | Software defined network controller, service function catenary system and route tracing method |
| CN109218196A (en) * | 2017-12-13 | 2019-01-15 | 新华三技术有限公司 | A kind of formation gathering method, device, equipment and machine readable storage medium |
| CN109921987A (en) * | 2017-12-13 | 2019-06-21 | 中兴通讯股份有限公司 | A kind of BIER-TE network detecting method, apparatus and system |
| US10498641B2 (en) | 2013-10-14 | 2019-12-03 | Huawei Technologies Co., Ltd. | Forward entry generating method, forward node, and controller |
| CN110677335A (en) * | 2018-07-03 | 2020-01-10 | 中国电信股份有限公司 | Path tracking method, system, related device and computer readable storage medium |
-
2007
- 2007-06-15 CN CN200710106759A patent/CN101325584B/en active Active
Cited By (33)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102598588A (en) * | 2009-10-15 | 2012-07-18 | 瑞典爱立信有限公司 | Network connection segment monitoring |
| CN102598588B (en) * | 2009-10-15 | 2014-12-10 | 瑞典爱立信有限公司 | Network connection segment monitoring |
| CN102347850A (en) * | 2010-07-28 | 2012-02-08 | 中兴通讯股份有限公司 | Fault positioning method and system for point 2 multiple point (P2MP) path |
| CN101924670A (en) * | 2010-09-25 | 2010-12-22 | 杭州华三通信技术有限公司 | Method and equipment for detecting label switched path (LSP) |
| CN102594582A (en) * | 2011-01-14 | 2012-07-18 | 中兴通讯股份有限公司 | Looping back method and system of message |
| WO2012159316A1 (en) * | 2011-07-06 | 2012-11-29 | 华为技术有限公司 | Method, network device and system for determining equal-cost paths in network |
| CN103004149A (en) * | 2011-07-06 | 2013-03-27 | 华为技术有限公司 | Method, network device and system for determining equal-cost paths in network |
| CN103004149B (en) * | 2011-07-06 | 2015-08-19 | 华为技术有限公司 | For the method in certainty equivalents path in a network, network equipment and system |
| CN102957573B (en) * | 2011-08-24 | 2017-05-17 | 中兴通讯股份有限公司 | Path detection realizing method and node |
| WO2013026336A1 (en) * | 2011-08-24 | 2013-02-28 | 中兴通讯股份有限公司 | Method for path detection and node |
| CN102957573A (en) * | 2011-08-24 | 2013-03-06 | 中兴通讯股份有限公司 | Path detection realizing method and node |
| 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 |
| US10498641B2 (en) | 2013-10-14 | 2019-12-03 | Huawei Technologies Co., Ltd. | Forward entry generating method, forward node, and controller |
| WO2015184687A1 (en) * | 2014-06-05 | 2015-12-10 | 中兴通讯股份有限公司 | Packet transmission method, node, path management server and storage medium |
| CN105282028A (en) * | 2014-06-05 | 2016-01-27 | 中兴通讯股份有限公司 | Message transmission method, nodes and path management servers |
| WO2017050198A1 (en) * | 2015-09-25 | 2017-03-30 | 华为技术有限公司 | Path detection method and device |
| CN106559325A (en) * | 2015-09-25 | 2017-04-05 | 华为技术有限公司 | Path detection method and device |
| CN106559325B (en) * | 2015-09-25 | 2020-06-09 | 华为技术有限公司 | Path detection method and device |
| US10659253B2 (en) | 2015-09-25 | 2020-05-19 | Huawei Technologies Co., Ltd. | Path detection method and apparatus |
| CN107317691A (en) * | 2016-04-26 | 2017-11-03 | 华为技术有限公司 | A kind of Fault Locating Method and equipment |
| CN107317691B (en) * | 2016-04-26 | 2020-02-14 | 华为技术有限公司 | Fault positioning method and equipment |
| CN107623584A (en) * | 2016-07-15 | 2018-01-23 | 中兴通讯股份有限公司 | The detection of multi-protocol exchange label, processing method, apparatus and system |
| WO2018010560A1 (en) * | 2016-07-15 | 2018-01-18 | 中兴通讯股份有限公司 | Method, apparatus, and system for detecting and processing multi-protocol label switching |
| CN108400934A (en) * | 2017-02-08 | 2018-08-14 | 南宁富桂精密工业有限公司 | Software defined network controller, service function catenary system and route tracing method |
| CN108400934B (en) * | 2017-02-08 | 2020-11-03 | 南宁富桂精密工业有限公司 | Software defined network controller, service function chain system and path tracking method |
| CN109218196A (en) * | 2017-12-13 | 2019-01-15 | 新华三技术有限公司 | A kind of formation gathering method, device, equipment and machine readable storage medium |
| WO2019114779A1 (en) * | 2017-12-13 | 2019-06-20 | 新华三技术有限公司 | Information collection |
| CN109921987A (en) * | 2017-12-13 | 2019-06-21 | 中兴通讯股份有限公司 | A kind of BIER-TE network detecting method, apparatus and system |
| CN109218196B (en) * | 2017-12-13 | 2020-09-08 | 新华三技术有限公司 | Information collection method, device, equipment and machine-readable storage medium |
| CN109921987B (en) * | 2017-12-13 | 2022-01-21 | 中兴通讯股份有限公司 | BIER-TE network detection method, device and system |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101325584B (en) | 2012-08-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101325584B (en) | Method for tracing route, MPLS network system and entry node thereof | |
| CN101051995B (en) | Protection switching method based on no connection network | |
| CN102404145B (en) | The detection method of multi-protocol label switching ring network, Apparatus and system | |
| CN101483558B (en) | Method, system and apparatus for packet switching network access by network appliance | |
| CN101132320B (en) | Method for detecting interface trouble and network node equipment | |
| CN101174975B (en) | Periodic line fault location method and system in Ethernet | |
| US8605603B2 (en) | Route convergence based on ethernet operations, administration, and maintenance protocol | |
| JP5764820B2 (en) | Transmission system and transmission system control method | |
| CN101562531B (en) | Method and system for processing network fault and router | |
| CN100454875C (en) | Method and system for realizing dual attachment or multiple attachment of user network boundary device | |
| CN101483592B (en) | Method and apparatus for inhibiting bidirectional forwarding detection link oscillation | |
| CN105721321B (en) | A kind of the outgoing interface update method and device of equal cost multipath | |
| RU2574812C9 (en) | Method and node for route detection in data network | |
| CN103166852B (en) | The route tracing method of LSP and routing device in MPLS network | |
| CN104243239B (en) | The condition detection method and device of controller in a kind of SDN clusters | |
| CN102946349A (en) | OSPF (open shortest path first) protocol-based Ethernet E-Line service link discovery method and device | |
| CN101505250B (en) | Detection method, detection system and VPN for public network LSP | |
| CN102195822A (en) | Fault detection method and business provider edge (PE) equipment | |
| CN103297340A (en) | Routing convergence method and device in multi-protocol label switching (MPLS) and border gateway protocol (BGP) networking | |
| CN100563140C (en) | The method of a kind of multicast network system and detection multicast network link defective | |
| CN101729361B (en) | Method and device for processing message | |
| CN101527645A (en) | Method, system and relevant device for collecting network topology information | |
| JP5618946B2 (en) | Communication apparatus and communication system | |
| CN101478489B (en) | Method and system for controlling default routing notification by IS-IS protocol | |
| CN102833122A (en) | Loopback detection method and system |
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 |