CN105991329B - Method for the diagnosis of L2VPN business - Google Patents
Method for the diagnosis of L2VPN business Download PDFInfo
- Publication number
- CN105991329B CN105991329B CN201510080404.0A CN201510080404A CN105991329B CN 105991329 B CN105991329 B CN 105991329B CN 201510080404 A CN201510080404 A CN 201510080404A CN 105991329 B CN105991329 B CN 105991329B
- Authority
- CN
- China
- Prior art keywords
- l2vpn
- business
- l2vpn business
- request message
- responds
- 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
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a kind of methods for the diagnosis of L2VPN business comprising: the first PE constructs L2VPN business and responds request message；The L2VPN business, which is sent, to the 2nd PE responds request message；The L2VPN business received from the 2nd PE responds response message.The L2VPN business responds request or response message includes target L2VPN Business Entity TLV, may also include routing tracking TLV and L2VPN type of service TLV.2nd PE verifies L2VPN business and responds request message；And according to the target type in target L2VPN Business Entity TLV, update L2VPN business and respond request message, it forwards updated L2VPN business to respond request message and/or return to L2VPN business and responds response message.This programme is able to verify that the availability of long-range L2VPN Business Entity and the correct binding of L2VPN Business Entity and MPLS service label.
Description
Technical field
The present invention relates to MPLS networks, more particularly, to the method for being used for the diagnosis of L2VPN business in an mpls network.
Background technique
2 Virtual Private Network (L2VPN:Layer of layer on existing long-range pseudo-wire (PW:PesudoWire) endpoint of verifying
2Virtual Private Network) Business Entity availability and by these L2VPN Business Entities data path
Availability solution include defined in RFC4379 label switched path (LSP:Label Switch Path)
The Virtual Circuit Connectivity that PING/ routes defined in tracking or RFC 5085 verifies (VCCV:Virtual Circuit
Connectivity Verification) or RFC 6136 in defined L2VPN Operations,Administration And Maintenance (OAM:
Operation, Administration and Maintenance).It is real that all these schemes may only all verify L2VPN business
A part of body, one is be able to verify that the in all aspects of L2VPN Business Entity.
Fig. 1 (A) and Fig. 1 (B) respectively illustrates the schematic diagram of basic VPWS Business Entity and the VPWS industry for PW exchange
The schematic diagram of entity.Fig. 2 shows the schematic diagrames of the conceptual model of VPLS Business Entity.LSP PING/ is routed and is tracked
Tool, if service label binding needs to be verified, LSP responds request/response message and hands over both for multiprotocol label
Change (MPLS:Multi-Protocol Label Switching) label stack or vpn label (also known as PW label or business mark
Label).However, LSP PING/ route tracing utility can not even if LSP PING/ route tracing utility is bound to PW label
Directly verify L2VPN Business Entity.For example, to Virtual Private LAN Service (VPLS:Virtual Private Local
Area Network Service) Business Entity for, LSP PING/ route tracing utility can not verify virtual bridged example
Whether it is set correctly.
There are three types of Connectivity Verification (CV:Connectivity Verification) types of type for VCCV tool at present:
It is Internet Control Message Protocol (ICMP:Internet Control Message Protocol) PING, LSP PING, double
BFD (Bi-directional Forwarding Detection) is detected to forwarding, wherein BFD defines several CV types.Institute
These having all are not properly suited for verifying L2VPN Business Entity.
RFC 6136 defines the demand and frame of the L2VPN OAM of standard compliant Ethernet service OAM framework, such as exists
IEEE 802.1Q (2011) clause 19 (connection error management physical operation), ITU-T recommend Y.1731 (07/2011) (based on
The too OAM(Operation Administration Maintenance) and mechanism of network) and 10.3 (the 3rd rank of Ethernet service attribute of MEF (Metro Ethernet Forum) technical specification
Section) in defined.However, the emphasis of all these specifications is test Ethernet transmission services, none specification is considered
Combination between Ethernet service entity and bottom transmission mechanism.RFC 6136 and its related mechanism do not relate to how to verify
The availability of long-range L2VPN Business Entity, correct binding and L2VPN between L2VPN Business Entity and MPLS service label
The problem of data path of business packet.
The data path of L2VPN traffic packets, which refers to, traverses all service nodes for participating in L2VPN business, all to be not involved in
The node of business is not within limit of consideration.That is, the fortune of only operation VPLS or VPLW Business Entity and termination PWs
Edge (PE:Provider Edger) node of doing business is counted as L2VPN service node, common operator (P:
Provider) node is not counted as L2VPN service node.
Therefore, the data that service availability and L2VPN traffic packets are verified currently without suitable diagnostic tool are logical
Road, L2VPN business include VPLS and virtual private line service (VPWS:Virtual Private Wire Service).
Invention defines the methods diagnosed for L2VPN business comprising for L2VPN business PING and routing with
Two new informations of track tool: the L2VPN business that L2VPN business responds request sum responds response message.When by request message and
When response message is applied to the L2VPN Business Entity on PE, L2VPN business PING tool can be used to verify L2VPN business
The availability of all Business Entities or specific transactions entity, and return to the system address of corresponding PE.L2VPN business routing tracking work
Tool can be used to disclose the data path of all Business Entities or specific transactions entity that reach L2VPN business, that is, reach by road
By the system address of all L2VPN service nodes on the path of the L2VPN Business Entity tracked.
Summary of the invention
According to it is above-mentioned to background technique and understanding, if it is possible to provide a kind of for L2VPN
The method of business diagnosis, will be very useful.
According to the first aspect of the invention, a kind of method for the diagnosis of L2VPN business is provided, the method includes
The following steps executed by the first PE: A. constructs L2VPN business and responds request message；B. the L2VPN industry is sent to the 2nd PE
Request message is responded in business；C. the L2VPN business received from the 2nd PE responds response message；Wherein, the L2VPN industry
It includes target L2VPN Business Entity TLV that request message is responded in business.
Advantageously, the target L2VPN Business Entity TLV defines the response L2VPN business and responds request message
The target type of L2VPN Business Entity is all L2VPN Business Entities or specific L2VPN Business Entity.
Advantageously, when the L2VPN business request information is for the routing tracking of L2VPN business, the L2VPN business is returned
Answering request message further includes tracking TLV for the routing of request, and the routing tracking TLV for request encodes described
L2VPN business responds request message from the first PE to the system address for terminating all PE that PE is passed through.
Advantageously, it further includes request L2VPN type of service TLV, the request that the L2VPN business, which responds request message,
L2VPN type of service TLV is used to request the L2VPN Business Entity type of the 2nd PE.
Advantageously, when the L2VPN business request information is used for L2VPN business PING, the L2VPN business is responded
Request message further includes request L2VPN type of service TLV, the request L2VPN type of service TLV for requesting the 2nd PE
L2VPN Business Entity type.
Advantageously, it further includes at least one of the following that the L2VPN business, which responds request message: version number, life
Deposit the time, reserved field, type of message, answer-mode, general error code, business particular error subcode, sender message handle,
Sequence number, sending time stamp and receiving time stamp.
According to the second aspect of the invention, a kind of method for the diagnosis of L2VPN business is provided, the method includes
The following steps executed by the 2nd PE: a. receives the L2VPN business response request message from the first PE, the L2VPN industry
It includes target L2VPN Business Entity TLV that request message is responded in business；B. it verifies the L2VPN business and responds request message；C. if
It is verified, determines that the L2VPN business responds whether request message is directed to itself；And d. is according to the target L2VPN
Target type in Business Entity TLV executes at least one in following steps: I. updates the L2VPN business and responds request
Message；II. updated L2VPN business is forwarded to respond request message；III. it returns to L2VPN business and responds response message.
Advantageously, when it includes L2VPN type of service TLV that the L2VPN business, which is responded in request message, the L2VPN
It also includes L2VPN type of service TLV that business, which responds response message, and the L2VPN business responds the L2VPN business in response message
It is any one of the following terms that type TLV, which defines type of service: VPWS type of service, VPLS type of service, general
L2VPN type of service, non-L2VPN type of service and no Business Entity.
Advantageously, described when it includes the routing tracking TLV for request that the L2VPN business, which responds request message,
It includes the routing tracking TLV for response that L2VPN business, which responds response message,.
Advantageously, the step b further include: the verification item in the L2VPN business response request message is verified, it is described to test
Card item includes at least one in version number, type of message, answer-mode, TTL value and TLV format；If in the verification item
Any one mistake, return L2VPN business respond response message and stop forwarding L2VPN business respond request message, wherein
It includes corresponding general error code that the L2VPN business, which responds response message,.
Advantageously, the step c further include: when the target type in the target L2VPN Business Entity TLV is all
L2VPN Business Entity；Or when the target type in the target L2VPN Business Entity TLV be specific L2VPN Business Entity simultaneously
And when the address matching of the address IPv4 therein and the 2nd PE, determine that the L2VPN business received responds request and disappears
Breath is for itself；Otherwise, it determines it is for itself that the L2VPN business received, which responds request message not,.
Advantageously, the step d further include: if the L2VPN business received is responded request message and is not directed to
Itself, update the L2VPN business response request message that the L2VPN business responds request message and forwarding is updated；
Advantageously, the step d further include: if described in the L2VPN business response request message received
Target type in target L2VPN Business Entity TLV is all L2VPN Business Entities, then returns to L2VPN business and respond response
Message；It updates the L2VPN business and responds request message；And the L2VPN business response request message that forwarding is updated.
Advantageously, the step d further include: when the target type in the target L2VPN Business Entity TLV is specific
When L2VPN Business Entity and the address matching of the address IPv4 therein and the 2nd PE, returns to L2VPN business and respond response
Message.
Advantageously, the step III includes: that i. building L2VPN business responds response message；And ii. passes through UDP
IPv4 returns to constructed L2VPN business and responds response message.
Advantageously, the step i further includes that the L2VPN business is responded the version in response message to be set as 1, message class
Type is set as 2, TTL and answer-mode is set as 1, and message handle, sequence number and the sending time stamp of sender are described in receive
L2VPN business is responded to be replicated in request message, and receiving time stamp responds request message according to the L2VPN business received
Date-time is filled.
Advantageously, the step I includes: the copy that the production L2VPN business responds request message；It will be in the copy
Ttl value reduce 1；If the copy includes the routing tracking TLV for request, in the routing tracking for request
The L2VPN business that end addition receives responds the system address and date-time of request message；The copy becomes institute
The L2VPN business of update responds request message.
Advantageously, if the step II includes: that the L2VPN business that is updated responds TTL in request message not equal to 0
Or the updated L2VPN business responds the PE that request message does not reach least significant end, forwards the updated L2VPN industry
Request message is responded in business.
Technical solution of the present invention be able to verify that long-range L2VPN Business Entity availability and L2VPN Business Entity and
The correct binding of MPLS service label, and show the system address and L2VPN industry for participating in the PE of L2VPN srvice instance
The data path of business grouping.
Detailed description of the invention
The following detailed description to non-limiting embodiment, other spies of the invention are read by referring to accompanying drawing
Sign, objects and advantages will become more apparent upon.
Fig. 1 (A) shows the schematic diagram of basic VPWS Business Entity；
Fig. 1 (B) shows the schematic diagram of the VPWS Business Entity for PW exchange；
Fig. 2 shows the schematic diagrames of the conceptual model of VPLS Business Entity；
Fig. 3 shows the schematic diagram of L2VPN business PING tool；
Fig. 4 shows the schematic diagram of L2VPN business route tracing utility；
Fig. 5 shows the schematic diagram that L2VPN business responds the format of request and response message；
Fig. 6 shows the schematic diagram of TLV and son-TLV format；
Fig. 7 (A) shows the schematic diagram that request message is responded for the L2VPN business of PING request；
Fig. 7 (B) shows the schematic diagram that response message is responded for the L2VPN business of PING response；
The L2VPN business that Fig. 8 (A) shows for routing tracking request responds the schematic diagram of request message；
The L2VPN business that Fig. 8 (B) shows for routing tracking response responds the schematic diagram of response message；
Run through different diagrams in the figure, same or similar appended drawing reference indicates the same or similar device (module)
Or step.
Specific embodiment
In the following detailed description of the preferred embodiment, reference is constituted to the appended attached drawing of present invention a part.Institute
Attached attached drawing, which has been illustrated by way of example, can be realized specific embodiment.Exemplary embodiment is not intended to
Exhaustive all embodiments according to the present invention.It is appreciated that without departing from the scope of the present invention, can use other
Embodiment can also carry out the modification of structure or logic.Therefore, it is below specific descriptions and it is unrestricted, and this
The range of invention is defined by the claims appended hereto.It should be noted that although describing this hair in attached drawing with particular order
The step of bright middle method, but this does not require that or implies must execute these operations in this particular order, or
It is to have to carry out operation shown in whole to be just able to achieve desired as a result, on the contrary, step described herein can change and hold
Row sequence.Additionally or alternatively, it is convenient to omit multiple steps are merged into step and executed by certain steps, and/or by one
A step decomposes dimension execution of multiple steps.
Central scope of the invention is the provision of a kind of for L2VPN business PING and route tracing utility method.It should
Method includes that transmission L2VPN business response request and L2VPN business respond response message.These message are all user data package associations
(UDP:User Datagram Protocol) data packet is discussed, UDP port number can be configured on each PE, or can be by
IANA (Internet Assigned Numbers Authority) distribution.
L2VPN business response request and L2VPN business response response message can carry various types of for various purposes
Type-Length Value (TLV:Type Length Value).Invention defines three kinds of TLV:
1) target L2VPN Business Entity TLV, it, which is defined, should respond to the L2VPN industry that L2VPN business responds request message
Entity.The present invention is that target L2VPN Business Entity defines two values: all L2VPN Business Entities, specific L2VPN industry
Entity (address IPv4 by running the PE of the specific L2VPN Business Entity is identified).
2) L2VPN type of service TLV, it be type of service is any one of the following terms that it, which defines type of service:
VPWS type of service, VPLS type of service, general L2VPN type of service, non-L2VPN type of service and without in Business Entity
Any one.Wherein the difference between VPWS type of service and VPLS type of service is as shown in fig 1 and 2.
3) routing tracking TLV encodes L2VPN business request information and owns from originating PE to what termination PE was passed through
The system address of PE.Routing tracking TLV will be sent back to originating PE in L2VPN business response message.
Message format definition
Fig. 5 shows the schematic diagram that L2VPN business responds the format of request and response message.Response request in Fig. 5 disappears
Breath and each domain responded in response message will be hereinafter described in detail, to better understand technical side of the invention
Case.
Version number: the version number for L2VPN business PING and the message format of route tracing utility.In the present invention,
Version number can be set to 1 it is not limited to 1.
Life span (TTL:Time To Live): being used to indicate, which allows L2VPN to service, responds request or response message warp
The maximum quantity (or hop count) for the L2VPN Business Entity crossed.If the value in the domain is reduced to zero, L2VPN service, which is responded, requests/
Response message must be dropped and terminate to forward.After each jump of L2VPN service entities, the value in the domain must decline 1.Its mesh
Be in order to ensure L2VPN service respond request/response message finally will be moved to end forwarding, even if in the topology of L2VPN business
It is middle that there are loop, (note: the topological loop in L2VPN business is usually as caused by incorrect business configuration, in normal condition
Under must avoid).The maximum value of TTL is 255, it means that the diagnostic message should be spread as far as possible.The minimum of TTL
Value is 1, it means that the diagnostic message should not exceed adjacent one hop distance of L2VPN Business Entity.
Retain: the domain can be arranged to 0 in the present invention.
Type of message: the domain identifies the type of L2VPN business diagnostic message, and value is as shown in such as table 1.
1 diagnostic message type of table
| Value | Meaning |
| 1 | L2VPN business responds request |
| 2 | L2VPN business responds response |
Answer-mode: the domain indicates that long-range PE sends back to the return path of the L2VPN business response response message of response.Example
Such as, answer-mode=1, which represents, passes through the response of IPv4UDP packet.In general, answer-mode 1 is sufficiently used for the diagnosis of L2VPN business.If
Other answer-modes are needed under special circumstances, which can extend.Answer-mode one that although the present invention defines only
Value, those skilled in the art should understand that be that the value of answer-mode is not limited to that, the value of any suitable answer-mode
Each fall within the scope of the present invention.
General error code: in this domain, long-range PE returns to general error code, and it is real that it is suitable for all types of business
Body.Invention defines general error codes as described in Table 2.It will be understood by those skilled in the art that general in table 2
Error code can extend according to actual needs.
2 general error code of table
| Value | Meaning |
| 0 | There is no mistake |
| 1 | Version number does not support |
| 2 | Type of message is not supported |
| 3 | Answer-mode is not supported |
| 4 | Receive the message of TTL=0 |
| 5 | TLV format error |
| 6 | Common message format mistake |
| 7 | Business particular error |
Business particular error subcode: in the domain, the long-range specific error code of PE answering service, it is suitable for specific transactions
Type, such as VPWS type or VPLS type.Invention defines the various businesses particular error subcodes as shown in table 3-7.
It will be understood by those skilled in the art that the wrong subcode in table 3-7 can extend according to actual needs.
The business particular error subcode of 3 VPWS Business Entity type of table
| Value | Meaning |
| 0 | Whole OK, Business Entity have initialized, and service label has been bound |
| 1 | General error |
| 2 | PW is not bound to access circuit or another PW |
The business particular error subcode of 4 VPLS Business Entity type of table
| Value | Meaning |
| 0 | Whole OK, Business Entity have initialized, and service label and virtual bridged example have been bound |
| 1 | General error |
| 2 | Virtual bridged example does not initialize or no and service label is correctly bound |
The business particular error subcode of the general L2VPN Business Entity of table 5
| Value | Meaning |
| 0 | Whole OK, Business Entity have initialized, and service label has been bound |
| 1 | General error |
The business particular error subcode of the non-L2VPN Business Entity of table 6
| Value | Meaning |
| 0 | Business Entity is not L2VPN, is not suitable for L2VPN business diagnostic tool |
The business particular error subcode of the not no Business Entity of table 7
| Value | Meaning |
| 0 | The Business Entity not being currently running, L2VPN business diagnostic tool are not applicable |
The message handle of sender: the domain is filled by the sender of L2VPN business response request message, and recipient does not do any
Change, returns as former state in L2VPN business response message.Sender can be used the value in this domain and disappear to match response and request
Breath.
Sequence number: the domain is arbitrarily set by the sender that L2VPN business responds request message, can be used for detecting answering for loss
Answer message.
Sending time stamp: the domain is when L2VPN business sends back and answers request message, according to the clock of sender with network
The date-time of time protocol (NTP:Network Time Protocol) format.
Receiving time stamp: the domain be when L2VPN business respond request message be received when, according to the clock of recipient with
The date-time of NTP format.
TLV: Fig. 6 shows the schematic diagram of TLV and son-TLV format.Length is the length of the codomain as unit of byte.
Codomain depends on type, it can make 4 octet boundary alignments with zero padding.TLV can also be nested in other TLV
Interior, in this case, the TLV being nested is referred to as sub- TLV.Sub- TLs has independent type and must 48 bit byte pair
Together.Top TLV for L2VPN business diagnostic message is recited in table 8.
Table 8 is used for the TLV of L2VPN business diagnosis
| Type | Meaning |
| 1 | Target L2VPN Business Entity |
| 2 | L2VPN Business Entity type |
| 3 | Routing tracking |
Target L2VPN Business Entity TLV
The value of target L2VPN Business Entity TLV is the sub- TLV as defined in table 9.
The sub- TLV of 9 target L2VPN Business Entity TLV of table
| Sub- TLV type | Length | Value | Meaning |
| 1 | 0 | It is empty | All L2VPN Business Entities |
| 2 | 4 | The address IPV4 | Specific L2VPN Business Entity type |
Target L2VPN Business Entity is to respond the essential TLV in request message in L2VPN business.
L2VPN Business Entity type TLV
L2VPN Business Entity type TLV is an optional TLV, can L2VPN business respond request message and
L2VPN business is responded to be presented in response message.It being presented if responded in request message in L2VPN business, its value must be 0,
To indicate that originating PE request-reply PE reports L2VPN Business Entity type.When terminating PE building L2VPN business response message,
Based on whether there is a kind of L2VPN Business Entity type TLV (value=0) in the L2VPN business request information received, determine
It whether include L2VPN Business Entity type TLV.The L2VPN Business Entity type reported can be one in the value in table 10
It is a.(note: between VPWS Business Entity and VPLS Business Entity the difference is that whether there is one in L2VPN Business Entity
Virtual bridged example).It will be understood by those skilled in the art that the L2VPN Business Entity type in table 10 can basis
It is actually needed and extends.
10 L2VPN Business Entity type of table
| Value | Meaning |
| 0 | L2VPN Business Entity type requests |
| 1 | VPWS |
| 2 | VPLS |
| 3 | General L2VPN |
| 4 | Non- L2VPN Business Entity, for example, L3VPN |
| 5 | There is no Business Entity, for example, service label with any Business Entity without binding |
General L2VPN (the L2VPN Business Entity types of value=3) refer to L2VPN Business Entity be not yet fixed (or certainly
It is fixed) it is point-to-point or multiple spot L2VPN type of service special circumstances, it can support point-to-point and point multipoint message traffic.For reality
Existing general L2VPN Business Entity, the VPLS Business Entity that implementer simply can always be started using instances of virtual bridges, or
Person can enable or disable virtual bridged example according to the Number dynamics of current adjunct circuit, to save hardware resource (such as
The virtual bridged example starting of fruit, more hardware resources can be consumed).The present invention indicates such general L2VPN using types value 3
Service type.
Routing tracking TLV
Routing tracking TLV is an optional TLV, it is for tracking L2VPN business request information from originating PE to end
The only path of PE and associated timestamp information.Routing tracking TLV can respond business request information in L2VPN simultaneously and answer
It answers in message and presents.The presence of the TLV responds whether request message is intended for L2VPN business for determining L2VPN business
PING operation or L2VPN routing tracking operation.
The sub- TLV of the value of the routing tracking of table 11 TLV
| Sub- TLV type | Length | Value |
| 1 | 12 multiple | The address IPv4 and timestamp |
Codomain is a 12 byte list items, each includes the address the IPv4 subitem of 4 bytes and the timestamp of 8 bytes
Subitem.The system address that subitem record in the address IPv4 responds the PE of request message for receiving L2VPN business, as reception L2VPN
When business responds response message, timestamp subitem is according to the clock of PE with the NTP format record date time.
If originating PE is intended to activate L2VPN business route tracing utility, it should service in L2VPN and respond request message
In include routing tracking TLV, value may include the address IPv4 and timestamp.The address IPv4 is the system address of originating PE, time
Stamp is the day of NTP format when L2VPN business is responded request message (identical with the sending time timestamp value in Fig. 5) and sent
Time phase.When receiving, there is the L2VPN business of routing tracking TLV to respond request message, each downstream PE should be by additional
The address IPv4 and timestamp respond request message to update L2VPN business to indicate its system address and date-time existing
L2VPN business is received on some routing tracking TLV (and decremented TTL values) and responds request message, is then broadcasted in normal layer 2
The L2VPN business of update is forwarded to respond request message in frame.
The operation of L2VPN business PING and route tracing utility
Fig. 3 shows the schematic diagram of L2VPN business PING tool, and Fig. 4 shows L2VPN business route tracing utility
Schematic diagram.L2VPN business PING is similar with the operation of routing tracking.For both, originating PE sends L2VPN industry
Business responds request message and the L2VPN business replied from response PE is waited to respond response message.L2VPN business responds request and disappears
Breath is transmitted along the data path of 2 layers of broadcast frame, as long as therefore TTL value it is sufficiently large, can reach L2VPN business owns
PEs.Whether the target that each PE being traversed has to check for L2VPN business response request message is directed to oneself.If it is not,
The L2VPN business responds request message and is first updated (ttl value decline 1；L2VPN business is routed and is tracked, routing tracking TLV
It is added new routing and timestamp information), the L2VPN Business Entity in all downstreams is then forwarded to (or if for all
L2VPN Business Entity target, reaches last PE, then stops forwarding；Or it for specific L2VPN Business Entity target, arrives
Specific PE is reached)；(it is for PE itself), in addition to updating and forwarding L2VPN business that L2VPN business, which responds request message, for other
Request message is responded, PE should reply L2VPN business and respond request message.Ttl value is for preventing in L2VPN topological structure
Endless loop in the case where error configurations.
L2VPN business PING and route tracing utility respond the different-format of request and response message using L2VPN business,
Fig. 7 (A) and Fig. 7 (B) shows the schematic diagram that request and response message are responded for the L2VPN business of PING comprising essential
Target L2VPN Business Entity TLV and optional L2VPN Business Entity type TLV.Fig. 8 (A) and Fig. 8 (B) show use
The schematic diagram of request and response message is responded in the L2VPN business of routing tracking comprising essential target L2VPN Business Entity
TLV, routing tracking TLV and optional L2VPN Business Entity type TLV.
L2VPN business responds request message and response message is all encapsulated in UDP message packet.UDP port number can be used
Proprietary (Vendor proprietary) value of supplier is locally configured on each PE, or is disclosed by IANA and distribute and have complete
Ball interoperability.Udp port is known as the port L2VPN business PING in the present invention.
For L2VPN service request packet, the address Target IP v4 is arranged to any address IPv4 in 127/8 range,
The address source IP v4 is arranged to the system address of originating PE.Target UDP port number is arranged to L2VPN business PING port numbers；
Source udp port is arbitrarily set by originating PE.Response message is responded for corresponding L2VPN business, the address Target IP v4 is set
It is set to and receives the source IP address that L2VPN business responds request packet, source IP address is arranged to the system address of response PE.Target
UDP port number is arranged to receive the udp port that L2VPN business responds request packet, and source UDP port number is arranged to L2VPN
The port business PING.
L2VPN business responds request packet along the data path transmission of 2 layers of broadcast frame, to reach L2VPN business reality
All L2VPN entities in example.Guaranteeing does not have loop in L2VPN data path be the responsibility of operator.L2VPN industry in order to prevent
Request endless loop in the L2VPN topological structure of error configurations is responded in business, and each L2VPN business responds request and is limited to ttl value
(maximum ttl value is 255).
The operation of originating PE
When above-mentioned L2VPN business responds request message and business responds response message for the diagnosis of L2VPN business,
The following steps that originating PE executes: building L2VPN business responds request message；The L2VPN business is sent to other PE to respond
Request message；The L2VPN business received from other PE responds response message.The L2VPN business responds request and disappears
Breath includes target L2VPN Business Entity TLV.Wherein, originating PE is also considered the first PE.Specifically, in detail below
Describe the operation of originating PE according to an embodiment of the present invention.
(1) the originating PE building L2VPN business to be sent responds request message.Wherein, version number can be 1, type of message
=1, the input of the value of answer-mode=1, TTL from administrator.Reserved field, general error code and business particular error
Code both is set to 0.The message handle of sender is for matching response and request message, it can set in different ways
Set, for example, when new continuous L2VPN business is responded request message group and is sent, it can be set to one it is new random
Number.Sequence number can also be arranged in different ways for detecting the response message missed, for example, it can be set
It is 1,2,3 ..., for responding the message handle of each continuous meassage same sender in request message group in L2VPN business
Value.Timestamp, which is sent, is arranged to send the date-time that L2VPN business responds request message (with NT format).Timestamp receives
It is set as 0.
(2) the target L2VPN Business Entity TLV for L2VPN business PING and route tracing utility is essential.According to
The input of administrator, the value of L2VPN Business Entity TLV can be set to Class1-TLV (all L2VPN Business Entities) or
2 son-TLV of type (specific L2VPN Business Entity).
L2VPN Business Entity type TLV for L2VPN business PING and route tracing utility is optional.If necessary
L2VPN Business Entity type is reported, it should include L2VPN type of service TLV that L2VPN business, which responds request message, be worth=0 type
TLV.Otherwise, L2VPN Business Entity type TLV should not exist in L2VPN business request information.
For L2VPN business route tracing utility, routing tracking TLV is strong essential, but cannot be used in L2VPN business
In PING tool.When administrator has invoked L2VPN service routing trace tool, PE must respond request message in L2VPN business
In include routing tracking TLV.Routing tracking TLV must contain only a pair of of address IPv4 and timestamp, and IPv4 is the system of PE
Address, timestamp are the date-times (identical value such as in timestamp sending domain) for sending L2VPN business and responding request message.
Constructed L2VPN business is responded request message and is encapsulated in UDPIPv4 packet.
(3) originating PE sends constructed L2VPN business and responds request message packet to being bound to L2VPN Business Entity
All PW.
The case where tracking for all L2VPN Business Entities by PING or by routing, all PE for participating in L2VPN business are returned
Multiple L2VPN business responds response message.The case where being tracked for only special L2VPN Business Entity by PING or by routing, only
There is the PE being specifically directed to that can reply business and respond response message, every other PE only simply updates and forwards L2VPN business
Respond response message, without response it.
If all L2VPN Business Entities in L2VPN business are by PING or the routing tracking that is considered, initial TTL value can
To be arranged to 255 (or by implementer be considered as any other sufficiently large number).If only L2VPN Business Entity
Part tracked by PING or by routing, ttl value can be set as 1,2,3 ..., for example, the L2VPN business of TTL=1 is returned
The L2VPN Business Entity for answering request message to jump PING or routing tracking all adjacent one.
When each PE, which receives L2VPN business by L2VPN business PING udp port, responds request message, verifying
L2VPN business respond request message in verification item, the verification item include version number, type of message, answer-mode, ttl value and
At least one of in TLV format.If any one of verification item mistake, such as ttl value are zero, return to L2VPN business and return
It answers response message and stops forwarding L2VPN business and respond request message, wherein the L2VPN business responds response message packet
Include corresponding general error code.
If PE should analyze the domain TLV without wrong (therefore type of message must be 1) in input message format.Class
Type 1TLV (target L2VPN Business Entity) be it is essential, the TLV of type 2 and 3 is optional.If in the L2VPN industry received
The format error for having any TLV (or sub- TLV) in request message is responded in business, and PE must return to 5 (format of general error code
Mistake TLVs) L2VPN business respond request message and stop forwarding L2VPN business respond request message.
After TLV verifying, PE should determine that the L2VPN business of input responds whether request message is directed to oneself.If
Meet following two condition: PE thinks that incoming L2VPN business responds request message for itself:
(1) value of target L2VPN Business Entity TLV is the sub- TLV (all L2VPN Business Entities) of type=1
(2) value of target L2VPN Business Entity TLV be type=2 sub- TLV (specific L2VPN Business Entity) and
The address of the address IPv4 and PE system itself in the sub- TLV of type 2 matches.
Otherwise, it is for PE itself that the L2VPN business of input, which responds request message not,.
Receive the operation of PE
When above-mentioned L2VPN business responds request message and business responds response message for the diagnosis of L2VPN business,
Receive L2VPN business and respond the following steps that the PE of request message is executed: the L2VPN business response received from the first PE is asked
Message is sought, it includes target L2VPN Business Entity TLV which, which responds request message,；Verify L2VPN business response
Request message；If the verification passes, determine that the L2VPN business responds whether request message is directed to itself；And according to mesh
The target type in L2VPN Business Entity TLV is marked, at least one in following steps is executed: updating the L2VPN business and responds
Request message；Updated L2VPN business is forwarded to respond request message；It returns to L2VPN business and responds response message.Wherein, it connects
The PE for receiving L2VPN business response request message is also believed to the 2nd PE.
Specifically, when receiving L2VPN business and responding request message, all other PE's other than originating PE
Operation is described below.
If it is for PE itself that the L2VPN business received, which responds request message not:
PE executes the program that request message is responded for updating L2VPN business；
PE executes the program for forwarding updated L2VPN business to respond request message.
If the L2VPN business received responds request message for all L2VPN Business Entities:
PE executes the program that response message is responded for returning to L2VPN business；
PE executes the program that request message is responded for updating L2VPN business；
PE executes the program for forwarding updated L2VPN business to respond request message.
Otherwise (it is for specific L2VPN Business Entity that the received L2VPN business of institute, which responds request message),
PE executes the program that response message is responded for returning to L2VPN business.
Update the program that L2VPN business responds request message
(1) the L2VPN business received is made first and responds the copy of request message, and following place is done to the message copy
Reason:
The ttl value of message copy is reduced 1 by PE；
If message copy includes that routing tracks TLV, PE adds the input message received in the end of routing tracking TLV
System address and date-time (such as with NTP format).
(2) the L2VPN business that message copy becomes updated responds request message.
Updated L2VPN business is forwarded to respond the program of request message
If the ttl value that the L2VPN business updated responds request message is zero, stop forwarding；
Otherwise, PE sends updated L2VPN business to all related PW and responds request message, just as 2 layers of broadcast
Frame is the same.That is, if having received original L2VPN business by spoke PW responds request (receiving before update
Message), the message updated should send (including spoke to all other PW in addition to input spoke PW (spoke PW)
With netted PW)；If having received original L2VPN business response by netted PW (PW for belonging to horizontal segmentation group) to ask
It asks (message received before update), the message updated should send (including spoke and netted to every other PWs
PWs), in addition to PWs and all PWs in the identical horizontal segmentation group for inputting netted PW.
Repeating process will stop in following any case: (a) ttl value is reduced to 0；(b) L2VPN business responds request
The PE of message arrival most downstream.
Return to the process that L2VPN business responds response message
The PE building L2VPN business to be sent responds response message.For example, version=1, type of message=2, L2VPN industry
Business, which is responded, does not use TTL and answer-mode in response message, can be set to 0.The message handle of sender, sequence number and when
Between stamp to send all be to respond in request message to replicate from the L2VPN business that receives.Timestamp receives domain by receiving
L2VPN business responds the date-time (with NTP format) of request message to fill.
CLI command for L2VPN business PING and route tracing utility
L2VPN PING and route tracing utility can be with command line interface (CLI:Command Line Interface)
Order realize.In the CLI of the PE in the context (context) of L2VPN srvice instance, administrator can be as follows with use-case
Order is stated to run L2VPN business PING tool: l2vpn-ping* | ip-address [l2vpn-type enable |
Disable] [hop hop-count], wherein " * | ip-address " it is essential CLI parameter, which specify target L2VPN
Business Entity.* all Business Entities are indicated, the address ip- indicates the specific objective L2VPN with particular system address on PE
Business Entity." l2vpn-type enable | disable " it is optional CLI parameter, it defines L2VPN Business Entity type
Information whether should report.If L2VPN-PING tool for all L2VPN Business Entities (L2VPN PING*),
Default value can be disabling；If L2VPN-PING tool is for specific L2VPN Business Entity (L2VPN PING IP
Location), default value can be enabling." hop hop-count " is optional CLI parameter, it defines the response of L2VPN business and asks
The initial TTL value of message is sought, TTL default value can be 255.
In another example l2vpn-ping*: it orders PING all with L2VPN type=disabling and hop count=255
The system address of L2VPN Business Entity, all PE for participating in L2VPN business will be shown.L2vpn-ping 10.1.2.3: its
Ordering system address of the PING on PE is 10.1.2.3, L2VPN type=enabling, the L2VPN Business Entity of hop count=255,
L2VPN Business Entity type and state will be shown.L2vpn-ping*hop 1: it orders all L2VPN type=taboos of PING
With the L2VPN Business Entity of hop count=1, that is to say, that its L2VPN Business Entity for ordering PING all adjacent one to jump.
In the CLI of PE, in the context of some L2VPN srvice instance, administrator can be with for example following order fortune of use-case
Row L2VPN business route tracing utility: l2vpn-traceroute* | ip-address [l2vpn-type enable |
Disable] [hop hop-count], wherein " * | ip-address ": it is essential CLI parameter, which specify target L2VPN
Business Entity.* mean all L2VPN Business Entities, ip-address refers to that specific, to be located at system address be ip-
Target L2VPN Business Entity on the PE of address." l2vpn-type enable | disable " it is optional CLI parameter,
It defines whether L2VPN Business Entity type information should be reported.Default value can be disabling."hop hop-count"
It is optional CLI parameter, which specify the initial TTL values that L2VPN business responds request message.TTL default value can be 255.
L2vpn-traceroute 10.1.2.3: it is ordered from originating PE to by system address 10.1.2.3, L2VPN type=disabling,
The routing for the PE tracking L2VPN business packet that hop count=255 are identified.
It is obvious to a person skilled in the art that invention is not limited to the details of the above exemplary embodiments, Er Qie
In the case where without departing substantially from spirit or essential attributes of the invention, the present invention can be realized in other specific forms.Therefore, no matter
How from the point of view of, the present embodiments are to be considered as illustrative and not restrictive.In addition, it will be evident that one word of " comprising " not
Exclude other elements and steps, and wording "one" be not excluded for plural number.The multiple element stated in device claim can also
To be implemented by one element.The first, the second equal words are used to indicate names, and are not indicated any particular order.
Claims (17)
1. a kind of method for the diagnosis of L2VPN business, the following steps that the method includes being executed by the first PE:
A. building L2VPN business responds request message；
B. the L2VPN business is sent to the 2nd PE respond request message；
C. the L2VPN business received from the 2nd PE responds response message；
Wherein the L2VPN business responds request message for L2VPN business routing tracking or is used for L2VPN business PING,
And including target L2VPN Business Entity TLV, wherein the target L2VPN Business Entity TLV defines the response L2VPN
The target type that business responds the L2VPN Business Entity of request message is that all L2VPN Business Entities or specific L2VPN business are real
Body.
2. the method according to claim 1, wherein responding request message when the L2VPN business is used for L2VPN
When business routing tracking, it further includes tracking TLV for the routing of request that the L2VPN business, which responds request message, described to be used for
The routing tracking TLV of request encodes the L2VPN business and responds what request message was passed through from the first PE to termination PE
The system address of all PE.
3. according to the method described in claim 2, it is characterized in that, it further includes request that the L2VPN business, which responds request message,
L2VPN type of service TLV, the request L2VPN type of service TLV are used to request the L2VPN Business Entity class of the 2nd PE
Type.
4. the method according to claim 1, wherein responding request message when the L2VPN business is used for L2VPN
When business PING, it further includes request L2VPN type of service TLV, the request L2VPN that the L2VPN business, which responds request message,
Type of service TLV is used to request the L2VPN Business Entity type of the 2nd PE.
5. method according to claim 1 to 4, which is characterized in that the L2VPN business responds request message
It further include at least one of the following: version number, life span, reserved field, type of message, answer-mode, general error
Code, business particular error subcode, the message handle of sender, sequence number, sending time stamp and receiving time stamp.
6. a kind of method for the diagnosis of L2VPN business, the following steps that the method includes being executed by the 2nd PE:
A. the L2VPN business received from the first PE responds request message, and the L2VPN business is responded request message and is used for
L2VPN business routing tracking is used for L2VPN business PING, and including target L2VPN Business Entity TLV；
B. it verifies the L2VPN business and responds request message；
C. if the verification passes, determine that the L2VPN business responds whether request message is directed to itself；And
D. request message is responded according to the response L2VPN business as defined in the target L2VPN Business Entity TLV
The target type of L2VPN Business Entity executes at least one in following steps:
I. it updates the L2VPN business and responds request message；
II. updated L2VPN business is forwarded to respond request message；
III. it returns to L2VPN business and responds response message.
7. according to the method described in claim 6, it is characterized in that, when including in L2VPN business response request message
When L2VPN type of service TLV, it also includes L2VPN type of service TLV, the L2VPN that the L2VPN business, which responds response message,
It is any one of the following terms: VPWS industry that the L2VPN type of service TLV that business responds in response message, which defines type of service,
Service type, VPLS type of service, general L2VPN type of service, non-L2VPN type of service and no Business Entity.
8. according to the method described in claim 6, it is characterized in that, responding request message when the L2VPN business includes being used for
When the routing of request tracks TLV, it includes the routing tracking TLV for response, the use that the L2VPN business, which responds response message,
The L2VPN business response request message is encoded in the routing tracking TLV of request to be passed through from the first PE to PE is terminated
All PE system address.
9. according to the method described in claim 6, it is characterized in that, the step b further include:
The verification item in the L2VPN business response request message is verified, the verification item includes version number, type of message, answers
Answer at least one of mode, ttl value and TLV format；
If any one of verification item mistake, returns to L2VPN business and respond response message and stop forwarding L2VPN industry
Request message is responded in business, wherein it includes corresponding general error code that the L2VPN business, which responds response message,.
10. according to the method described in claim 6, it is characterized in that, the step c further include:
When the target type in the target L2VPN Business Entity TLV is all L2VPN Business Entities；Or work as the target
Target type in L2VPN Business Entity TLV is specific L2VPN Business Entity and the address IPv4 therein and the 2nd PE
Address matching when, determine that the L2VPN business that receives responds request message for itself；
Otherwise, it determines it is for itself that the L2VPN business received, which responds request message not,.
11. according to the method described in claim 10, it is characterized in that, the step d further include:
If it is to update the L2VPN business for itself and respond that the L2VPN business received, which responds request message not,
The L2VPN business that request message and forwarding are updated responds request message.
12. according to the method described in claim 6, it is characterized in that, the step d further include:
If the L2VPN business received responds the target in the target L2VPN Business Entity TLV in request message
Type is all L2VPN Business Entities, then
It returns to L2VPN business and responds response message；
It updates the L2VPN business and responds request message；And
Updated L2VPN business is forwarded to respond request message.
13. according to the method described in claim 6, it is characterized in that, the step d further include:
When the target type in the target L2VPN Business Entity TLV for specific L2VPN Business Entity and IPv4 therein
When the address matching of location and the 2nd PE, returns to L2VPN business and respond response message.
14. the method according to any one of claim 7-13, which is characterized in that the step III includes:
I. building L2VPN business responds response message；And
Ii. constructed L2VPN business is returned to by UDPIPv4 and responds response message.
15. according to the method for claim 14, which is characterized in that the step i further includes responding the L2VPN business
Version in response message is set as 1, and type of message is set as 2, TTL and answer-mode is set as 1, message handle, the sequence number of sender
It responds in request message and replicates from the L2VPN business received with sending time stamp, receiving time stamp basis receives
The L2VPN business responds the date-time of request message to fill.
16. the method according to any one of claim 7-13, which is characterized in that the step I includes:
Make the copy that the L2VPN business responds request message；
Ttl value in the copy is reduced 1；
If the copy includes the routing tracking TLV for request, in the end addition of the routing tracking for request
The L2VPN business received responds the system address and date-time of request message, the routing tracking for request
TLV encodes the L2VPN business and responds request message from the first PE to terminating all PE that PE is passed through systematically
Location；
The L2VPN business that the copy becomes updated responds request message.
17. according to the method for claim 16, which is characterized in that the step II includes:
If the L2VPN business updated responds the TTL in request message not equal to 0 or the updated L2VPN business
The PE that request message does not reach least significant end is responded, the updated L2VPN business is forwarded to respond request message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510080404.0A CN105991329B (en) | 2015-02-13 | 2015-02-13 | Method for the diagnosis of L2VPN business |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510080404.0A CN105991329B (en) | 2015-02-13 | 2015-02-13 | Method for the diagnosis of L2VPN business |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105991329A CN105991329A (en) | 2016-10-05 |
| CN105991329B true CN105991329B (en) | 2019-09-03 |
Family
ID=57041526
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510080404.0A Active CN105991329B (en) | 2015-02-13 | 2015-02-13 | Method for the diagnosis of L2VPN business |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105991329B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110061926A (en) * | 2019-04-26 | 2019-07-26 | 武汉思创易控科技有限公司 | A kind of ping method, storage medium, the terminal and server of multiplexing |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102055619A (en) * | 2009-11-02 | 2011-05-11 | 中兴通讯股份有限公司 | Method and system for realize fault detection in bidirectional path segment |
| CN103067278A (en) * | 2013-01-30 | 2013-04-24 | 杭州华三通信技术有限公司 | Data frame transmission processing method, equipment and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9042369B2 (en) * | 2013-03-13 | 2015-05-26 | Alcatel Lucent | System and method for reflecting FEC route information |
-
2015
- 2015-02-13 CN CN201510080404.0A patent/CN105991329B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102055619A (en) * | 2009-11-02 | 2011-05-11 | 中兴通讯股份有限公司 | Method and system for realize fault detection in bidirectional path segment |
| CN103067278A (en) * | 2013-01-30 | 2013-04-24 | 杭州华三通信技术有限公司 | Data frame transmission processing method, equipment and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105991329A (en) | 2016-10-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10581732B2 (en) | Target FEC (forwarding equivalence class) stack based FEC query in segment routing environments | |
| US7599303B2 (en) | System and methods for sending trace messages | |
| US7808919B2 (en) | Network monitoring using a proxy | |
| US8605603B2 (en) | Route convergence based on ethernet operations, administration, and maintenance protocol | |
| US20160277239A1 (en) | Method and device for configuring and managing network element equipment, and network element equipment | |
| US8559318B2 (en) | Method, node and system for obtaining link aggregation group information | |
| US9059905B2 (en) | Methods and arrangements in an MPLS-TP network | |
| KR20100096086A (en) | Ip network and performance monitoring using ethernet oam | |
| US7839796B2 (en) | Monitor for multi-protocol label switching (MPLS) networks | |
| US9397913B1 (en) | Packet loss measurement in a distributed data plane | |
| US20140293798A1 (en) | Mpls-tp network and link trace method thereof | |
| WO2008109279A2 (en) | Analyzing virtual private network failures | |
| US8971195B2 (en) | Querying health of full-meshed forwarding planes | |
| CN103138955B (en) | Multiple igmp querying device is used in layer 2 network | |
| CN102870376B (en) | Interworking between ethernet and MPLS | |
| US11303549B2 (en) | Segmented traceroute for segment routing traffic engineering | |
| CN105991329B (en) | Method for the diagnosis of L2VPN business | |
| WO2017144946A1 (en) | Method and apparatus for legacy network support for computed spring multicast | |
| JP5913732B2 (en) | Pseudowire groups in packet switched networks | |
| US8355347B2 (en) | Creating multipoint-to-multipoint MPLS trees in an inter-domain environment | |
| CN103650453B (en) | The method communicated in path computation element communication protocol and network equipment | |
| US7944857B2 (en) | Method and system for deriving tunnel path information in MPLS networks | |
| CN106817273B (en) | Method and apparatus for L3VPN service diagnosis | |
| CN117857437A (en) | Method and device for determining backup path and nonvolatile storage medium | |
| Filsfils et al. | PERFORMANCE DELAY MEASUREMENT AND FAULT DETECTION OF SR/SRV6 TE POLICIES IN SOFTWARE DEFINED NETWORKS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 201206 Shanghai, Pudong Jinqiao Ning Bridge Road, No. 388, No. Applicant after: Shanghai NOKIA Baer Limited by Share Ltd Address before: 201206 Shanghai, Pudong Jinqiao Ning Bridge Road, No. 388, No. Applicant before: Shanghai Alcatel-Lucent Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |