CN103166786B - A kind of method and system for realizing link trace - Google Patents
A kind of method and system for realizing link trace Download PDFInfo
- Publication number
- CN103166786B CN103166786B CN201110419929.4A CN201110419929A CN103166786B CN 103166786 B CN103166786 B CN 103166786B CN 201110419929 A CN201110419929 A CN 201110419929A CN 103166786 B CN103166786 B CN 103166786B
- Authority
- CN
- China
- Prior art keywords
- maintenance
- link trace
- endpoint
- response message
- source
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Abstract
The invention discloses a kind of method and systems for realizing link trace, receive the Maintenance Intermediate Point for the Link Trace messages that source maintenance endpoint is sent, and safeguard that the of equal value of endpoint returns to transmission path number to source according to itself, reply link trace response message to source maintenance endpoint；Each link trace response message carries the traffic identifier of different return transmission paths；When the link trace response message that the Maintenance Intermediate Point received is replied is multiple, the link trace response message that source maintenance endpoint only replys the Maintenance Intermediate Point is handled.The method of the present invention and system, the not smooth brought influence of the return transmission path that link trace response message can be avoided as far as possible to be passed through, to realize the link trace function of being directed to forward path under equal cost multipath scene.
Description
Technical field
The present invention relates to the communications fields, and in particular to a kind of method and system for realizing link trace.
Background technique
In current Ethernet, normal structure Institute of Electrical and Electric Engineers (Institute of
Electricaland Electronics Engineers, IEEE) it formulated a set of ethernet operation, managed and maintained
The working mechanism of (Operation, Administration and Maintenance, OAM), and it has been used as 802.1ag standard
Formal publication.
IEEE 802.1ag standard defines the OAM(Operation Administration Maintenance) logic entity in Ethernet, including is located at Ethernet and transmits road
The maintenance endpoint (Maintenance End Point, MEP) at diameter both ends, and the maintenance among Ethernet transmission path
Intermediate point (Maintenance Intermediate Point, MIP).Wherein, safeguard that endpoint and Maintenance Intermediate Point are referred to as tieing up
It protects point (Maintenance Point, MP).
Every interchanger (Switch, SW) in Ethernet can create MP based on port.Detection of connectivity
(Continuity Check, CC) and link trace (LinkTrace, LT) are the ether that IEEE 802.1ag standard defines respectively
One of net OAM(Operation Administration Maintenance), the two functions can be run simultaneously.Wherein, detection of connectivity function is run between MEPs, using two
The mechanism that detection of connectivity message (Continuity Check Message, CCM) is periodically actively mutually sent out between a MEPs, is used
In the failure of the entire Ethernet transmission path of real-time detection.Link trace function is run between MEPs or between MEP and MIP,
When detection of connectivity Function detection to entire Ethernet transmission path does not have in the event of failure, link trace function is for carrying out path hair
It is existing, to detect the node situation that entire or one section of Ethernet transmission path is passed through；When detection of connectivity Function detection to transmission
When path fails, link trace function is for carrying out fault location.
The link trace mechanism that existing IEEE 802.1ag standard defines is described referring to Fig. 1, Fig. 1.In Fig. 1, SW1,
SW2, SW3 and SW4 are four interchangers, and wherein SW1 and SW4 respectively create and had 1 MEP, SW2 and SW3 respectively to create to have 1 MIP, are showed
Having Ethernet Link Trace mechanism includes following key step:
Step 1, after starting link trace function, source MEP is to purpose MP (can be some MIP or opposite end MEP) send chain
Road tracks message (LinkTrace Message, LTM)；As shown in fig. 1, the MEP1 of SW1 sends LTM to the MIP2 of SW3.
Step 2, after each MIP in the fixation single path of source MEP to purpose MP receives the LTM, to the transmission link
The source MEP for tracking message replys link trace and responds (LinkTrace Reply, LTR) message, and the LTR message is along reversed fixed
Single path reaches source MEP；Meanwhile MIP will continue to forward the LTM to purpose MP；As shown in fig. 1, MIP1 is returned to MEP1
Multiple LTR1, while MIP1 continues to forward LTM to MIP2.
Step 3, after purpose MP receives LTM, LTR message is replied to the source MEP for sending the LTM, the LTR message is along reversed
Fixed single path reaches source MEP；Meanwhile purpose MP does not continue to be forwarded LTM；As shown in fig. 1, purpose MP (MIP2)
LTR2 is replied to MEP1, while MIP2 will not continue to forwarding LTM.
Step 4, if source MEP receives the LTR message that all MIP and purpose MP are replied, path discovery has just been reached
Purpose；If source MEP receives only the LTR message of part MIP reply, or is not received by any LTR message, just reach
The purpose of fault location.
IEEE 802.1Qbp project formulating equal cost multipath in Ethernet (Equal Cost MultiplePaths,
ECMP working mechanism), for realizing load balancing of the service traffics on equal cost multipath, to improve the link in Ethernet
Utilization rate.IEEE 802.1Qbp draft standard (version d 0.1) regulation, supports one the Ethernet of ECMP, network edge
Interchanger will be fed stamp a forwarding label (F-tag) into client's Ether frame of network, hereafter network edge interchanger and net
Network intermediary switch selects the forwarding of progress client's Ether frame in equal cost multipath according to the F-tag, when stamping F-tag
Client's Ether frame when leaving network, network edge exchange opportunity removes F-tag entrained by client's Ether frame.
Referring to table 1, table 1 describes forwarding label (F-tag) as defined in IEEE 802.1Qbp draft standard (version d 0.1)
Specific encapsulation format.
Table 1
As shown in table 1, F-tag includes the tag protocol identifier (Tag Protocol ID, TPID) of 16 bits (bits), 3
The priority code character (Priority Code Point, PCP) of bit, the discarding of 1 bit identify (DropEligible
Indicator, DEI), the reserved field (Reserved Field, Rev) of 6 bits, 6 bits time-to-live (Time To
Live, TTL) and 16 bits traffic identifier (Flow ID).Wherein traffic identifier is used to carry out the service traffics for entering network
Shunt, different traffic identifier likely corresponds to different transmission paths, each specific traffic identifier for choose source node and
A particular path between destination node in equal cost multipath.Moreover, for the bidirectional transmission path between two nodes,
It is not associated for corresponding respectively to the traffic identifier of both direction particular transmission path.That is, one between two nodes
(so-called road altogether refers to the node complete one that forward path and reverse transfer path are passed through to the road Tiao Gong bidirectional transmission path
Cause), the traffic identifier corresponding to the traffic identifier of forward path and corresponding to reverse transfer path both may be identical, it is also possible to no
Together；Similarly, the road the Tiao Bugong bidirectional transmission path between two nodes, corresponding to the traffic identifier of forward path and right
It should both may be identical in the traffic identifier in reverse transfer path, it is also possible to different.
The link trace function that current announced IEEE 802.1ag standard defines only is applicable between two maintenance points only
There is the case where Ethernet transmission path, and the function is usually to use simultaneously with detection of connectivity function.It realizes
The function of link trace has a precondition, the return transmission path for exactly requiring LTR to be passed through be it is smooth, before this
Condition is proposed to readily satisfy in the targeted two-way fixed single path environment in road altogether of 802.1ag standard.Work as detection of connectivity
Function detection does not have in the event of failure to transmission path, it can be ensured that the return transmission path that LTR is passed through is smooth；Work as connectivity
When detection function detects that transmission path breaks down, there are two types of situation, a kind of situation is to only detect forward path hair
Raw unidirectional fault, the return transmission path that can likewise ensure that LTR is passed through at this time is smooth, another situation is that detecting
Bi-directional failure occurs for forward and reverse transmission path, and the link trace function that 802.1ag standard defines at this time only considers the bi-directional failure
The situation in transmission path same place occurs, without considering that the transmission path of both direction is not existing together while breaking down respectively
Situation, the return transmission path that can likewise ensure that LTR is passed through under former situation is smooth.
In the ECMP ethernet environment defined in IEEE 802.1Qbp, it is desirable that Ethernet OAM supports the connection based on stream
Property detection function and the link trace function based on stream.Wherein, the detection of connectivity function based on stream can continue to use 802.1ag institute
Defined detection of connectivity mechanism carries identical Flow ID in the CCM that two MEPs are sent respectively；And if be based on
The link trace function of stream continues to use the link trace mechanism of 802.1ag defined, i.e. each MIP that LTM is passed through only replys one
A LTR that identical Flow ID is carried with LTM, then it is difficult to ensure that the return transmission path that LTR is passed through is smooth, link
The purpose of following function is also just difficult to reach.
For example, as shown in Fig. 2, there is totally 11 telephone net nodes such as SW1, SW2, SW3 in ECMP ethernet environment,
The detection of connectivity function based on stream is run between the MEP2 on MEP1 and SW5 on SW1, which passes through between two MEPs
Periodicity sending is realized based on the CCM of stream.As previously mentioned, the biography that the CCM for carrying the both direction of identical Flow ID is passed through
Defeated path is possible to different, in this example MEP1 to CCM (the Flow ID X) paths traversed in the direction MEP2 be SW1- > SW21-
> SW31- > SW41- > SW5, MEP2 to CCM (the Flow ID X) paths traversed in the direction MEP1 be SW5- > SW42- > SW33-
>SW24->SW1.Similarly, it carries the transmission path that the LTM and LTR of identical Flow ID are passed through and is also possible to difference, this example
Middle LTM (Flow ID X) paths traversed is SW1- > SW21- > SW31- > SW41- > SW5, and the MIP1 on node SW21 is returned
LTR1 (Flow ID X) paths traversed be SW21- > SW1, LTR2 (the Flow ID that the MIP2 on node SW31 is returned
X) paths traversed is SW31- > SW22- > SW1, what the LTR3 (Flow ID X) that the MIP3 on node SW41 is returned was passed through
Path is SW41- > SW32- > SW23- > SW1, is returned so can not detect each MIP to the CCM in the direction MEP1 from MEP2 in this example
Whether the return transmission path that the LTR returned is passed through is unimpeded.
As it can be seen that continuing to use link trace mechanism in the prior art in ECMP ethernet environment and completing the link based on stream
When following function, it is difficult to ensure that the return transmission path that LTR is passed through be it is smooth, the purpose for leading to link trace function is difficult to
Reach.
Summary of the invention
In view of this, being kept away as far as possible the main purpose of the present invention is to provide a kind of method and system for realizing link trace
Exempt from the not smooth brought influence of return transmission path that LTR is passed through, to realize under ECMP scene for forward path
Link trace function.
In order to achieve the above objectives, the technical scheme of the present invention is realized as follows:
A method of realizing link trace, this method comprises:
Source safeguards that endpoint tracks message to purpose maintenance point transmission link, wherein carrying tracked forward path
Traffic identifier；
The Maintenance Intermediate Point for receiving the Link Trace messages safeguards that the of equal value of endpoint returns to transmission road to source according to itself
Diameter number replys link trace response message to source maintenance endpoint；Each link trace response message carries different return transmission
The traffic identifier in path；
When the link trace response message that the Maintenance Intermediate Point received is replied is multiple, source safeguards endpoint only to this
The link trace response message that Maintenance Intermediate Point is replied is handled.
According to the method for equal value for returning to transmission path number and replying link trace response message are as follows:
For all return transmission paths of equal value for going to source maintenance endpoint, Maintenance Intermediate Point reply, which can be avoided, to be passed through
Return transmission path it is not smooth brought by influence more than one link trace response message.
According to the method for equal value for returning to transmission path number and replying link trace response message are as follows:
For all return transmission paths of equal value for going to source maintenance endpoint, Maintenance Intermediate Point is directed to each return transmission path
Reply link trace response message to cover all return transmission paths；Or,
For all return transmission paths of equal value for going to source maintenance endpoint, Maintenance Intermediate Point is returned for wherein at least two
Reply link trace response message in transmission back path.
Endpoint or purpose Maintenance Intermediate Point are safeguarded for the purpose of the purpose maintenance point.
This method further include:
When the reverse transfer path that the confirmation link trace response message is passed through does not have in the event of failure, purpose safeguards endpoint
A link trace response message is only replied, wherein carrying corresponding traffic identifier；And/or
When confirming reverse transfer path that the link trace response message is passed through in the event of failure, purpose safeguards endpoint needle
To all return transmission paths of equal value for going to source maintenance endpoint, it is not smooth that reply can be avoided passed through return transmission path
The more than one link trace response message of brought influence.
The method that the purpose maintenance endpoint replys link trace response message are as follows:
For all return transmission paths of equal value for going to source maintenance endpoint, purpose safeguards that endpoint transmits road for each return
Diameter replys link trace response message to cover all return transmission paths；Or,
For all return transmission paths of equal value for going to source maintenance endpoint, purpose safeguards that endpoint is directed to wherein at least two
It returns to transmission path and replys link trace response message.
This method further include:
Source maintenance endpoint directly abandons other link trace response messages from the Maintenance Intermediate Point.
The method that the link trace response message that the Maintenance Intermediate Point is replied is handled are as follows:
The first link trace response message replied the Maintenance Intermediate Point is handled.
A kind of system for realizing link trace, the system include source maintenance endpoint, Maintenance Intermediate Point；Wherein,
The Maintenance Intermediate Point for receiving the Link Trace messages that the source maintenance endpoint is sent, for arriving source according to itself
It safeguards that the of equal value of endpoint returns to transmission path number, replys link trace response message to source maintenance endpoint；Each link trace response
Message carries the traffic identifier of different return transmission paths；
Endpoint is safeguarded in the source, for tracking message to purpose maintenance point transmission link, wherein carrying tracked forward direction
The traffic identifier of transmission path；And when the link trace response message that the Maintenance Intermediate Point received is replied is multiple, only
The link trace response message replied the Maintenance Intermediate Point is handled.
The Maintenance Intermediate Point is used when replying link trace response message according to the return transmission path number of equal value
In:
For all return transmission paths of equal value for going to source maintenance endpoint, replys and can be avoided passed through return transmission
The more than one link trace response message influenced brought by path is not smooth.
The Maintenance Intermediate Point is used when replying link trace response message according to the return transmission path number of equal value
In:
For all return transmission paths of equal value for going to source maintenance endpoint, link is replied for each return transmission path
Tracking response message is to cover all return transmission paths；Or,
For all return transmission paths of equal value for going to source maintenance endpoint, transmission path is returned for wherein at least two
Reply link trace response message.
Endpoint or purpose Maintenance Intermediate Point are safeguarded for the purpose of the purpose maintenance point.
When safeguarding endpoint for the purpose of the purpose maintenance point, the purpose maintenance endpoint is used for:
When confirming that reverse transfer path that the link trace response message is passed through in the event of failure, only do not reply a chain
Road tracking response message, wherein carrying corresponding traffic identifier；And/or
When confirming reverse transfer path that the link trace response message is passed through in the event of failure, for going to source maintenance
All return transmission paths of equal value of endpoint, reply can be avoided the not smooth brought influence of passed through return transmission path
More than one link trace response message.
When the purpose maintenance endpoint replys link trace response message, it is used for:
For all return transmission paths of equal value for going to source maintenance endpoint, link is replied for each return transmission path
Tracking response message is to cover all return transmission paths；Or,
For all return transmission paths of equal value for going to source maintenance endpoint, transmission path is returned for wherein at least two
Reply link trace response message.
The source maintenance endpoint is also used to: directly being abandoned other link traces response from the Maintenance Intermediate Point and is disappeared
Breath.
Source maintenance endpoint when handling the link trace response message that the Maintenance Intermediate Point is replied,
For:
The first link trace response message replied the Maintenance Intermediate Point is handled.
The system is set in the Ethernet for supporting equal cost multipath.
As it can be seen that receiving the Maintenance Intermediate Point for the Link Trace messages that source maintenance endpoint is sent, can be tieed up according to itself to source
It protects the of equal value of endpoint and returns to transmission path number, reply link trace to source maintenance endpoint and respond LTR message；Each link trace response
Message carries the traffic identifier of different return transmission paths；When the link trace response that the Maintenance Intermediate Point received is replied
When message is multiple, the link trace response message that source maintenance endpoint only replys the Maintenance Intermediate Point is handled.This
Inventive method and system, the not smooth brought influence of the return transmission path that LTR can be avoided as far as possible to be passed through, to realize
The link trace function of forward path is directed under ECMP scene.
Detailed description of the invention
Fig. 1 is link trace process schematic as defined in IEEE 802.1ag standard；
Fig. 2 is to continue to use link trace schematic diagram of mechanism as defined in 802.1ag standard in ECMP environment；
Fig. 3 is that the present invention is based on the link trace general flow charts of stream；
Fig. 4 is the link trace process schematic for path validation of the embodiment of the present invention；
Fig. 5 is the link trace process schematic for fault location of the embodiment of the present invention.
Specific embodiment
In practical applications, it in the Ethernet for supporting equal cost multipath, is defined by extension IEEE 802.1ag standard
Link trace mechanism, the Maintenance Intermediate Point in the transmission path based on stream can safeguard the equative route between endpoint according to source
Number, all link trace response messages of equal value for returning to transmission path can be covered by replying to source maintenance endpoint.Safeguard endpoint in source
The link trace response message (such as first link trace response message) returned from the Maintenance Intermediate Point is then only handled,
It is influenced brought by the return transmission path that thus LTR can be avoided as far as possible to be passed through is not smooth.
Referring to Fig. 3, Fig. 3 be the present invention is based on the link trace general flow chart of stream, the process the following steps are included:
Step 301: safeguarding that endpoint tracks message to purpose maintenance point transmission link in source.
The purpose maintenance point may be opposite end maintenance endpoint (can be described as purpose maintenance endpoint), it is also possible to some maintenance
Intermediate point (can be described as purpose Maintenance Intermediate Point).
The Link Trace messages carry F-tag, wherein including the traffic identifier of the specific forward path tracked
(usually 16 bit).
Step 302: after Maintenance Intermediate Point receives the Link Trace messages, replying one or more chains to source maintenance endpoint
Road tracking response message.It is arrived it should be noted that the number for the link trace response message replied is equal to the Maintenance Intermediate Point
Source safeguards that the of equal value of endpoint returns to transmission path number, and all link trace response messages carry different traffic identifier respectively and abide by
Follow different return transmission paths.Then, the Maintenance Intermediate Point continues to forward the Link Trace messages to purpose maintenance point.
IEEE 802.1Qbp draft standard (version d 0.1) regulation supports the Ethernet of ECMP to run intermediate system in
Between system (Intermediate System to Intermediate System, IS-IS) Routing Protocol, so each net
Network node all learns to have arrived full mesh topology；Moreover, being selected from equal cost multipath using traffic identifier and Local Node Information specific
Hash (Hash) algorithm of transmission path be it is standardized, so Maintenance Intermediate Point can automatically select it is one or more different
Traffic identifier, and then one or more different link trace response messages are encapsulated respectively, all of equal value return are transmitted with realizing
The all standing in path.
Step 303: after source maintenance endpoint receives the link trace response message that the Maintenance Intermediate Point is replied, recording it
The nodal informations such as node identification, incoming interface, the outgoing interface of middle carrying.Also, if what the Maintenance Intermediate Point received was replied
Link trace response message (that is: carrying the link trace response message of the node identification of the Maintenance Intermediate Point) be it is multiple, then
Safeguard that endpoint only carries out the link trace response message (such as first link trace response message) in these message in source
Processing, and directly abandon other link trace response messages from the Maintenance Intermediate Point.
For start link trace function source maintenance endpoint for, the source maintenance endpoint be only concerned tracked it is specific just
To the accessibility and its nodal information of the passed through node of transmission path, and it is not relevant for the return transmission path letter of these nodes
Breath, that is to say, that being not relevant for link trace response message is returned by what path.So specific for being tracked
Each MIP that forward path passes through, as long as there is a link trace response message that can safeguard endpoint, link back to source
The realization of following function would not be affected.
The present invention is further described below by way of the specific embodiment in two practical applications.
Embodiment one,
In the present embodiment, source, which is safeguarded, runs the detection of connectivity function based on stream, week between endpoint and opposite end maintenance endpoint
Phase property mutually sends out the CCM message for carrying Flow ID X, judges corresponding to for MEP1 to MEP2 by running detection of connectivity function
The specific forward path of Flow ID X does not have failure.Then, source safeguards that endpoint is initiated to opposite end maintenance endpoint based on stream
Link trace safeguards Ethernet transmission path institute of the endpoint to opposite end maintenance endpoint for carrying out path validation to detect from source
The node situation of process.Here why be known as path validation, rather than so-called path discovery in 802.1ag standard, be because
For 802.1Qbp draft standard (version d 0.1) regulation, Intermediate System-Intermediate System, network are run in the Ethernet for supporting ECMP
Each of node all pass through topology and all transmission path that the whole network has been arrived in Routing Protocol study, so link trace
The function of be accomplished that path validation herein, that is, verify actual transmission path whether with by Intermediate System-Intermediate System
The transmission path practised is consistent.
Referring to fig. 4, Fig. 4 is the link trace process schematic for path validation of the embodiment of the present invention.In conjunction with Fig. 3 and
Fig. 4, then process shown in Fig. 4 mainly includes the following steps:
Step 401: safeguarding that endpoint MEP1 determines that purpose maintenance point is that endpoint MEP2 is safeguarded simultaneously in opposite end according to input information in source
It is sent to it LTM, the Flow ID X of tracked transmission path is carried in the LTM.
The source received input information of maintenance endpoint includes the MAC Address of port where MEP2, further includes reaching from MEP1
The mark of the specific forward path of MEP2, this mark can be Flow ID X, be also possible to that Flow can be calculated
Other marks of ID X, for example information parameter (parameter set " source/destination MAC Address, source/destination IP address, the source/mesh of stream are described
Port " one or more of).
The Flow ID X of the transmission path tracked includes in F-tag entrained by LTM, and then LTM can follow described
Transmission path reaches MEP2.
Step 402: after Maintenance Intermediate Point MIP1 receives LTM, going to source by judgement discovery only one and safeguard endpoint
Return transmission path SW21- > SW1 of MEP1.Then MIP1 only replys a link trace response message LTR1 to MEP1, wherein
Carry the Flow ID X copied from the LTM.Then MIP1 continues to forward the LTM to purpose maintenance point MEP2.
After Maintenance Intermediate Point MIP2 receives LTM, safeguard that the return of endpoint MEP1 passes by judging that discovery there are two to go to source
Defeated path SW31- > SW21- > SW1 and SW31- > SW22- > SW1, and Flow ID X and Flow ID Y corresponds respectively to this two
Return to transmission path.Then MIP2 replys two link trace response message LTR21 and LTR22 to MEP1 to cover two returns
Transmission path, LTR21 and LTR22 carry Flow ID X and Flow ID Y respectively.Then MIP2 continues to purpose maintenance point
MEP2 forwards the LTM.
After Maintenance Intermediate Point MIP3 receives LTM, safeguard that the return of endpoint MEP1 passes by judging that discovery there are three to go to source
Defeated path SW41- > SW31- > SW21- > SW1, SW41- > SW31- > SW22- > SW1 and SW41- > SW32- > SW23- > SW1, and
Flow ID X, Flow ID Y and Flow ID Z correspond respectively to this three return transmission paths.Then MIP3 is replied to MEP1
Three link trace response message LTR31, LTR32 and LTR33 to cover three return transmission paths, LTR31, LTR32 and
LTR33 carries Flow ID X, Flow ID Y and Flow ID Z respectively.Then MIP3 continues to forward to purpose maintenance point MEP2
The LTM.
It should be noted that indicating (Remote according to the remote bug in the CCM message received
DefectIndicator, RDI), if passed by the particular inverse corresponding to Flow ID X of judgement discovery MEP2 to MEP1
Defeated path does not have failure, then only can reply a link trace response after purpose maintenance point MEP2 receives LTM to MEP1 and disappear
LTR4 is ceased, wherein carrying Flow ID X；If by judgement discovery MEP2 to MEP1 corresponding to the specific anti-of Flow ID X
It is faulty to transmission path, then purpose maintenance point MEP2 can go to the return transmission road of MEP1 according to four judged
Diameter replys four link trace response messages to MEP1, wherein this four return transmission paths can be covered not respectively by carrying
Same Flow ID.
Step 403: source maintenance endpoint MEP1 receives Maintenance Intermediate Point MIP1, MIP2, MIP3 and purpose maintenance point MEP2
After the link trace response message of reply, the nodal informations such as the node identification, incoming interface, outgoing interface wherein carried are recorded.Such as
The above-mentioned all return transmission paths of fruit be all it is smooth, source maintenance endpoint MEP1 will receive MIP2 reply two link traces
Three link trace response messages that response message and MIP3 are replied, but MEP1 is only to the respectively from MIP2 and MIP3
One link trace response message is handled, and directly abandons other link trace response messages from MIP2 and MIP3.
Embodiment two,
In the present embodiment, source, which is safeguarded, runs the detection of connectivity function based on stream, week between endpoint and opposite end maintenance endpoint
Phase property mutually sends out the CCM message for carrying Flow ID X, judges corresponding to for MEP1 to MEP2 by running detection of connectivity function
The specific forward path of Flow ID X is faulty.Then, source safeguards that endpoint initiates the chain based on stream to opposite end maintenance endpoint
Road tracking safeguards that endpoint is in the Ethernet transmission path of opposite end maintenance endpoint for carrying out fault location to determine from source
There are failures between which two node.
It is the link trace process schematic for fault location of the embodiment of the present invention referring to Fig. 5, Fig. 5.In conjunction with Fig. 3 and
Fig. 5, then process shown in Fig. 5 mainly includes the following steps:
Step 501: safeguarding that endpoint MEP1 determines that purpose maintenance point is that endpoint MEP2 is safeguarded simultaneously in opposite end according to input information in source
It is sent to it LTM, the Flow ID X of tracked transmission path is carried in the LTM.
The source received input information of maintenance endpoint includes the MAC Address of port where MEP2, further includes reaching from MEP1
The mark of the specific forward path of MEP2, this mark can be Flow ID X, be also possible to that Flow can be calculated
Other marks of ID X, for example information parameter (parameter set " source/destination MAC Address, source/destination IP address, the source/mesh of stream are described
Port " one or more of).
The Flow ID X of the transmission path tracked includes in F-tag entrained by LTM.
Step 502: after Maintenance Intermediate Point MIP1 receives LTM, going to source by judgement discovery only one and safeguard endpoint
Return transmission path SW21- > SW1 of MEP1, then MIP1 only replys a link trace response message LTR1 to MEP1, wherein
Carry the Flow ID X copied from the LTM.Then MIP1 continues to forward the LTM to purpose maintenance point MEP2.
After Maintenance Intermediate Point MIP2 receives LTM, safeguard that the return of endpoint MEP1 passes by judging that discovery there are two to go to source
Defeated path SW31- > SW21- > SW1 and SW31- > SW22- > SW1, and Flow ID X and Flow ID Y corresponds respectively to this two
Return to transmission path.Then MIP2 replys two link trace response message LTR21 and LTR22 to MEP1 to cover two returns
Transmission path, LTR21 and LTR22 carry Flow ID X and Flow ID Y respectively.Then MIP2 continues to purpose maintenance point
MEP2 forwards the LTM.
Due to going to the forward path corresponding to Flow ID X of MIP3 from MIP2, there are failures, so in maintenance
Between point MIP3 can not receive the LTM, would not also send any link trace and reply message.
Step 503: source maintenance endpoint MEP1 receives the link trace response message of Maintenance Intermediate Point MIP1 and MIP2 reply
Afterwards, the nodal informations such as the node identification, incoming interface, outgoing interface wherein carried are recorded.If road is transmitted in above-mentioned all returns
Diameter be all it is smooth, source maintenance endpoint MEP1 will receive MIP2 reply two link trace response messages, but MEP1 only to come
It is handled from first link trace response message of MIP2, and directly abandons another link trace response from MIP2
Message.
As it can be seen that by comparing on forward path corresponding to Flow ID X collected by this link trace
Nodal information on nodal information, and forward path corresponding to the Flow ID X that is collected into before, it can be determined that go out
Transmission fault occurs between MIP2 and MIP3 (including MIP3).
It, can be according to certainly in conjunction with Fig. 3 and above-mentioned two embodiment it is found that receiving the Maintenance Intermediate Point of Link Trace messages
Body safeguards that the of equal value of endpoint returns to transmission path number to source, replys link trace response message to source maintenance endpoint；All links
Tracking response message all carries the corresponding traffic identifier for returning to transmission path respectively.
Based on above-mentioned thinking, in order to ensure reliability, for all return transmission paths for going to source maintenance endpoint, maintenance
Intermediate point can reply link trace response message for each return transmission path to cover all return transmission paths.But in reality
In the application of border, various flexible variations can also be carried out, such as: for all return transmission paths for going to source maintenance endpoint, maintenance
Intermediate point returns to transmission path for wherein at least two and replys link trace response message, or for wherein no less than two
It is a and more than half return transmission path reply link trace response message.As it can be seen that no matter returning to the number of transmission path
How, as long as the link trace response message with certain amount (more than one as far as possible) replied can avoid LTR as far as possible
It is influenced brought by the return transmission path passed through is not smooth.Above-mentioned thinking is equally applicable to purpose in step 402 and ties up
Protect the case where point MEP2 replys link trace response message.
In addition, when selection will reply the return transmission path of link trace response message, it may be considered that traffic load, transmission
Rate, service quality (QoS) etc..
In summary as it can be seen that the method for either realizing link trace still includes Maintenance Intermediate Point, source maintenance endpoint
The system for realizing link trace, the not smooth brought shadow of the return transmission path that the present invention can avoid as far as possible LTR from being passed through
It rings, to realize the link trace function of being directed to forward path under ECMP scene.
The foregoing is only a preferred embodiment of the present invention, is not intended to limit the scope of the present invention.
Claims (17)
1. a kind of method for realizing link trace, which is characterized in that this method comprises:
Source safeguards that endpoint tracks message to purpose maintenance point transmission link, wherein carrying failing to be sold at auction for tracked forward path
Know；
Each Maintenance Intermediate Point of the Link Trace messages is received, determines the traffic identifier for returning to transmission path；According to determining
The traffic identifier number for returning to transmission path determines that itself safeguards that the of equal value of endpoint returns to transmission path number to source；Source is arrived according to itself
It safeguards that the of equal value of endpoint returns to transmission path number, replys link trace response message to source maintenance endpoint to realize to all equivalences
Return to all standing of transmission path；According to the path that the traffic identifier of the forward path determines, the link trace is forwarded
Message；Each link trace response message carries the traffic identifier of different return transmission paths；
When determining at least one return transmission path is unimpeded and receives the dimension according to the traffic identifier for returning to transmission path
When the link trace response message that shield intermediate point is replied is multiple, source safeguards endpoint only to a chain of Maintenance Intermediate Point reply
Road tracking response message is handled.
2. the method according to claim 1, wherein according to it is described it is of equal value return transmission path number reply link with
The method of track response message are as follows:
For go to source maintenance endpoint it is all it is of equal value return to transmission paths, Maintenance Intermediate Point, which is replied, can be avoided returning of being passed through
The more than one link trace response message influenced brought by transmission back path is not smooth.
3. according to the method described in claim 2, it is characterized in that, according to it is described it is of equal value return transmission path number reply link with
The method of track response message are as follows:
For all return transmission paths of equal value for going to source maintenance endpoint, Maintenance Intermediate Point is returned for each return transmission path
Multiple link trace response message is to cover all return transmission paths；Or,
For all return transmission paths of equal value for going to source maintenance endpoint, Maintenance Intermediate Point is returned for wherein at least two and is passed
Reply link trace response message in defeated path.
4. the method according to claim 1, wherein safeguarding endpoint or purpose dimension for the purpose of the purpose maintenance point
Protect intermediate point.
5. method according to any one of claims 1 to 4, which is characterized in that this method further include:
When the reverse transfer path that the confirmation link trace response message is passed through does not have in the event of failure, purpose maintenance endpoint is only returned
A multiple link trace response message, wherein carrying corresponding traffic identifier；And/or
When confirming reverse transfer path that the link trace response message is passed through in the event of failure, purpose maintenance endpoint is for going
Toward all return transmission paths of equal value of source maintenance endpoint, reply can be avoided the not smooth institute's band of passed through return transmission path
The more than one link trace response message of the influence come.
6. according to the method described in claim 5, it is characterized in that, purpose maintenance endpoint replys link trace response message
Method are as follows:
For all return transmission paths of equal value for going to source maintenance endpoint, purpose safeguards that endpoint is equal for each return transmission path
Link trace response message is replied to cover all return transmission paths；Or,
For all return transmission paths of equal value for going to source maintenance endpoint, purpose safeguards that endpoint is returned for wherein at least two
Transmission path replys link trace response message.
7. the method according to claim 1, wherein this method further include:
Source maintenance endpoint directly abandons other link trace response messages from the Maintenance Intermediate Point.
8. the method according to claim 1, wherein being rung to the link trace that the Maintenance Intermediate Point is replied
Answer the method that message is handled are as follows:
The first link trace response message replied the Maintenance Intermediate Point is handled.
9. a kind of system for realizing link trace, which is characterized in that the system includes source maintenance endpoint, Maintenance Intermediate Point；Wherein,
The each Maintenance Intermediate Point for receiving the Link Trace messages that the source maintenance endpoint is sent, returns to transmission path for determining
Traffic identifier；According to the traffic identifier number of determining return transmission path, determine that itself safeguards that the of equal value of endpoint returns to transmission to source
Number of path；It safeguards that the of equal value of endpoint returns to transmission path number to source according to itself, replys link trace response to source maintenance endpoint
Message is to realize to all standings of equal value for returning to transmission path；According to the traffic identifier of forward path determine path,
Forward the Link Trace messages；Each link trace response message carries the traffic identifier of different return transmission paths；
Endpoint is safeguarded in the source, for tracking message to purpose maintenance point transmission link, wherein carrying tracked positive transmission
The traffic identifier in path；And according to it is described return transmission path traffic identifier determine at least one return transmission path it is unimpeded and
When the link trace response message that the Maintenance Intermediate Point received is replied is multiple, only to one of Maintenance Intermediate Point reply
Link trace response message is handled.
10. system according to claim 9, which is characterized in that the Maintenance Intermediate Point is passed according to of equal value return
When defeated number of path replys link trace response message, it is used for:
For all return transmission paths of equal value for going to source maintenance endpoint, reply can be avoided passed through return transmission path
The more than one link trace response message influenced brought by not smooth.
11. system according to claim 10, which is characterized in that the Maintenance Intermediate Point is passed according to of equal value return
When defeated number of path replys link trace response message, it is used for:
For all return transmission paths of equal value for going to source maintenance endpoint, link trace is replied for each return transmission path
Response message is to cover all return transmission paths；Or,
For all return transmission paths of equal value for going to source maintenance endpoint, transmission path is returned for wherein at least two and is replied
Link trace response message.
12. system according to claim 9, which is characterized in that safeguard endpoint or purpose for the purpose of the purpose maintenance point
Maintenance Intermediate Point.
13. according to the described in any item systems of claim 9 to 12, which is characterized in that tieed up for the purpose of the purpose maintenance point
When protecting endpoint, the purpose maintenance endpoint is used for:
When confirming reverse transfer path that the link trace response message is passed through not in the event of failure, only reply a link with
Track response message, wherein carrying corresponding traffic identifier；And/or
When confirming reverse transfer path that the link trace response message is passed through in the event of failure, for going to source maintenance endpoint
It is all it is of equal value return to transmission paths, reply can be avoided passed through returns transmission path it is not smooth brought by influence it is more
In one link trace response message.
14. system according to claim 13, which is characterized in that the purpose maintenance endpoint replys link trace response and disappears
When breath, it is used for:
For all return transmission paths of equal value for going to source maintenance endpoint, link trace is replied for each return transmission path
Response message is to cover all return transmission paths；Or,
For all return transmission paths of equal value for going to source maintenance endpoint, transmission path is returned for wherein at least two and is replied
Link trace response message.
15. system according to claim 9, which is characterized in that the source maintenance endpoint is also used to: directly being abandoned from institute
State other link trace response messages of Maintenance Intermediate Point.
16. system according to claim 9, which is characterized in that the source maintenance endpoint is returned to the Maintenance Intermediate Point
When a multiple link trace response message is handled, it is used for:
The first link trace response message replied the Maintenance Intermediate Point is handled.
17. system according to claim 9, which is characterized in that the system is set to the Ethernet for supporting equal cost multipath
In.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110419929.4A CN103166786B (en) | 2011-12-15 | 2011-12-15 | A kind of method and system for realizing link trace |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110419929.4A CN103166786B (en) | 2011-12-15 | 2011-12-15 | A kind of method and system for realizing link trace |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103166786A CN103166786A (en) | 2013-06-19 |
| CN103166786B true CN103166786B (en) | 2019-03-08 |
Family
ID=48589539
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110419929.4A Active CN103166786B (en) | 2011-12-15 | 2011-12-15 | A kind of method and system for realizing link trace |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103166786B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103607301B (en) * | 2013-11-18 | 2018-04-06 | 新华三技术有限公司 | The protection switching method and equipment of link failure under a kind of ECMP modes |
| CN106452963A (en) * | 2016-10-18 | 2017-02-22 | 北京东土科技股份有限公司 | Network path sensing method and system |
| US10129127B2 (en) * | 2017-02-08 | 2018-11-13 | Nanning Fugui Precision Industrial Co., Ltd. | Software defined network controller, service function chaining system and trace tracking method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101826989A (en) * | 2009-03-02 | 2010-09-08 | 华为技术有限公司 | Method and device for treating fault |
| CN101986604A (en) * | 2010-10-29 | 2011-03-16 | 中兴通讯股份有限公司 | Link fault positioning method and system of packet transport network (PTN) |
| CN102177681A (en) * | 2011-04-21 | 2011-09-07 | 华为技术有限公司 | Fault detection method and system |
| CN102185719A (en) * | 2011-05-12 | 2011-09-14 | 中兴通讯股份有限公司 | Service link tracking realization method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8391163B2 (en) * | 2009-03-23 | 2013-03-05 | Cisco Technology, Inc. | Operating MPLS label switched paths and MPLS pseudowire in loopback mode |
-
2011
- 2011-12-15 CN CN201110419929.4A patent/CN103166786B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101826989A (en) * | 2009-03-02 | 2010-09-08 | 华为技术有限公司 | Method and device for treating fault |
| CN101986604A (en) * | 2010-10-29 | 2011-03-16 | 中兴通讯股份有限公司 | Link fault positioning method and system of packet transport network (PTN) |
| CN102177681A (en) * | 2011-04-21 | 2011-09-07 | 华为技术有限公司 | Fault detection method and system |
| CN102185719A (en) * | 2011-05-12 | 2011-09-14 | 中兴通讯股份有限公司 | Service link tracking realization method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103166786A (en) | 2013-06-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1716912B (en) | Method and apparatus providing rapid end-to-end failover in a packet switched communications network | |
| CN101953124B (en) | Constructing repair paths around multiple non-available links in a data communications network | |
| CN100397088C (en) | Method and system for providing failure protection in a ring network that utilizes label switching | |
| CN101051995B (en) | Protection switching method based on no connection network | |
| US9871708B2 (en) | Method and system for ring protection switching | |
| US8149692B2 (en) | Ring topology discovery mechanism | |
| CN109547279B (en) | Method and system for processing signal degradation fault | |
| EP1111860A2 (en) | Automatic protection switching using link-level redundancy supporting multi-protocol label switching | |
| CN104380671B (en) | The increase failure covering in classification, redundancy, QoS routing selection | |
| CN101702658B (en) | Implement method of ring network protection and system thereof | |
| US20130343179A1 (en) | Ethernet chain protection switching | |
| CN104662851A (en) | Enhancements to PIM fast re-route with upstream activation packets | |
| CN104509044A (en) | Enhancements of the protocol independent multicast (PIM) fast re-route methodology with downstream notification packets | |
| CN102006218B (en) | Tunnel protection method and device | |
| EP3654664A1 (en) | Method, apparatus and system for interconnected ring protection | |
| CN102088387B (en) | Tunnel protection method and device of ring network | |
| EP2521275B1 (en) | Method and device for tunnel protection | |
| CN104852809B (en) | The processing method and system of Signal Degrade failure | |
| CN103368844B (en) | Message processing method and LSR in MPLS network | |
| CN103166786B (en) | A kind of method and system for realizing link trace | |
| JP5113124B2 (en) | Fault monitoring system in packet network | |
| CN102833122B (en) | Loopback detection method and system | |
| WO2015096512A1 (en) | Packet transmission method and device based on trill network | |
| CN103036731B (en) | A kind of equipment of the loopback detection based on stream, system and method | |
| JP2009159512A (en) | Telephone system, node device thereof, and method for forming roundabout route |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |