CN100536409C - Round trip method - Google Patents
Round trip method Download PDFInfo
- Publication number
- CN100536409C CN100536409C CNB2005100646734A CN200510064673A CN100536409C CN 100536409 C CN100536409 C CN 100536409C CN B2005100646734 A CNB2005100646734 A CN B2005100646734A CN 200510064673 A CN200510064673 A CN 200510064673A CN 100536409 C CN100536409 C CN 100536409C
- Authority
- CN
- China
- Prior art keywords
- loopback
- message
- point
- maintenance
- multicast
- 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.)
- Expired - Fee Related
Links
Abstract
A method to achieve the return, it is: sets sign information of every maintenance end, loads the sign information of the maintenance end with return aim in the multi-broadcast return information by the maintenance end, send; receives the return answer information that sends by the every maintenance end of the return information according to the maintenance end sign information that loads in the return information. The invention provides a new mechanism of the return, avoids the process that needs to write the maintenance end address information with return aim when MEP sends the return information, the invention can achieve return to the certain prearrange maintenance end with pertinence, thereby achieve perfect the return function of the Ethernet OAM solving project, improves the practical aim of the return method.
Description
Technical field
The present invention relates to the network test technical field, be specifically related to a kind of implementation method of loopback.
Background technology
At present, ITU-T (standardization department of international telecommunication union telecommunication) and two groups of IEEE (IEEE) at the same time to Ethernet end to end OAM (operation management maintain) function study, wherein ITU-T in two pieces of documents Y.1730 and Y.71ehtoam to Ethernet end to end OAM(Operation Administration Maintenance) be described, IEEE in the 802.1ag document to Ethernet end to end OAM(Operation Administration Maintenance) be described.In the above-mentioned document, the thinking of two tissues is identical substantially, and the solution of OAM(Operation Administration Maintenance) is also very similar, has wherein comprised in the document of ITU-T alarm and performance part making the OAM system more perfect.
Industry is reached common understanding to basic OAM(Operation Administration Maintenance) at present, and promptly OAM(Operation Administration Maintenance) should comprise three parts: fault discovery automatically, failure proof and fault location.Here " fault " may be caused by link failure, loop and software misconfiguration etc.
LB (Loopback loopback) provides a kind of failure proof method.LB can realize the Connectivity Verification of point-to-point.When network breaks down, fault is further located by LB.
At present, the implementation method of the LB of industry definition mainly comprises following three steps:
Step 1, MEP (Maintenance End Point maintaining end point) send LB message.
MEP can send the packet of LB message by order line transmitting order to lower levels or MEP control MIB (management information bank).The LB message frame adopts through specifically defined multicast MAC (medium access control) address.This sequence number that sends bag keeps 5s at least after this bag sends, MEP waits for the response message of opposite end, i.e. LBR (LB response) message in this gap.
The every other MEP that is in same MEG (Maintenance Entity) on step 2, the network receives LB message, structure LBR message, and send.
MEP receives LB message, and check whether the validity of this message and the MEGIDTLV (maintenance entity group id TLV) in this message packets mate with the Configuration Values that receives bridge port, if this message is effective and MEGID TLV and the Configuration Values coupling that receives bridge port, then each territory in the LB message all is copied in the LBR message, and source MAC in the LBR message and target MAC (Media Access Control) address are exchanged, operation code field is become LBR from LBM.
All TLV in the LB message comprise the TLV that identifies the LB sender of the message like this, have all been suffered by the complete LBR message that is mapped to, and except source MAC, the MEP that sends LBR message does not need to provide any other information to the MEP that sends LB message.
The MEP of step 3, transmission LB message receives LBR message.
The MEP that sends LB message judges whether to receive the LBR message of normally returning in the sequence number retention time of appointment, if received the LBR message of normally returning, then the information of each the far-end MEP that stores in the MIB storehouse according to this MEP again judges whether that all far-end MEP have sent LBR message, if, then this LB success; All send LBR message if not all far-end MEP, determined this LB failure; In the sequence number retention time of appointment, do not receive the LBR message of normally returning if send the MEP of LB message, determine this LB failure.After determining this LB failure, the MEP that sends LB message can re-construct LB message and test, or directly there is fault in report network.
Because MIP (Maintenance Intermediate Point Maintenance Intermediate Point) does not have MIPID (MIP identifier) in the prior art, so, in above-mentioned LB method, the loopback for specifying MIP to order is merely able to realize by the MAC Address of loopback source MAC and loopback point of destination.Therefore, send the MEP of LB message need be in LB message the direct MAC Address of appointment LB purpose maintenance point, or obtain the MAC Address of LB purpose maintenance point by additive method, be filled up to then in the LB message.
Because the OAM(Operation Administration Maintenance) of Ethernet is separate, the MAC Address that obtains loopback purpose maintenance point by CC (continuity detection) and LT methods such as (link tracings) can make the OAM(Operation Administration Maintenance) generation interdepend, so, can not obtain the MAC Address of LB purpose maintenance point by methods such as CC, LT, and also not have definition to make each MEP can learn the method for the MAC Address of all MIP on the network in the prior art.Therefore, the implementation method of LB can not realize the LB function at all MP in the network in the prior art, has the realization limitation.
Summary of the invention
The objective of the invention is to, a kind of implementation method of loopback is provided,,, improve the purpose of loop back method practicality to realize improving the loop fuction of Ethernet OAM solution by the identification information of each maintenance point in the network is set.
For achieving the above object, the implementation method of a kind of loopback provided by the invention is used for Ethernet, comprising:
A, the identification information of each maintenance point in the network is set;
B, maintaining end point are carried on the identification information of loopback purpose maintenance point in the multicast loopback message, send;
C, receive each maintenance point of described loopback message, if with described loopback message in the Maintenance Point Identification information of carrying send loopback response message coupling, then with the source address of described loopback message as destination address, send the loopback response message.Described maintenance point is: Maintenance Intermediate Point, or maintaining end point and Maintenance Intermediate Point.
The identification information of described each maintenance point has nothing in common with each other.
Described step b specifically comprises:
In loopback message, increase the TLV field;
Described maintaining end point is carried on the identification information of loopback purpose maintenance point in the TLV field of described increase, and sends described multicast loopback message.
Described step c specifically comprises:
When the Maintenance Point Identification information that the maintenance point that receives described multicast loopback message carries is identical, determine that it is loopback purpose maintenance point in the Maintenance Point Identification information of determining himself and described multicast loopback message;
Described loopback purpose maintenance point produces the loopback response message, and its address information is carried in the described loopback response message is sent to described maintaining end point.
Described step c also comprises:
When inequality the and maintenance point that receive described multicast loopback message of the Maintenance Point Identification information that the maintenance point that receives described multicast loopback message carries is Maintenance Intermediate Point, continue to transmit its described multicast loopback message that receives in the Maintenance Point Identification information of determining himself and described multicast loopback message.
Described step c also comprises:
When the source address information that the maintenance point that receives described multicast loopback message carries is identical, determine that it is the maintaining end point of the described loopback message of transmission in the address information of determining himself and described multicast loopback message, abandon described multicast loopback message.
Described method also comprises:
The maintaining end point of described transmission multicast loopback message judges whether to receive the loopback response message in the interval at the fixed time;
If described maintaining end point receives the loopback response message in the interval at the fixed time, determine this loopback success;
If described maintaining end point does not receive the loopback response message in the interval at the fixed time, determine this loopback failure.
Described maintaining end point reports fault message or resends described loopback message when determining this loopback failure.
Described address information comprises: Media Access Control address information.
Description by technique scheme as can be known, the invention provides a kind of new mechanism of loopback, by the identification information of each maintenance point in the network is set, MEP is when sending the multicast loopback message, the identification information of loopback purpose maintenance point is carried in the multicast loopback message, avoided MEP when sending loopback message, need in this message, write the process of loopback purpose maintenance point address information, make loop back method provided by the invention have practicality, make the present invention realize loopback to certain scheduled maintenance point targetedly, and method is simple, easily realization; Thereby realized improving the loop fuction of Ethernet OAM solution by technical scheme provided by the invention, improved the purpose of loop back method practicality.
Embodiment
Core of the present invention is: the identification information of each maintenance point in the network is set, and maintaining end point is carried on the identification information of loopback purpose maintenance point in the multicast loopback message, sends; Each maintenance point that receives described loopback message sends the loopback response message according to the Maintenance Point Identification information of carrying in the described loopback message.
Based on core concept of the present invention technical scheme provided by the invention is further described below.
The present invention at first needs to be provided with the identification information of each maintenance point in the network, as be that each MIP in the network distributes MPID (Maintenance Point Identification information), or be that all MP in the network such as MIP, MEP distribute a MPID, and the same the whole network with MEPID of this MPID is unique.
After the MPID of each MP was set, MEP need be carried on the MPID of loopback destination node in this multicast LB message, and send this multicast LB message when sending multicast LB message.
MEP with the MPID of loopback purpose maintenance point be carried in the LB message method can for: in LB message, add a TLV field, the MPID of loopback purpose maintenance point be carried in the TLV field of adding in LB message.
MEP is sequence number of each multicast LB distribution of messages, and this sequence number is as the sign of identification LBR message, and MEP is when sending multicast LB message, and correspondence starts a timer, and the timing length of this timer is configurable, as is set to 5s (second) etc.MEP waits in the timing length of timer and receives the LBR message that loopback purpose maintenance point returns.
MEP is after sending multicast LB message, whether the MPID of the loopback purpose maintenance point that each maintenance point that receives this multicast LB message all relatively carries in this multicast LB message in the network is identical with the MPID of himself, if it is identical, then this maintenance point is a loopback purpose maintenance point, loopback purpose maintenance point checks whether the validity of this multicast LB message and the MEG ID TLV in this multicast LB message mate with the Configuration Values that receives bridge port, if this LB message is effective and MEG ID TLV and the Configuration Values coupling that receives bridge port, generate a LBR message according to loaded information in the multicast LB message, and be sent to the MEP that sends this multicast LB message.
Loopback purpose maintenance point generate LBR message process can for: loopback purpose maintenance point all is copied into each territory in its multicast LB message that receives in the LBR message, and source MAC in the LBR message and target MAC (Media Access Control) address exchanged, the mac address information of this maintenance point is write source MAC in the LBR frame, and operation code field becomes LBR from LBM.
All TLV in the LB message packets comprise that the TLV of this multicast of sign LB sender of the message MEP has been suffered by the complete LBR message that is mapped to like this, and except source MAC, the maintenance point that sends LBR message does not need to provide any other information to MEP.
If the MPID of the loopback purpose maintenance point that the maintenance point that receives this multicast LB message carries in determining this multicast LB message is inequality with the MPID that himself disposes, determine that then this maintenance point is not a loopback purpose maintenance point, need to continue to judge whether the mac address information of the source MAC address information and this maintenance point self of carrying in this multicast LB message is identical, if it is identical, then determine this maintenance point for sending the MEP of this multicast LB message, this maintenance point abandons this multicast LB message; If source MAC address information of carrying in the multicast LB message and the mac address information of this maintenance point self are inequality, determine that then this maintenance point is not for sending the MEP of multicast LB message, be MIP, this MIP does not receive multicast LB message to it and carries out any processing, and continues to transmit this multicast LB message.
In the sequence number retention time of appointment, receive the LBR message of normally returning if send the MEP of this multicast LB message, this MEP checks whether the validity of LBR message and the MEG IDTLV in this LBR packet mate with the Configuration Values that receives bridge port, if this LBR is effective and MEG ID TLV and the Configuration Values coupling that receives bridge port, then this LB success; If timer expiry up to the sequence number retention time of this appointment, the MEP that sends LB message does not still receive the LBR message of normally returning, then determine this LB failure, MEP can re-construct multicast LB message and carry out loopback test, or directly there is fault in report network.
Though described the present invention by embodiment, those of ordinary skills know, the present invention has many distortion and variation and do not break away from spirit of the present invention, and the claim of application documents of the present invention comprises these distortion and variation.
Claims (10)
1, a kind of implementation method of loopback is used for Ethernet, it is characterized in that, comprising:
A, the identification information of each maintenance point in the network is set;
B, maintaining end point are carried on the identification information of loopback purpose maintenance point in the multicast loopback message, send;
C, receive each maintenance point of described loopback message, if with described loopback message in the Maintenance Point Identification information matches of carrying, then with the source address of described loopback message as destination address, send the loopback response message.
2, the implementation method of a kind of loopback as claimed in claim 1 is characterized in that, described maintenance point is: Maintenance Intermediate Point, or maintaining end point and Maintenance Intermediate Point.
3, the implementation method of a kind of loopback as claimed in claim 1 is characterized in that, the identification information of described each maintenance point has nothing in common with each other.
4, the implementation method of a kind of loopback as claimed in claim 1 is characterized in that, described step b specifically comprises:
In loopback message, increase the TLV field;
Described maintaining end point is carried on the identification information of loopback purpose maintenance point in the TLV field of described increase, and sends described multicast loopback message.
5, as the implementation method of the described a kind of loopback of arbitrary claim in the claim 1 to 4, it is characterized in that described step c specifically comprises:
When the Maintenance Point Identification information that the maintenance point that receives described multicast loopback message carries is identical, determine that it is loopback purpose maintenance point in the Maintenance Point Identification information of determining himself and described multicast loopback message;
Described loopback purpose maintenance point produces the loopback response message, and its address information is carried in the described loopback response message is sent to described maintaining end point.
6, the implementation method of a kind of loopback as claimed in claim 5 is characterized in that, described step c also comprises:
When inequality the and maintenance point that receive described multicast loopback message of the Maintenance Point Identification information that the maintenance point that receives described multicast loopback message carries is Maintenance Intermediate Point, continue to transmit its described multicast loopback message that receives in the Maintenance Point Identification information of determining himself and described multicast loopback message.
7, the implementation method of a kind of loopback as claimed in claim 5 is characterized in that, described step c also comprises:
When the source address information that the maintenance point that receives described multicast loopback message carries is identical, determine that it is the maintaining end point of the described loopback message of transmission in the address information of determining himself and described multicast loopback message, abandon described multicast loopback message.
8, as the implementation method of the described a kind of loopback of arbitrary claim in the claim 1 to 4, it is characterized in that described method also comprises:
The maintaining end point of described transmission multicast loopback message judges whether to receive the loopback response message in the interval at the fixed time;
If described maintaining end point receives the loopback response message in the interval at the fixed time, determine this loopback success;
If described maintaining end point does not receive the loopback response message in the interval at the fixed time, determine this loopback failure.
9, the implementation method of a kind of loopback as claimed in claim 8 is characterized in that:
Described maintaining end point reports fault message or resends described loopback message when determining this loopback failure.
10, the implementation method of a kind of loopback as claimed in claim 5 is characterized in that, described address information comprises: Media Access Control address information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100646734A CN100536409C (en) | 2005-04-19 | 2005-04-19 | Round trip method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100646734A CN100536409C (en) | 2005-04-19 | 2005-04-19 | Round trip method |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007101530630A Division CN101166125A (en) | 2005-04-19 | 2005-04-19 | A loop realization method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1855850A CN1855850A (en) | 2006-11-01 |
| CN100536409C true CN100536409C (en) | 2009-09-02 |
Family
ID=37195710
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100646734A Expired - Fee Related CN100536409C (en) | 2005-04-19 | 2005-04-19 | Round trip method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100536409C (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101170458B (en) * | 2007-11-27 | 2011-04-20 | 中兴通讯股份有限公司 | Ethernet OAM remote loop method |
| CN102984019B (en) * | 2011-09-02 | 2016-01-27 | 华为技术有限公司 | Ethernet Loopback method of testing and equipment |
| CN102291266A (en) * | 2011-09-13 | 2011-12-21 | 中兴通讯股份有限公司 | Loopback (LB) detection method and device |
| CN102739448A (en) * | 2012-06-28 | 2012-10-17 | 华为技术有限公司 | Method, device and system for transmitting messages |
| ES2617974T3 (en) | 2013-06-17 | 2017-06-20 | Huawei Technologies Co., Ltd. | MEP configuration method and network device |
| CN104348678B (en) * | 2013-08-05 | 2018-10-30 | 华为技术有限公司 | Ethernet performance measurement method, apparatus and system |
| CN117527637B (en) * | 2023-12-29 | 2024-04-02 | 摩尔线程智能科技(北京)有限责任公司 | Method and device for detecting link failure, storage medium and electronic equipment |
-
2005
- 2005-04-19 CN CNB2005100646734A patent/CN100536409C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN1855850A (en) | 2006-11-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100536409C (en) | Round trip method | |
| US7697440B2 (en) | Scalable selective alarm suppression for data communication network | |
| US20190222496A1 (en) | Oam mechanisms for evpn active-active services | |
| CN101442502B (en) | Method, apparatus and system for monitoring session based on multicast technology | |
| CN1992707B (en) | Fast restoration method of multicast service and network apparatus | |
| CN101094121B (en) | Method, system and device for detecting Ethernet links among not direct connected devices | |
| CN1992651B (en) | Implementation method for detecting multicast performance of Ethernet | |
| CN108632099B (en) | Fault detection method and device for link aggregation | |
| CN100442706C (en) | Method for making maintaining node labels to match with media visiting controlled addresses | |
| US11139995B2 (en) | Methods and router devices for verifying a multicast datapath | |
| CN107295428A (en) | A kind of register method of optical network unit, device and optical line terminal | |
| CN102244609A (en) | Method for preventing flow interruption caused by failover during access of VPLS (virtual private LAN service) to L3 (network layer 3) and router | |
| CN101166125A (en) | A loop realization method | |
| CN1829191A (en) | Method for realizing FEC bidirectional forwarding detection | |
| CN102957620A (en) | Equipment and method for management of MAC (media access control) address table entries in TRILL (transparent interconnection of lots of links) network | |
| CN106375211B (en) | Exchange data processing method and interchanger in VRRP load-balancing scenario | |
| CN107612738B (en) | The uplink traffic fast switching system and method for VPLS dual-homed service model | |
| JP2012529201A (en) | Address refresh method and system | |
| RU2389146C2 (en) | System for passive propagation and suppression of alarm signal for packet switched networks | |
| CN104468158B (en) | The method and apparatus of state advertisement between a kind of node | |
| CN102404171A (en) | Method and device for detecting Ethernet links | |
| CN102158395A (en) | Device and method for processing neighbor discovery items of router | |
| CN101237319A (en) | Time synchronization method in Ethernet ring network and Ethernet ring system | |
| CN101997724A (en) | Method and device for updating multicast forwarding entries | |
| CN106341297B (en) | Networking method and device for monitoring ring network |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20180426 Address after: London, England Patentee after: GW partnership Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. Effective date of registration: 20180426 Address after: California, USA Patentee after: Global innovation polymerization LLC Address before: London, England Patentee before: GW partnership Co.,Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090902 |