CN106817273A - For the method and apparatus of L3VPN business diagnosis - Google Patents

For the method and apparatus of L3VPN business diagnosis Download PDF

Info

Publication number
CN106817273A
CN106817273A CN201510864379.5A CN201510864379A CN106817273A CN 106817273 A CN106817273 A CN 106817273A CN 201510864379 A CN201510864379 A CN 201510864379A CN 106817273 A CN106817273 A CN 106817273A
Authority
CN
China
Prior art keywords
l3vpn
business
l3vpn 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.)
Granted
Application number
CN201510864379.5A
Other languages
Chinese (zh)
Other versions
CN106817273B (en
Inventor
张立新
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Original Assignee
Alcatel Lucent Shanghai Bell Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alcatel Lucent Shanghai Bell Co Ltd filed Critical Alcatel Lucent Shanghai Bell Co Ltd
Priority to CN201510864379.5A priority Critical patent/CN106817273B/en
Publication of CN106817273A publication Critical patent/CN106817273A/en
Application granted granted Critical
Publication of CN106817273B publication Critical patent/CN106817273B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/10Active monitoring, e.g. heartbeat, ping or trace-route
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a kind of method and apparatus for the diagnosis of L3VPN business.The device is located in a PE, including:Construction unit, it is configured as building L3VPN business response request message;Transmitting element, it is configured as sending the L3VPN business response request message to the 2nd PE;And receiving unit, it is configured as receiving the L3VPN business response response message from the 2nd PE;Wherein, the L3VPN business responds request message includes target service entity TLV, and the L3VPN Business Entities that the L3VPN business responds request message should be responded for specifying.

Description

For the method and apparatus of L3VPN business diagnosis
Technical field
The present invention relates to the communications field, more specifically, it is related to a kind of for L3VPN business The method and apparatus of diagnosis.
Background technology
Currently, it is existing to be used for the Virtual Private Network of diagnostic horizon 3 (L3 Virtual Private Network, L3VPN) business instrument include RFC 4379 in defined tag changeable path In footpath (Label Switch Path, LSP) Ping/ route tracing utilities, or RFC 5085 Virtual Circuit Connectivity checking (the Virtual Circuit Connectivity of defined Verification, VCCV) tradition applied in instrument, or the context of L3VPN examples IP Ping/ route tracing utilities.Although each can be used for diagnosing the one of L3VPN business A little aspects, but they are all not enough to diagnose all main aspects of L3VPN business:L3VPN The state of Business Entity, service label allocation model and the industry for the distribution of L3VPN Business Entities The sum of business label and the data path of L3VPN traffic packets.
Here, the data path of L3VPN traffic packets refers to all participation L3VPN of traversal The service node of business, does not consider to be not involved in all nodes of business.That is, only transporting Row L3VPN Business Entities and terminate service label Provider Edge (Provider Edge, PE) node is seen as L3VPN service nodes, general operator (Provider, P) Node is not qualified as L3VPN service nodes.
For LSP Ping/ route tracing utilities, LSP responds the mesh of request/response message Mark is MPLS label stack.If MPLS label stack includes service label, service label Binding can be identified.However, LSP Ping/ route tracing utilities can not diagnose L3VPN industry Entity.
For VCCV instruments, current VCCV instruments have specified some to be used for ICMP (Internet Control Message Protocol, ICMP) Ping, LSP Ping and two-way converting detection (Bidirectional Forwarding Detection, BFD) Connection confirm (Connectivity Verification, CV) type, but they are not yet It is suitable for diagnosing L3VPN Business Entities.
IP Ping/ route tracing utilities can be used for verifying IP main frames in L3VPN environment Accessibility and path, but it is transparent for bottom MPLS label.Therefore IP Ping/ Route tracing utility can not be used for diagnosing all main aspects of L3VPN business.
As can be seen that VPN traffic entity is also verified without appropriate diagnostic tool so far Integrality and based on RFC 4364 Border Gateway Protocol (Border Gateway Protocol, BGP)/multiprotocol label switching (Multi-Protocol Label Switching, MPLS) IP VPN The data path of the traffic packets of business.
The content of the invention
For problem above, the present invention proposes a kind of for comprehensively carrying out L3VPN business The scheme of diagnosis.More specifically, the present invention proposes two kinds of diagnostic tools:L3VPN industry Business Ping instruments and L3VPN business route tracing utilities, and for both instruments are fixed respectively Justice diagnostic message newly, i.e. L3VPN business responds (Echo) request message and L3VPN Business responds response message.Wherein, when being applied to PE in L3VPN Business Entity environment When upper, L3VPN business Ping instruments can be used to verify L3VPN business all or one The availability of specific L3VPN Business Entities, and return corresponding PE system address (with And other service related informations), and L3VPN business route tracing utilities can be used for disclosing Lead to all or all possible data path for specific L3VPN Business Entities, i.e. Reach by all L3VPN service nodes on the path of the L3VPN Business Entities of route tracking System address.
According to the first aspect of the invention, there is provided it is a kind of for L3VPN business diagnosis Method, methods described includes the following steps performed by a PE:L3VPN business is built to return Answer request message;The L3VPN business is sent to the 2nd PE respond request message;And connect Receive the L3VPN business from the 2nd PE and respond response message;Wherein, the L3VPN Business responds request message includes target service entity TLV, for specify should respond it is described L3VPN business responds the L3VPN Business Entities of request message.
According to the second aspect of the invention, there is provided it is a kind of for L3VPN business diagnosis Method, methods described includes the following steps performed by the 2nd PE:Receive and come from a PE L3VPN business respond request message, the L3VPN business responds request message includes mesh Mark L3VPN Business Entity TLV, the L3VPN business response should be responded for specifying The L3VPN Business Entities of request message;Determine that the L3VPN business responds request message Target is all L3VPN Business Entities or a specific L3VPN Business Entity;Work as institute It is described when the target for stating L3VPN business response request message is all L3VPN Business Entities 2nd PE returns to L3VPN business and responds response message to a PE, updates described L3VPN business responds request message and forwards the L3VPN business after updating to respond request and disappears Breath;And when the target that the L3VPN business responds request message is one specific L3VPN Business Entities and when the 2nd PE is the specific L3VPN Business Entities, 2nd PE returns to L3VPN business and responds response message to a PE.
According to the third aspect of the present invention, there is provided it is a kind of for L3VPN business diagnosis Device, the device is located in a PE, including:Construction unit, it is configured as building L3VPN Business responds request message;Transmitting element, it is configured as sending the L3VPN to the 2nd PE Business responds request message;And receiving unit, it is configured as receiving from described second The L3VPN business of PE responds response message;Wherein, the L3VPN business responds request Message includes target service entity TLV, and the L3VPN business time should be responded for specifying Answer the L3VPN Business Entities of request message.
According to the fourth aspect of the present invention, there is provided it is a kind of for L3VPN business diagnosis Device, described device is located in the 2nd PE, including:Receiving unit, it is configured as receiving L3VPN business from a PE responds request message, and the L3VPN business is responded please Seeking message includes target L3VPN Business Entity TLV, for specify should respond it is described L3VPN business responds the L3VPN Business Entities of request message;Determining unit, it is configured To determine that the target that the L3VPN business responds request message is all L3VPN Business Entities Or a specific L3VPN Business Entity;And processing unit, it is configured as institute When the target for stating L3VPN business response request message is all L3VPN Business Entities, to institute State a PE and return to L3VPN business response response message, update the L3VPN business and return Answer request message and forward the L3VPN business after updating to respond request message;And work as institute State L3VPN business respond request message target be a specific L3VPN Business Entity simultaneously And the 2nd PE is when being the specific L3VPN Business Entities, returned to a PE L3VPN business responds response message.
Brief description of the drawings
By the description below with reference to the specific embodiment of the invention given by drawings below Afterwards, be better understood with the present invention, and other objects of the present invention, details, feature and Advantage will become apparent.In the accompanying drawings:
Fig. 1 shows the general deployment mould of the BGP/MPLS L3VPN based on RFC 4364 The schematic diagram of type;
Fig. 2 shows the signal of the operation of L3VPN business Ping instruments of the invention Figure;
Fig. 3 shows the operation of L3VPN business route tracing utility of the invention Schematic diagram;
Fig. 4 shows that L3VPN business of the invention responds request with response message The schematic diagram of form;
Fig. 5 is shown in L3VPN business response request of the invention and response message TLV and son-TLV fields form schematic diagram;
Fig. 6 A and Fig. 6 B respectively illustrate the L3VPN for L3VPN business Ping instruments Business responds request message and L3VPN business responds the schematic diagram of response message;
Fig. 7 A and Fig. 7 B are respectively illustrated for L3VPN business route tracing utilities L3VPN business responds request message and L3VPN business responds the schematic diagram of response message;
Fig. 8 shows the square frame of the device for the diagnosis of L3VPN business of the invention Figure;
Fig. 9 shows another device for the diagnosis of L3VPN business of the invention Block diagram.
Specific embodiment
The preferred embodiment of the present invention is more fully described below with reference to accompanying drawings.Although attached The preferred embodiment of the present invention is shown in figure, however, it is to be appreciated that can be in a variety of manners Realize the present invention without that should be limited by embodiments set forth herein.Conversely, there is provided these realities The mode of applying be in order that the present invention is more thorough and complete, and can be complete by the scope of the present invention Whole conveys to those skilled in the art.
Before basic thought of the invention is described, L3VPN business models are first looked back to introduce The necessary concept of some of and term.Fig. 1 shows the BGP/MPLS based on RFC 4364 The schematic diagram of the general deployment model of L3VPN.
Generally, distributed L3VPN business can be seen as one group of virtual flow-line and forwarding (Virtual Routing and Forwarding, VRF) example, it passes through business between VRF Transmitting path is interconnected.L3VPN topology by export (Export) route target (Route Target, RT) controlled with the setting of input (Import) RT, wherein output RT is bgp protocol The extended community attribute of the L3VPN routes distributed, and be input into RT and then control each VRF The L3VPN of input is allowed to route, this further determines whether VRF should be input L3VPN routes are re-distributed to other reciprocity VRF.L3VPN routes redistribution rule can be with Described by the concept of horizontal segmentation group (Split Horizon Group).Industry between VRF Business transmitting path (or equivalently, L3VPN business equity end) multiple can be grouped into The L3VPN of input will not be route redistribution to same level by horizontal segmentation group, VRF Other business equity end in segmentation group, and always the L3VPN route redistributions of input are arrived Other business equity end in varying level segmentation group.How business between a VRF is transmitted Path (or a L3VPN business equity end) is assigned to the rule of specific horizontal segmentation group Value only by being input into RT and output RT determines.Due to the rule (or algorithm) be not it is new, Therefore the present invention will not be described in detail, and be just assumed that each VRF and one or more automatic wounds The horizontal segmentation group built is associated, and the topology of L3VPN business is controlled by these horizontal segmentation groups System, and business transmitting path (or each L3VPN business equity end) between every VRF Clearly belong to a horizontal segmentation group.The related horizontal segmentation of the topological sum of L3VPN business Group is as shown in fig. 1.
Note, herein, based on context, horizontal segmentation group can refer to business transmission path Footpath group or L3VPN business peer-groups.
Assuming that the topology (or two-way L3VPN route distributions path) of L3VPN business The control of the horizontal segmentation group by being associated with VRF, invention proposes two kinds of L3VPN industry Business diagnostic tool:L3VPN business Ping instruments and L3VPN business route tracing utilities, and And describe the message coding of correlation and realize algorithm.
It is proposed that being L3VPN business Ping instruments and L3VPN business route tracking work Tool defines two kinds of message:L3VPN business responds request message and L3VPN business responds response Message.These message are by UDP (User Datagram Protocol, UDP) Packet bearer, UDP port number can be manually configured on each PE, or can be by mutual Networking number assignment mechanism (Internet Assigned Numbers Authority, IANA) point Match somebody with somebody.
Note:The present invention is that same inventor diagnoses for layer 2VPN (L2VPN) business The extension of the application No.2015100804040 of proposition, therefore the message before its partial reuse Coding and algorithm.However, due to the characteristics of L2VPN and L3VPN have respective, e.g. It is no based on route etc., therefore the two is suitable for the solution of different application scene.
L3VPN business responds request message and L3VPN business is responded response message and can be taken Band all kinds-Length Value (Type-Length-Value, TLV) for various purposes.This Invention suggestion reuse before for L2VPN two kinds of TLV and define two kinds it is new only Suitable for the TLV of L3VPN business Ping/ route tracking:
1) target L3VPN Business Entities TLV, it specifies and should respond to L3VPN industry The L3VPN Business Entities of request message are responded in business.The present invention is target L3VPN Business Entities Define two values:All L3VPN Business Entities and a specific L3VPN Business Entity (for example, can be known by the IPv4 addresses for running the PE of the specific L3VPN Business Entities Not).
2) route tracking TLV, it encodes L3VPN business request informations from originating PE To the system address for terminating all PE that PE is traveled through.Route tracking TLV will be in L3VPN Originating PE is sent back in business response message.
3) service label allocation model TLV, it indicates how PE is L3VPN business realities Body distributes service label.According to RFC 4364, PE can select to distribute single for whole VRF Individual service label, a service label is distributed for each direct-connected circuit, is each IP routes point Service label can be distributed with a service label, or PE using other specific process. The present invention defines the new TLV and comes from distal end L3VPN Business Entity inquiry businesses label distribution Pattern.
4) allocated service label number TLV, it is the distribution of L3VPN entities to PE Service label number is encoded.Come from distal end L3VPN industry invention defines the new TLV Entity inquires about allocated service label number.
Fig. 2 shows the signal of the operation of L3VPN business Ping instruments of the invention Figure.Fig. 3 shows showing for the operation of L3VPN business route tracing utility of the invention It is intended to.
L3VPN business Ping instruments and L3VPN business route tracing utilities can be implemented as Command line interface (CLI) is ordered, and is adjusted from the cli interface of the PE for participating in L3VPN business Use them.Fig. 2 and Fig. 3 show CLI screens and L3VPN business diagnostic messages in industry Propagation in business transmitting path.
As shown in Figures 2 and 3, band arrow solid line represents that L3VPN business is responded request and disappeared The transmitting path of breath, wherein L3VPN business are responded request message and are initiated by node 10.1.1.1, Destination node is 10.1.2.3, is arrived along the data path of the broadcast packe in L3VPN business domains Up to all L3VPN Business Entities.
The present invention is the extension of previous invention, and the total of suggestion disappears during it has reused previous invention Breath coded format and define necessary new extension (two kinds of new type of messages, four kinds it is new Specific to the wrong subcode of business and two kinds of new TLV) supporting L3VPN business The operation of Ping and route tracing utility.
Message encoding format and its field described below, previous invention has been defined and this hair The new definition of bright suggestion is suitably marked.
L3VPN business responds request and response message and is grouped carrying by UDP.Udp port Number can be distributed by IANA, or be locally configured on the PE that can be participated at each.
Fig. 4 shows that L3VPN business of the invention responds the lattice of request and response message The schematic diagram of formula.Wherein, both message are present in the form of UDP packet load, It is identical with previous invention.
For the integrality of document, the definition of field has been redescribed here.Note, below Definition part it is identical with what is defined before, all L2VPN in previous invention are changed to More appropriate term (such as L3VPN).Although message format is constant, it is proposed that It is only applicable to new type of message, the new spy of L3VPN business Ping/ route tracking applications Due to the error code and new TLV of business.
Version number:The version number of message format.In the present invention, version number could be arranged to 1 it is not limited to 1.
Life span (Time To Live, TTL):For indicating to allow L3VPN business Respond the maximum quantity (or hop count) of the L3VPN Business Entities that request or response message are passed through. If the value of the field is reduced to zero, it is necessary that the L3VPN business responds request/response message It is dropped and terminates forwarding.After each jump of L3VPN Business Entities, the value of the field must Must subtract 1.Even if its purpose is to ensure there are two layers in the topology of L3VPN business domains Broadcast loops (note:L 2 broadcast loop is usual as caused by incorrect business configuration, just Should be avoided in the case of often) in the case of, L3VPN business response request/response message also can Forwarding finally will be moved to end.The maximum of TTL is 255, it means that diagnostic message should be by Travel to L3VPN Business Entities as far as possible.The minimum value of TTL is 1, it means that The diagnostic message should not be propagated and (noted beyond the adjacent hop distance of L3VPN business entity one: IP also includes ttl field, but it responds request/response message with L3VPN business Ttl field implication is different, therefore can not obscure).
Retain:Untapped field, the field can be arranged to 0.
Type of message:The type of the field identification business diagnostic message.Except in previous invention Outside the value of message types of definition, invention also defines two kinds of new values of message types:
The diagnostic message type of table 1
Value Implication
3 L3VPN business responds request message
4 L3VPN business responds response message
Note:It is that L2VPN business responds request message and response message in previous invention Type of message 1 and type 2 are defined, the present invention extends the species of type of message, for L3VPN business is diagnosed.
Answer-mode:The field indicates the business response response that long-range PE sends back response to disappear The return path of breath.The present invention is determined in reusing previous invention by the diagnosis of L2VPN business The existing answer-mode of justice.For example, answer-mode=1 represents passes through IPv4UDP packet acknowledgments. Generally, L3VPN business should be sufficiently used for based on the answer-mode value of IPv4UDP packets to examine It is disconnected.If needing other answer-modes under special circumstances, the value can extend.Although this Invention define only an answer-mode value, it will be appreciated by those skilled in the art that response Mode value is not limited to that any suitable answer-mode value each falls within the scope of the present invention.
General error code:In the field, long-range PE returns to general error code, its Suitable for all types of Business Entities.The present invention has reused and as shown in table 2 has been The existing general error code of L2VPN business diagnosis definition.Those skilled in the art should Understand, the general error code in table 2 can extend according to actual needs.
The general error code of table 2
Value Implication
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 errors
6 Common message format mistake
7 Specific to the mistake of business
Specific to the wrong subcode of business:In the field, long-range PE is returned specific to industry The error code of business, it is only applicable to specific Business Entity type.For L3VPN business Diagnosis, it is as described below (to note invention defines the new wrong subcode specific to business: The following wrong subcode specific to business is only applicable to the response request/response of L3VPN business and disappears Breath, i.e. type of message=3 or 4).
Wrong subcode of the table 3 specific to business
The handle of sender:The field is filled out by the sender that L3VPN business responds request message Fill, recipient without any changes, responds in L3VPN business and returned as former state in response message. Sender can match response and request message using the value of this field.
Sequence number:The field is arbitrarily set by the sender that L3VPN business responds request message It is fixed, can be used to detect the response message lost.
Send timestamp:The field is the root when L3VPN business response request message is sent According to the date-time of the clock of sender, its form for example can be NTP (Network Time Protocol, NTP) form.
Receive timestamp:The field be when receive L3VPN business respond request message when, The date-time of the clock according to recipient, its form can also be NTP forms.
TLV:Fig. 5 shows that L3VPN business of the invention responds request and response disappears The schematic diagram of the form of TLV and son-TLV fields in breath.The type of TLV is defined as below. Wherein, length is the length of the Value field, is represented with octet.The Value field depends on class Type, to its zero padding with so that 4 borders of octet of alignment.TLV can be nested in other In TLV, in this case, the TLV being nested is referred to as sub- TLV.Sub- TLV has Separate type and 4 octets that must also align.
Table 3 lists the top TLV for L3VPN business diagnostic messages, as follows:
Table 3 is used for the top TLV of L3VPN business diagnostic messages
Type Implication
1 Target L3VPN Business Entities // reused defined in previous invention
3 Route tracks // has reused the TLV defined in previous invention
4 New definition in service label allocation model // present invention
5 New definition in the service label number // present invention of distribution
Explanation is needed exist for, the top TLV 1,2,3, this hair defined in previous invention It is bright to have reused existing top TLV 1 and 3, and define two new top TLV 4 and 5. Top TLV2 is generally unsuitable for L3VPN business diagnostic tools, therefore not shown in table.
Hereinafter, respectively to (including the reuse and new definition) TLV used in the present invention It is introduced.
Target service entity TLV (TLV1)
The value of target service entity TLV is the sub- TLV as defined in table 4 below:
The target service entity TLV of table 4
Target service entity is that L3VPN business responds the TLV that must have in request message.
Route tracking TLV (TLV3)
Route tracking TLV is an optional TLV, and it is for tracking L3VPN business Request message is from originating PE to the path for terminating PE and associated timestamp information.Route Tracking TLV can be both used in L3VPN response business request informations, can be used in again L3VPN is responded in response message.The presence of the TLV is used to determine that L3VPN business is responded Request message is operated for L3VPN business PING or for L3VPN route tracking behaviour Make.
The value of route tracking TLV is the sub- TLV as defined in table 5 below:
The route tracking of table 5 TLV
Sub- TLV classes Length Value
Type 1 12 multiple IPv4 addresses and the pairing list of timestamp
The Value field is the byte of a row 12, and each includes IPv4 addresses for 4 bytes The timestamp subitem of item and 8 bytes.IPv4 addresses subitem is used to record reception L3VPN business The system address of the PE of request message is responded, timestamp subitem connects according to the clock log of PE Date-time during L3VPN business response response message is received, for example can be with NTP forms.
If originating PE intends activation L3VPN business route tracing utilities, it should be L3VPN business responds request message includes route tracking TLV, and its value must include IPv4 Address and the pairing of timestamp.IPv4 addresses are the system address of originating PE, and timestamp is to work as When sending L3VPN business response request message (identical with the transmission timestamp value in Fig. 4) Date-time, for example can be with NTP forms.Track TLV's with route when receiving When L3VPN business responds request message, each downstream PE should be by route tracking TLV It is interior add itself system address and date-time come update L3VPN business respond request message (and decremented TTL values), the L3VPN industry after then being updated along the forwarding of normal path downstream Request message is responded in business.
The TLV (TLV4 and TLV5) of new definition of the invention
Service label allocation model TLV (TLV4)
Service label allocation model TLV is an optional TLV, and it can both be used in L3VPN business is responded in request message, L3VPN business can be used in again and responds response message In.For example, the length of the TLV can be preset as into 1.Please if L3VPN business is responded Ask and there is the TLV in message, then its value for example can be 0, represent that initiating PE asks Response PE Report service label allocation models.Should when PE structure L3VPN business responses are terminated When answering message, its L3VPN business for being based on entering whether there is business in responding request message Label allocation model TLV (such as value=0) decides whether to include service label allocation model TLV.However, it will be understood by those skilled in the art that above-mentioned service label allocation model TLV The setting of length and value be merely exemplary, for application-specific, it can be carried out not Same setting.
In the above-described example, the service label allocation model reported for example can be following A value in table 6:
The service label allocation model TLV of table 6
Value Implication
0 For the request of service label allocation model
1 PE is that whole VRF distributes a service label
2 PE distributes a service label for each direct-connected circuit
3 PE is one service label of each IP route assignment
4 PE distributes service label using other specific process
Service label number TLV (TLV5) of distribution
The service label number TLV of distribution is an optional TLV, and it can both be used in L3VPN business is responded in request message, L3VPN business can be used in again and responds response message In.In one implementation, if L3VPN business has the TLV in responding request message, Then its length should be 1, and its value is also 1, and this is represented initiates PE just in request-reply The service label number of PE report distribution.Disappear when PE structure L3VPN business response responses are terminated During breath, its L3VPN business for being based on entering whether there is the industry distributed in responding request message Business number of tags TLV (such as value=0) is come the service label number TLV that decides whether to include to distribute. However, it will be understood by those skilled in the art that the length of the service label number TLV of above-mentioned distribution What the setting of degree and value was merely exemplary, for application-specific, it can be carried out different Set.
In the above-described example, during the service label number of the distribution reported can be table 7 below The integer value listed:
The service label number TLV of the distribution of table 7
Value Implication
0 For the request of the service label number of distribution
Integer The service label number of distribution
Below the value of each field and each TLV and its corresponding is given in the form of a list Implication example.However, it will be understood by those skilled in the art that above-mentioned setting is only to show Example property, these fields can be rearranged or set by those skilled in the art according to actual needs Put, or the value of TLV is made into any other different setting, these are without departing from this hair Bright scope.
The operation of L3VPN business PING and route tracing utility
Fig. 2 shows the signal of the operation of L3VPN business Ping instruments of the invention Figure, Fig. 3 shows showing for the operation of L3VPN business route tracing utility of the invention It is intended to.L3VPN business Ping is similar with the operation of route tracing utility.To they two For person, originating PE sends L3VPN business and responds request message and wait from response PE times Multiple L3VPN business responds response message.L3VPN business responds request message along broadcast Packet data path transmission, as long as therefore ttl value is sufficiently large, it can reach L3VPN industry All PE of pragmatic example.The PE that each is traversed must first check for the L3VPN for entering Whether the target that business responds request message is directed to oneself, so as to correspondingly operate.If it is not, The L3VPN business responds request message and is first updated (ttl value decline 1;For L3VPN Business route tracking, route tracking TLV is added new IPv4 addresses and timestamp information), The L3VPN Business Entities in all downstreams are then forwarded to (if target is all L3VPN industry Entity, then stop forwarding after reaching last PE;If target is specific L3VPN Business Entity, then stop forwarding after reaching specific PE);Otherwise (i.e. L3VPN industry Business responds request message and is directed to PE in itself), except updating and forwarding L2VPN business to respond Request message, PE should also reply L3VPN business and respond request message.Wherein, the TTL Value is for preventing from endless loop occur in the case of L3VPN topological structure error configurations.
L3VPN business Ping and route tracing utility are responded request and are disappeared using L3VPN business Breath and L3VPN business respond the different-format of response message.Fig. 6 A and Fig. 6 B are shown respectively L3VPN business for L3VPN business Ping instruments responds request message and L3VPN Business responds the schematic diagram of response message.
As shown in Figure 6A and 6B, for the L3VPN of L3VPN business Ping instruments Business responds request message includes target L3VPN Business Entities TLV (essential) and business Label allocation model TLV (optional) and service label number TLV (optional) of distribution, and L3VPN business response response message for L3VPN business Ping instruments includes business mark Sign service label number TLV (optional) of allocation model TLV (optional) and distribution.
Fig. 7 A and Fig. 7 B are respectively illustrated for L3VPN business route tracing utilities L3VPN business responds request message and L3VPN business responds the schematic diagram of response message.
As shown in Figure 7A and 7B, for the L3VPN of L3VPN business route tracing utilities Business respond request message include target L3VPN Business Entities TLV (essential) and route with Track TLV (essential) and service label allocation model TLV (optional) and the business of distribution Number of tags TLV (optional), and it is used for the L3VPN of L3VPN business route tracing utilities Business responds response message includes route tracking TLV (essential) and service label allocation model TLV (optional) and service label number TLV (optional) of distribution.
L3VPN business responds request message and L3VPN business is responded response message and all sealed In UDP packets.UDP port number can use manufacturer privately owned (Vendor proprietary) Value is locally configured on each PE, or discloses distribution to support worldwide interoperability by IANA. Udp port is referred to as L3VPN business Ping ports in the present invention.
Request packet is responded for L3VPN business, Target IP v4 addresses are arranged to Any IPv4 addresses in the range of 127/8, the system that source IP v4 addresses are arranged to originating PE Address.Target UDP port number is arranged to L3VPN business Ping port numbers, source UDP Port is arbitrarily set by originating PE.Response message is responded for corresponding L3VPN business, Target IP v4 addresses are arranged to the source that received L3VPN business responds request packet IPv4 addresses, source IP v4 addresses are arranged to the system address of the PE for carrying out response.Target UDP port number is arranged to the source UDP that received L3VPN business responds request packet Port, source UDP port number is arranged to L3VPN business Ping ports.
Carry L3VPN business and respond the diagnosis packet of request message along L3VPN business realities The acyclic data path of the broadcast packe in example advances to reach in L3VPN srvice instance All L3VPN entities once and only once.Note, diagnosis packet is in fact tape label IPv4 packets, MPLS label is allocated to any service label of L3VPN srvice instance, And IPv4 packets carry the UDP payloads that L3VPN business responds request message.The band The IPv4 packets of label are transmitted by business transmitting path between VRF, and it can be MPLS LSP Or generic route encapsulation (Generic Routing Encapsulation, GRE) passage.Just In the case of often, if operator has been configured with L3VPN traffic performances (i.e., suitably It is configured with output RT and input RT), the horizontal segmentation group being associated with each VRF should Do not include loop in the data path of broadcast diagnostics packet.In the L3VPN industry of error configurations In business, loop is might have in the data path of broadcast diagnostics packet.In order to prevent this not wishing Endless loop in the case of prestige, each L3VPN business responds request message and is limited to ttl value (maximum ttl value is 255).
The operation of originating PE
Responding request message and business response response message when above-mentioned L3VPN business is used for When L3VPN business is diagnosed, originating PE performs following steps:L3VPN business is built to respond Request message;The L3VPN business is sent to other PE respond request message;Receive and come from it The L3VPN business of his PE responds response message.Wherein the L3VPN business is responded request and is disappeared Breath includes target L3VPN Business Entities TLV.In other portions of claim and specification Point, originating PE is also referred to as a PE sometimes, correspondingly, L3VPN business will be participated in Other PE in addition to originating PE are also referred to as the 2nd PE.Specifically, retouch in detail below The operation of originating PE according to embodiments of the present invention is stated.
(1) originating PE builds the L3VPN business to be sent and responds request message.
In one implementation, in constructed L3VPN business responds request message, version This number can be 1, and type of message=3, answer-mode=1, ttl value comes from the defeated of keeper Enter.Reserved field, general error code and the error code specific to business both are set to 0. The message handle of sender is used for matching response and request message, and it can be in a variety of different ways To set.For example, responding the transmission of request message group when new continuous L3VPN business is sent When, it can be configured so that a new random number.Sequence number is used for detecting that the response missed disappears Breath, it is also possible to set in a different manner, for example, there is same sender message when sending When one group of L3VPN business of handle value responds each continuous meassage in request message, it can To be arranged to 1,2,3 ....Timestamp is sent to be arranged to send L3VPN business time Answer the date-time (such as with NTP forms) of request message.Timestamp is received to be set It is set to 0.
(2) for L3VPN business Ping and route tracing utility, target L3VPN Business Entity TLV is essential.According to the input of keeper, target service entity TLV Value can be configured so that Class1-TLV (all Business Entities) or son-TLV of type 2 (a specific transactions entity).
Route tracking TLV is essential for L3VPN business route tracing utilities, but It is not required for L3VPN business Ping instruments.When keeper calls L3VPN business During route tracing utility, originating PE must respond request message in L3VPN business includes road By tracking TLV.Route tracking TLV must only include a pair of IPv4 addresses and timestamp, IPv4 Address is the system address of originating PE, and timestamp is to send L3VPN business to respond request message Date-time (identical with the value in the transmission timestamp field in Fig. 4).
Service label allocation model TLV and the service label number TLV of distribution are for L3VPN It is optional for business diagnostic tool.Depending on the input of keeper, L3VPN business is returned Answering request message can not include including one of which, two or one.
Constructed L3VPN business responds request message and is encapsulated in UDP IPv4 packets In.However, it will be understood by those skilled in the art that the invention is not limited in this, can be with Carried using other protocol packets constructed L3VPN business respond request message (and/or L3VPN business responds response message).
(3) originating PE is by the business equity end to L3VPN srvice instance to be diagnosed All VRF between business transmitting path respond request sending constructed L3VPN business and disappear Breath.
When all L3VPN Business Entities are by Ping or by route tracking, own Participating in the PE of L3VPN business should all reply L3VPN business response response message.For The specific L3VPN Business Entities of only one of which are by Ping or the situation by route tracking, only spy Fixed target PE can reply L3VPN business and respond response message, and every other PE is letter Singly update and forward the L3VPN business to respond request message, without to its response.
If all L3VPN Business Entities in L3VPN business by Ping or route with Track, then initial TTL value can be configured so that 255 and (or be considered sufficiently large by implementer Any other numeral).If simply part L3VPN Business Entities by Ping or route with Track, then ttl value can be set as 1,2,3 ....For example, the L3VPN of TTL=1 Business responds request message and tracks all adjacent (being separated by a jump) Ping or route L3VPN Business Entities.
When each PE receives tape label from the L3VPN business transmitting paths of any entrance IPv4 is grouped and the target udp port of IPv4 packets is equal to configured L3VPN business During Ping ports, the PE must be regarded as the diagnosis packet of L3VPN business.The PE is necessary First verify that version number, type of message and answer-mode are all correct, and ttl value is not zero. If any one of above-mentioned checking mistake, PE returns to L3VPN business and responds response point Group and stop forwarding L3VPN business respond request message, wherein, the L3VPN business return Answering acknowledgment packet includes corresponding general error code.
If without mistake (therefore type of message must be 3) in message format is input into, The PE should analyze TLV fields.TLV1 (target service entity) be it is essential, TLV3, 4 or 5 is optional.If having any in the L3VPN business for entering responds request message TLV (or sub- TLV) format error, then PE must return to (the lattice of general error code 5 Formula mistake TLV) L3VPN business respond and request message and stop forwarding L3VPN industry Request message is responded in business.
If, all without mistake, PE should verify business mark for message format and TLV forms The correctness of label, its binding with L3VPN Business Entities (and its associated component) and The L3VPN Business Entities integralities of itself.If service label not in tag information base or Person is not associated with any L3VPN Business Entities, then PE must return to the mistake specific to business By mistake subcode=1 (service label mistake or incorrect be tied to L3VPN srvice instance) L3VPN business responds acknowledgment packet.If L3VPN Business Entities (or its associated component) There is any mistake, then PE must return to wrong subcode=2 (the L3VPN business specific to business Example error) L3VPN business respond acknowledgment packet.If not by defined specific In business wrong character code cover any other mistake, then PE must return to specific to business Wrong subcode=3 (general error) L3VPN business respond acknowledgment packet.If there is Any mistake specific to business, then PE must stop forwarding L3VPN business respond request disappear Breath.
Demonstrating message format, TLV forms, service label and L3VPN Business Entities Afterwards, PE can determine the L3VPN srvice instance being diagnosed, and then judge what is entered L3VPN business responds the target of request message.
When L3VPN business response request message is received, the institute in addition to originating PE There is the behavior of PE as described below:
If the target that received L3VPN business responds request message is all L3VPN Business Entities, then:
The PE performs the process that L3VPN business responds response message that returns;
The PE performs the process that L3VPN business responds request message that updates;
The PE performs the process that the L3VPN business after forwarding updates responds request message;
Otherwise, if the target that received L3VPN business responds request message is one specific L3VPN Business Entities and exactly the PE, then:
The PE performs the process that L3VPN business responds response message that returns;
Otherwise (that is, the L3VPN business for receiving responds the not all L3VPN of target of request message Business Entity is nor the specific PE), then
The PE performs the process that L3VPN business responds request message that updates;
The PE performs the process that the L3VPN business after forwarding updates responds request message.
In the present invention, after updating L3VPN business response request message, forwarding renewal L3VPN business responds request message and returns to the process that L3VPN business responds response message It is as described below:
Update the process that L3VPN business responds request message:
(1) the L3VPN business for making entrance first responds the copy of request message, and right The copy does following treatment:
Ttl value in the message copy is reduced 1 by PE;
If the message copy is tracked comprising route tracking TLV, the PE in route Add its system address with the date-time for receiving input message (for example in the end of TLV With NTP forms).
In this way so that the message copy is changed into the L3VPN business after updating Respond request message.
L3VPN business after forwarding renewal responds the process of request message:
If the ttl value that the L3VPN business after updating responds request message is zero, Stop forwarding;
Otherwise, business is transmitted between all VRF that the PE passes through L3VPN srvice instance Path is sent the L3VPN business after updating in the same mode of broadcast packe and responds request Message.That is, except belonging to same level segmentation group with the business equity end for entering VRF between outside business transmitting path, the message after renewal should be by every other Traffic assignments path is (by industry between all VRF for belonging to varying level segmentation group between VRF Business transmitting path) it is transmitted.
Note:Repeating process will stop in following any one situation:A () ttl value subtracts It is small to 0;B () L3VPN business responds the PE that request message reaches most downstream.
Return to the process that L3VPN business responds response message:
(1) PE builds the L3VPN business to be sent and responds response message.Realized in one kind In, in constructed L3VPN business responds response message, version number=1, type of message= 4.L3VPN business does not use TTL and answer-mode in responding response message, can be set It is set to 0.The handle of sender, sequence number and to send timestamp be all from the L3VPN for entering Replicated in business response request message.Timestamp field is received by receiving the L3VPN of entrance The date-time (such as with NTP forms) that business responds request message is filled.
(2) if the L3VPN business for entering responds request message and do not include that route is tracked TLV (i.e. for the situation of L3VPN business Ping), then the PE should be according to entrance L3VPN business responds whether request message includes service label allocation model TLV (value=0) And/or distribution service label number TLV (value=0) come build with zero, one or two The L3VPN business of TLV responds response message.For L3VPN business Ping situations, PE The L3VPN business of structure responds response message should not include route tracking TLV.
Otherwise, if the L3VPN business for entering responds request message and includes route tracking TLV (i.e. for the situation of L3VPN business route tracking), PE should be built with a route Tracking TLV is along with zero, (service label distributes mould to one or two other optional TLV The formula TLV and/or service label number TLV of distribution) L3VPN business respond response message. The end for routeing tracking TLV that request message is replicated is responded by from the L3VPN business for entering When the system address of the additional PE of tail and the L3VPN business response request message for receiving entrance Date-time (such as with NTP forms) route tracking TLV to produce.L3VPN business is returned Answer in response message whether business that should be comprising service label allocation model TLV and/or distribution Number of tags TLV depends on one or both of which (value=0) with the presence or absence of in entrance L3VPN business is responded in request message.
(3) PE is grouped the response of the L3VPN business constructed by returning and answers by UDP IPv4 Answer message.
In a kind of realization of the invention, in order to avoid diagnosing the situation of all Business Entities Lower many very similar L3VPN business are responded response message and are full of by the PE of response, each The PE for carrying out response should postpone a random time intervals before response message is sent.Can To use any rational random delay algorithm, postpone to calculate the invention is not limited in specific Method.
In a kind of realization of the invention, the L3VPN business being only forwarded responds request The data path of message traverses L3VPN traffic packets.The L3VPN business of return responds response Message without L3VPN traffic packets data path, but by normal IP forward number According to path.
In a kind of realization of the invention, because L3VPN traffic packets are from originating PE to spy The PE that sets the goal may travel through multiple data paths of L3VPN traffic packets, so in initialization L3VPN business is responded after request message, and originating PE is likely to be received multiple L3VPN industry Response message is responded in business, and it represents that L3VPN business responds the multiple that request message may pass through Data path, for example as shown in Figure 3.
For L3VPN business Ping and the CLI command of route tracing utility
L3VPN business Ping and route tracing utility can be with command line interface (Command Line Interface, CLI) order to realize.In the CLI interfaces of PE, in current CLI Context is that when L3VPN srvice instance is diagnosed, keeper can be come with for example following orders of use-case Call L3VPN business Ping or route tracing utility:
l3vpn-ping*|ip-address[[no]service-label-assign-mode][[no] nbr-of-service-label][hop hop-count]
l3vpn-traceroute*|ip-address[[no]service-label-assign-mode][[no] nbr-of-service-label][hop hop-count]
Wherein, " * | ip-address " it is essential CLI parameters, which specify target L3VPN industry Entity.* all L3VPN Business Entities are represented, ip-address is represented with appointing system A specific L3VPN Business Entity on the PE of address.“[no] Service-label-assign-mode " and " [no] nbr-of-service-label " are optional CLI ginsengs Number, it is specified whether should Report service label allocation model and/or service label number.Realize Person may decide that its default value.
" hop hop-count " is optional CLI parameters, and it defines L3VPN business and responds request The initial TTL value of message.Implementor may decide that its default value.
Fig. 8 shows the side of the device 800 for the diagnosis of L3VPN business of the invention Block diagram.Device 800 for example may be located in originating PE (PE).
As shown in Figure 8, device 800 includes:Construction unit 810, it is configured as structure Build L3VPN business and respond request message;Transmitting element 820, it is configured as to the 2nd PE Send L3VPN business and respond request message;Receiving unit 830, it is configured as receiving and Response message is responded from the L3VPN business of the 2nd PE;Wherein, L3VPN business is responded and asked Seeking message includes target service entity TLV, and the response of L3VPN business should be responded for specifying The L3VPN Business Entities of request message.
In one implementation, target L3VPN Business Entities TLV is used to specify and should respond The L3VPN Business Entities that the L3VPN business responds request message are all L3VPN business Entity or a specific L3VPN Business Entity, and wherein, when target L3VPN business Entity TLV is specified should respond the L3VPN industry that the L3VPN business responds request message When entity is all L3VPN Business Entities, the 2nd PE is all participation L3VPN business PE in any one in addition to a PE, as target L3VPN Business Entities TLV The specified L3VPN Business Entities that should respond L3VPN business response request message are one During specific L3VPN Business Entities, the 2nd PE is the specific L3VPN Business Entities.
In one implementation, L3VPN business responds request message and also includes being arranged to first The message type field of value, and L3VPN business responds response message also including being arranged to Different from the message type field of the second value of the first value.
In one implementation, responding request message when L3VPN business is used for L3VPN business During route tracking, the L3VPN business responds request message also includes route tracking TLV, uses The institute that request message is traveled through from a PE to termination PE is responded in the L3VPN business is indicated There is the system address of PE.
In one implementation, L3VPN business is responded request message and is also distributed including service label The pattern TLV and/or service label number TLV for being distributed, to be respectively used to indicate the 2nd PE By the pattern and the service label number for distributing of L3VPN Business Entities distribution service label.
In one implementation, L3VPN business responds request message also including in the following At least one:Version number, life span, reserved field, answer-mode, general error code, Wrong subcode, the handle of sender, sequence number, transmission timestamp and reception specific to business Timestamp.
Fig. 9 shows another device 900 for the diagnosis of L3VPN business of the invention Block diagram.Device 900 for example may be located at other PE (second in addition to originating PE PE in).
As shown in Figure 9, device 900 includes:Receiving unit 910, it is configured as connecing Receive the L3VPN business from a PE and respond request message, the L3VPN business is responded please Seeking message includes target L3VPN Business Entity TLV, and the L3VPN should be responded for specifying Business responds the L3VPN Business Entities of request message;Determining unit 920, it is configured as Determine the L3VPN business respond request message target be all L3VPN Business Entities or One specific L3VPN Business Entity;Processing unit 930, it is configured as the L3VPN When the target that business responds request message is all L3VPN Business Entities, returned to a PE L3VPN business responds response message, updates L3VPN business and responds request message and forward L3VPN business after renewal responds request message;And responded when the L3VPN business and asked The target of message is a specific L3VPN Business Entity and the 2nd PE is that this is specific During L3VPN Business Entities, return to L3VPN business to a PE and respond response message.
In one implementation, the L3VPN business responds request message and also includes being arranged to the The message type field of one value, and the L3VPN business responds response message also including being set It is set to the message type field of the second value different from the first value.
In one implementation, responding request message when the L3VPN business is used for L3VPN industry During business route tracking, the L3VPN business responds response message also includes route tracking TLV, For indicating the L3VPN business to respond what request message was traveled through from a PE to termination PE The system address of all PE.
In one implementation, the L3VPN business responds response message also including service label point With the pattern TLV and/or service label number TLV for being distributed, to be respectively used to indicate the 2nd PE By the pattern and the service label number for distributing of L3VPN Business Entities distribution service label.
In one implementation, the processing unit 930 is additionally configured to:As the L3VPN Business responds the not all L3VPN Business Entities of target of request message nor the 2nd PE When, update the L3VPN business and respond request message and forward the L3VPN business after updating Respond request message.
In one implementation, device 900 also includes authentication unit 940, for determining unit The target that 920 determination L3VPN business respond request messages be all L3VPN Business Entities also Before being a specific L3VPN Business Entity, checking L3VPN business responds request message. More specifically, authentication unit 940 is configured to verify that in L3VPN business response request message At least one checking item, the checking include version number, type of message, answer-mode, Ttl value and TLV forms;And if any one of checking item mistake, then return to L3VPN Business responds response message and stops forwarding L3VPN business and responds request message, wherein, The L3VPN business responds response message to be included corresponding error code to indicate authentication error.
In one implementation, the processing unit 930 is obstructed by IP forwarding data paths The data path for crossing L3VPN traffic packets returns to the L3VPN business response response message.
Summarize:
The invention provides two kinds of new L3VPN business diagnostic tool (L3VPN business Ping Instrument and L3VPN business route tracing utility), it is to for the diagnosis of L2VPN business The extension of previous invention.In order to support two kinds of new diagnostic tools, invention proposes to previous The following extension of invention:Two kinds of new type of messages, four kinds of new mistake specific to business Code, two kinds of new TLV, and describe to realize new L3VPN service Ping and route with The behavior of the PE of track instrument or pseudo Algorithm.
In one or more exemplary designs, can with hardware, software, firmware or they Any combination realize function described herein.If realized with software, can be by The function is stored on a computer-readable medium as one or more instructions or code, or Transmitted as one or more instructions on computer-readable medium or code.Computer-readable Medium includes computer-readable storage medium and communication media, and wherein communication media includes helping to calculate Machine program is delivered to the arbitrary medium of another place from place.Storage medium can be logical With or the addressable any usable medium of special-purpose computer.This computer-readable medium can be wrapped Include, such as but not limited to, RAM, ROM, EEPROM, CD-ROM or other CDs Storage device, disk storage equipment or other magnetic storage apparatus, or can be used for general or special With computer or universal or special processor it is addressable instruction or data structure form come Carry or store any other medium of desired code modules.Also, any connection Can be known as computer-readable medium.If for example, software is to use coaxial cable, light Fine optical cable, twisted-pair feeder, Digital Subscriber Line (DSL) or such as infrared ray, radio and microwave Etc wireless technology come from website, server or other remote sources transmission, then coaxial electrical Cable, optical fiber cable, twisted-pair feeder, DSL or the such as nothing of infrared ray, radio and microwave etc Line technology is also included within the definition of medium.
General processor, digital signal processor (DSP), application specific integrated circuit can be used (ASIC), field programmable gate array (FPGA) or other PLDs, point Found door or transistor logic, discrete hardware components or for performing appointing for function as herein described Meaning combines to realize or perform with reference to various exemplary logical block, the module described by the disclosure And circuit.General processor can be microprocessor, or, processor can also be any general Logical processor, controller, microcontroller or state machine.Processor can also be embodied as meter The combination of calculation equipment, for example, the combination of DSP and microprocessor, multi-microprocessor, one Or the combination of multi-microprocessor and DSP core, or any other such structure.
Those of ordinary skill in the art are also understood that with reference to embodiments herein description Various exemplary logical blocks, module, circuit and algorithm steps can be implemented as electronic hardware, Computer software or combination.In order to clearly show that between hardware and software it is this can Interchangeability, above to various exemplary parts, block, module, circuit and step around it Function has carried out general description.As for this function be implemented as hardware be also implemented as it is soft Part, depending on specific application and applying design constraint over the whole system.This area Technical staff can be directed to every kind of application-specific, and described function is realized in the way of accommodation, But, it is this to realize that decision-making should not be interpreted as causing a departure from the scope of this disclosure.
The above description of the disclosure is used to enable any those of ordinary skill of this area to realize Or use the present invention.To those skilled in the art, the various modifications of the disclosure are all Be it will be apparent that and general principle defined herein can also do not depart from it is of the invention Other deformations are applied in the case of spirit and scope.Therefore, the present invention is not limited to this Example and design described in text, but with principle disclosed herein and the most wide model of novel features Enclose consistent.

Claims (15)

1. it is a kind of for L3VPN business diagnosis method, methods described include by a PE The following steps of execution:
Build L3VPN business and respond request message;
The L3VPN business is sent to the 2nd PE respond request message;And
Receive the L3VPN business from the 2nd PE and respond response message;
Wherein, the L3VPN business responds request message includes target service entity TLV, The L3VPN business realities that the L3VPN business responds request message should be responded for specifying Body.
2. method according to claim 1, wherein, the target L3VPN business Entity TLV is used to specify should respond the L3VPN that the L3VPN business responds request message Business Entity be all L3VPN Business Entities or a specific L3VPN Business Entity,
Wherein, described in specifying and should respond as the target L3VPN Business Entities TLV The L3VPN Business Entities that L3VPN business responds request message are all L3VPN business realities During body, the 2nd PE is except a PE in all PE for participating in the L3VPN business Outside any one,
The L3VPN should be responded when the target L3VPN Business Entities TLV is specified The L3VPN Business Entities that business responds request message are a specific L3VPN Business Entity When, the 2nd PE is the specific L3VPN Business Entities.
3. method according to claim 1, wherein, the L3VPN business is responded Request message also includes being arranged to the message type field of the first value, and the L3VPN Business responds response message also including being arranged to disappearing for the second value different from first value Breath type field.
4. method according to claim 3, wherein, when the L3VPN business is returned When answering request message to route tracking for L3VPN business, the L3VPN business responds request Message also includes route tracking TLV, for indicating the L3VPN business to respond request message From a PE to the system address for terminating all PE that PE is traveled through.
5. the method according to claim 3 or 4, wherein, the L3VPN business Responding request message also includes service labels allocation model TLV and/or the service labels for being distributed Number TLV, to be respectively used to indicate a PE to distribute business as L3VPN Business Entities The pattern of label and the service label number for being distributed.
6. method according to claim 1, wherein, the L3VPN business is responded Request message is also including at least one in the following:Version number, life span, reserved word Section, answer-mode, general error code, specific to the wrong subcode of business, the sentence of sender Handle, sequence number, transmission timestamp and reception timestamp.
7. it is a kind of for L3VPN business diagnosis method, methods described include by the 2nd PE The following steps of execution:
Receive the L3VPN business from a PE and respond request message, the L3VPN Business responds request message includes target L3VPN Business Entity TLV, should be rung for specifying The L3VPN business is answered to respond the L3VPN Business Entities of request message;
Determine that the target that the L3VPN business responds request message is all L3VPN business Entity or a specific L3VPN Business Entity;
When the target that the L3VPN business responds request message is all L3VPN business realities During body, the 2nd PE returns to L3VPN business and responds response message to a PE, The L3VPN business is updated to respond request message and forward the L3VPN business after updating to return Answer request message;And
When the target that the L3VPN business responds request message is a specific L3VPN Business Entity and when the 2nd PE is the specific L3VPN Business Entities, described second PE returns to L3VPN business and responds response message to a PE.
8. method according to claim 7, wherein, the L3VPN business is responded Request message also includes being arranged to the message type field of the first value, and the L3VPN Business responds response message also including being arranged to disappearing for the second value different from first value Breath type field.
9. method according to claim 8, wherein, when the L3VPN business is returned When answering request message to route tracking for L3VPN business, the L3VPN business responds response Message also includes route tracking TLV, for indicating the L3VPN business to respond request message From a PE to the system address for terminating all PE that PE is traveled through.
10. method according to claim 8 or claim 9, wherein, the L3VPN industry Response message is responded in business also includes service label allocation model TLV and/or the business mark for being distributed Number TLV is signed, is L3VPN Business Entity distribution businesses to be respectively used to indicate the 2nd PE The pattern of business label and the service label number for being distributed.
11. methods according to claim 7, also include:
When the L3VPN business responds the not all L3VPN business of target of request message Entity is nor during two PE, the 2nd PE updates the L3VPN business and responds Request message and forward update after L3VPN business respond request message.
12. methods according to claim 7, also include, it is determined that the L3VPN The target that business responds request message is that all L3VPN Business Entities or one are specific Before L3VPN Business Entities:
Verify that the L3VPN business responds request message, it is further included:
Verify that the L3VPN business responds at least one of request message checking item, institute Stating checking item includes version number, type of message, answer-mode, ttl value and TLV forms;
If any one of checking item mistake, returns to the L3VPN business and returns Answer response message and stop forwarding the L3VPN business and respond request message, wherein, institute State L3VPN business and respond response message including corresponding error code to indicate authentication error.
13. methods according to claim 7, wherein, by IP forwarding data paths Response is responded without returning to the L3VPN business by the data path of L3VPN traffic packets Message.
A kind of 14. devices for the diagnosis of L3VPN business, described device is located at a PE In, including:
Construction unit, it is configured as building L3VPN business response request message;
Transmitting element, it is configured as being responded to the 2nd PE transmission L3VPN business and asks Seek message;And
Receiving unit, it is configured as receiving the L3VPN business from the 2nd PE time Answer response message;
Wherein, the L3VPN business responds request message includes target service entity TLV, The L3VPN business realities that the L3VPN business responds request message should be responded for specifying Body.
A kind of 15. devices for the diagnosis of L3VPN business, described device is located at the 2nd PE In, including:
Receiving unit, it is configured as receiving the L3VPN business response from a PE please Message is sought, the L3VPN business responds request message includes target L3VPN Business Entities TLV, the L3VPN industry that the L3VPN business responds request message should be responded for specifying Entity;
Determining unit, it is configured to determine that the L3VPN business responds request message Target is all L3VPN Business Entities or a specific L3VPN Business Entity;And
Processing unit, it is configured as the mesh that the L3VPN business responds request message When mark is all L3VPN Business Entities, returns to L3VPN business to a PE and respond Response message, updates after the L3VPN business responds request message and forward renewal L3VPN business responds request message;And when the L3VPN business responds request message Target is a specific L3VPN Business Entity and the 2nd PE is that this is specific During L3VPN Business Entities, return to L3VPN business to a PE and respond response message.
CN201510864379.5A 2015-11-30 2015-11-30 Method and apparatus for L3VPN service diagnosis Active CN106817273B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510864379.5A CN106817273B (en) 2015-11-30 2015-11-30 Method and apparatus for L3VPN service diagnosis

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510864379.5A CN106817273B (en) 2015-11-30 2015-11-30 Method and apparatus for L3VPN service diagnosis

Publications (2)

Publication Number Publication Date
CN106817273A true CN106817273A (en) 2017-06-09
CN106817273B CN106817273B (en) 2021-09-03

Family

ID=59107147

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510864379.5A Active CN106817273B (en) 2015-11-30 2015-11-30 Method and apparatus for L3VPN service diagnosis

Country Status (1)

Country Link
CN (1) CN106817273B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102437931A (en) * 2011-12-29 2012-05-02 华为技术有限公司 Detection method and device of service path
CN102739448A (en) * 2012-06-28 2012-10-17 华为技术有限公司 Method, device and system for transmitting messages
CN103457794A (en) * 2013-08-22 2013-12-18 华为技术有限公司 Method and system for confirming faults of IP bearer network
US9042369B2 (en) * 2013-03-13 2015-05-26 Alcatel Lucent System and method for reflecting FEC route information

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102437931A (en) * 2011-12-29 2012-05-02 华为技术有限公司 Detection method and device of service path
CN102739448A (en) * 2012-06-28 2012-10-17 华为技术有限公司 Method, device and system for transmitting messages
US9042369B2 (en) * 2013-03-13 2015-05-26 Alcatel Lucent System and method for reflecting FEC route information
CN103457794A (en) * 2013-08-22 2013-12-18 华为技术有限公司 Method and system for confirming faults of IP bearer network

Also Published As

Publication number Publication date
CN106817273B (en) 2021-09-03

Similar Documents

Publication Publication Date Title
CN109981457B (en) Message processing method, network node and system
CN105141434B (en) The fault detection method and device of business chain
CN102986170B (en) For providing in DIAMETER network dynamically based on method, system and equipment that the routed keyword of starting point is registered
CN104780066B (en) Determined for the physical pathway of virtual network stream of packets
CN101904184B (en) Automatic MEP provisioning in a link state controlled Ethernet network
CN103379032B (en) The acquisition methods and device, sub-route computational entity of cross-domain end-to-end route
CN100399757C (en) Injecting addresses to enable OAM functions
CN105191215A (en) Data plane learning of bi-directional service chains
CN107710693A (en) The method of opening relationships between multigroup label switched path and virtual network
CN106921572B (en) A kind of method, apparatus and system for propagating qos policy
CN106603413B (en) Method and device for transmitting flow through designated path
CN104579728A (en) Network element equipment configuration and management method and device as well as network element equipment
CN111585780B (en) Supporting multiple virtual networks through underlying network topology
CN109756521B (en) NSH message processing method, device and system
CN103634214B (en) A kind of routing iinformation generation method and device
CN106941437A (en) A kind of information transferring method and device
CN103326940A (en) Method for forwarding message in network and edge device of operator
CN106789748A (en) A kind of distributed couple in multiplexer DAM stacking network system and its apparatus
CN108270673A (en) File transmitting method, device and system
CN107566280A (en) Verify the method and router device in multicast packet path
CN109379241A (en) A kind of routing information determines method and device
CN103200107B (en) Message transmitting method and message transmitting equipment
CN101120553B (en) Method for aggregating data traffic over an access domain and nodes therefor
CN107294849A (en) Method, device and system for establishing service path
CN105915458A (en) Shortest Path Bridging (SPB) - Protocol-Independent Multicast (PIM) Interactions

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information

Address after: 201206 Pudong New Area Jinqiao Ning Road, Shanghai, No. 388

Applicant after: Shanghai NOKIA Baer Limited by Share Ltd

Address before: 201206 Pudong New Area Jinqiao Ning Road, Shanghai, No. 388

Applicant before: Shanghai Alcatel-Lucent Co., Ltd.

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant