CN103580894A - Method, device and system for operation, administration and maintenance (OAM) configuration - Google Patents

Method, device and system for operation, administration and maintenance (OAM) configuration Download PDF

Info

Publication number
CN103580894A
CN103580894A CN201210268576.7A CN201210268576A CN103580894A CN 103580894 A CN103580894 A CN 103580894A CN 201210268576 A CN201210268576 A CN 201210268576A CN 103580894 A CN103580894 A CN 103580894A
Authority
CN
China
Prior art keywords
oam
egress
source
lsp ping
entity
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
CN201210268576.7A
Other languages
Chinese (zh)
Other versions
CN103580894B (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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201210268576.7A priority Critical patent/CN103580894B/en
Priority to PCT/CN2013/070534 priority patent/WO2014019348A1/en
Publication of CN103580894A publication Critical patent/CN103580894A/en
Application granted granted Critical
Publication of CN103580894B publication Critical patent/CN103580894B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/12—Arrangements for remote connection or disconnection of substations or of equipment thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Landscapes

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

Abstract

An embodiment of the invention provides a method, a device and a system for OAM configuration. The method comprises the steps of configuring a source-side OAM entity for a source-side PE, and forbidding the source-side OAM entity to send an OAM message to the source-side PE; sending a first LSP Ping request message carried with source-side OAM entity configuration information to a sink-side PE; receiving a first LSP Ping response message carried with sink-side OAM entity configuration information and sent by the sink-side PE, and enabling an energy-side OAM entity to send the OAM message the sink-side PE when the sink-side OAM entity configuration information is matched with the source-side OAM entity configuration information. The embodiment of the invention further provides the source-side PE, the sink-side PE and the OAM configuration system. By adopting the technical scheme, the OAM configuration working amounts of the source-side and the sink-side are decreased, the source-side and the sink-side dynamically finish the OAM configuration by interacting the LSP Ping response messages, and errors arisen in manual configuration are avoided.

Description

Method, the equipment and system of Operations, Administration and Maintenance OAM configuration
Technical field
The present invention relates to network communication field, relate in particular to a kind of method, equipment and system of OAM configuration.
Background technology
(English full name is Operations to perfect Operations, Administration and Maintenance, Administration and Maintenance, English referred to as OAM) function is that the important symbol of carrier class network is extremely important for operator, OAM can reduce operation complexity and the O&M cost of operator, can strengthen the availability of carrier network, the SLA (Service-Level Agreement, service-level agreement) that can also help carrier network checking and user to sign.
OAM mechanism mainly comprises that fault management (Fault Management), performance monitoring (Performance Monitoring) and protection switch (Protection Switching) three aspects.Wherein fault management can be divided into again fault detect (Fault Detection), failure proof (Fault Verification), fault location (Fault Localization) and these four aspects of fault notification (Fault Notification); And performance monitoring mainly provides the monitoring to packet loss, these three indexs of delay time and jitter.
For Internet protocol/multi protocol label, (English full name is Internet Protocol/Multiprotocol Label Switching in exchange, English referred to as IP/MPLS) and Ethernet (Ethernet) network, mainly containing at present comparatively perfect OAM mechanism is mainly Ethernet OAM and connection-oriented packet switching network technology (English full name is Transport Profile for MPLS, English referred to as MPLS-TP) OAM.The former comprises IEEE802.3ah, IEEE802.1ag, ITU-T Y.1731 and the standard of some metropolitan area ether forums (English full name is Metro Ethernet Forum, English referred to as MEF), and the latter is comprised of the defined series of standards of IETF.
VPN (virtual private network) (English full name is Virtual Private Network, English referred to as VPN) is the virtual proprietary network that operator provides to user by its public network, at user's angle VPN, is user's a proprietary network.For operator, public network comprises public backbone network and public operator edge device.Geographically VPN member's website separated from one another is connected to corresponding provider edge router by client device (CPE) (English full name is Provider Edge, English referred to as be PE), the VPN network of the public network composition client by operator.
Layer3 Virtual Private Network (English full name is Layer 3 Virtual Private Network, English referred to as L3VPN) is a kind of three-layer VPN technology based on MPLS.In L3VPN network, when configuring OAM in prior art VPN being detected, the OAM entity that needs manual creation source PE and egress PE, and respectively the OAM entity of source PE and egress PE is carried out to parameter configuration, in this process, to manually guarantee that the configuration parameter of OAM entity of egress PE and the configuration parameter of the OAM entity of source PE are consistent, so not only make the workload of OAM configuration larger, and easily occur configuration error.
Summary of the invention
Embodiments of the invention provide a kind of OAM method, the equipment and system of configuration, and when solving that PE equipment configuration OAM detects VPN in L3VPN networking, the problem of configuration error appears greatly and easily in the configuration effort amount that human configuration causes.
First aspect, a kind of method that provides OAM to configure, described method comprises:
Source provider edge router PE configuration source OAM entity, and forbid that described source OAM entity sends OAM message to described egress PE;
To described egress PE, send the first label switched path the Internet packets survey meter LSP Ping request message that carries described source OAM physical arrangements information, so that described egress PE is according to the egress OAM entity of egress PE described in described source OAM physical arrangements information configuration, start the message receiving function of described egress OAM entity, a described LSP Ping request message also comprises the VPN sign of Layer3 Virtual Private Network L3VPN, and described VPN sign is for identifying the VPN that described egress PE equipment need to carry out OAM detection;
Receive the LSP Ping response message that described egress PE sends, a described LSP Ping response message carries described egress OAM physical arrangements information, when definite described egress OAM physical arrangements information and described source OAM physical arrangements information matches, enable described source OAM entity and to described egress PE, send the function of OAM message.
In the possible implementation of the first of described first aspect, described method also comprises:
When definite described egress OAM physical arrangements information is not mated with described source OAM physical arrangements information, adjust described source OAM physical arrangements information and described egress OAM physical arrangements information matches, enable described source OAM entity and to described egress PE, send the function of OAM message.
In the possible implementation of the first of described first aspect or described first aspect, the possible implementation of the second of described first aspect is also provided, a described LSP Ping request message is carried described VPN and is identified by Virtual Private Network OAM forwarding equivalence class stack type, length, content VPNOAM FEC TLV, and described VPN OAM FEC TLV comprises:
Target World Wide ID Target Global ID, destination node ID Target Node ID and target Route Distinguisher Target Route Distinguisher.
The third possible implementation in the possible implementation of the second of described first aspect, described VPN OAM FEC TLV also comprises:
Target interface ID Target IF ID, the interface that need to carry out OAM detection for identifying described egress PE:
Target ip address information, need to carry out OAM detection route for identifying described egress PE.
In aforementioned any one possible implementation of described first aspect or described first aspect, the 4th kind of possible implementation of described first aspect is also provided, in a described LSP Ping request message, also comprise OAM management type, length, content OAM Administration TLV, described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE.
In the 4th kind of possible implementation of described first aspect, the 5th kind of possible implementation of described first aspect is also provided, described method also comprises:
Before sending a described LSP Ping request message to described egress PE, comprising:
The OAM message receiving function of described source PE configuration source OAM entity, and the two-way detection that described OAM Administration TLV is set is masked as enabled state, so that described egress PE configures the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE transmission OAM message;
A described LSP Ping request message also comprises VPN OAM source sign type, length, content VPN OAM Source Identifier TLV, described VPN OAM Source Identifier TLV need to carry out the VPN sign of OAM detection for identifying described source PE, wherein, described VPN OAM Source Identifier TLV comprises:
The information of source World Wide ID Source Global ID, source node ID Source Node ID and source Route Distinguisher Source Route Distinguisher.
In the 5th kind of possible implementation of described first aspect, the 6th kind of possible implementation of described first aspect is also provided, described VPN OAM Source Identifier TLV also comprises:
Source interface ID Source IF ID, the interface that need to carry out OAM detection for identifying described source PE;
Source IP address information, need to carry out OAM detection route for identifying described source PE.
In the 4th kind of described first aspect or the 5th kind or the 6th kind of possible implementation, the 7th kind of possible implementation of described first aspect is also provided, alarm enabler flags in the OAM Administration TLV comprising in a described LSP Ping request message is illegal state, so that described egress PE is after the described egress OAM entity of configuration, suppress described egress OAM entity alarm report function, described, enable described source OAM entity after described egress PE sends the function of OAM message, comprising:
To described egress PE, send the 2nd LSP Ping request message, described the 2nd LSP Ping request message comprises described OAM Administration TLV, alarm enabler flags in described OAM Administration TLV is enabled state, so that described egress PE, after receiving described the 2nd LSP Ping request message, enables the alarm report function of described egress OAM entity.
In the 7th kind of possible implementation of described first aspect, the 8th kind of possible implementation of described first aspect is also provided, described method also comprises:
Receive the 2nd LSP Ping response message that described egress PE sends, described the 2nd LSP Ping response message is the response message for described the 2nd LSP Ping request message;
When the alarm enabler flags of the OAM Administration TLV comprising when described the 2nd LSP Ping response message is enabled state, enable the alarm report function of described source OAM entity.
Second aspect, a kind of method that provides OAM to configure, described method comprises:
Egress provider edge router PE receives the first label switched path the Internet packets survey meter LSP Ping request message of the source OAM physical arrangements information of carrying of source PE transmission; A described LSP Ping request message also comprises the VPN sign of Layer3 Virtual Private Network L3VPN;
According to a described LSP Ping request message configuration egress OAM entity, and configure described egress OAM entity and described VPN is identified to corresponding VPN detect, start the message receiving function of described egress OAM entity;
To described source PE, send a LSP Ping response message, a described LSP Ping response message carries the configuration information of described egress OAM entity.
In the possible implementation of the first of described second aspect, in a described LSP Ping request message, also comprise OAM management type, length, content OAM Administration TLV, described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE:
When described two-way detection flag is enabled state, described egress PE configures the OAM message sending function of described egress OAM entity, and starts described egress OAM entity to the function of described source PE transmission OAM message.
In the possible implementation of the first of described second aspect or described first aspect, the possible implementation of the second of described second aspect is also provided, when the alarm enabler flags in the OAM Administration TLV in a described described LSP Ping request message when receiving is illegal state, described egress PE is after the described egress OAM entity of configuration, suppress described egress OAM entity alarm report function, described method also comprises:
Receive the 2nd LSP Ping request message that described source PE sends, the alarm enabler flags of the OAM Administration TLV comprising in described the 2nd LSP Ping request message is enabled state, enables the alarm report function of described egress OAM entity.
In the possible implementation of the second of described second aspect, the third possible implementation of described second aspect is also provided, to described source PE, send the 2nd LSP Ping response message, described the 2nd LSP Ping response message comprises OAM Administration TLV, when the two-way detection in the OAM Administration TLV also comprising in a described LSP Ping request message is masked as enabled state, in described the 2nd LSP Ping response message, the alarm enabler flags of OAM Administration TLV is enabled state, so that described source PE is after receiving described the 2nd LSP Ping response message, enable the alarm report function of described source OAM entity.
The third aspect, provides a kind of source PE, it is characterized in that, comprising:
OAM solid element, for configuring source OAM entity, and forbids that described source OAM entity sends OAM message to described egress PE;
Generation unit, for source OAM solid generation the one LSP Ping request message configuring according to described OAM solid element, a described LSP Ping request message carries described source OAM physical arrangements information, a described LSP Ping request message also comprises the VPN sign of Layer3 Virtual Private Network L3VPN, and described VPN sign is for identifying the VPN that described egress PE equipment need to carry out OAM detection;
Transmitting element, for the described LSP Ping request message that described generation unit is generated, send to egress PE, so that described egress PE, according to a described LSP Ping request message configuration egress OAM entity, starts the message receiving function of described egress OAM entity;
Receiving element, the LSP Ping response message sending for receiving described egress PE, a described LSP Ping response message carries the egress OAM physical arrangements information of described egress PE;
Described OAM solid element, also for when definite described egress OAM physical arrangements information and the described source OAM physical arrangements information matches, enables described source OAM entity and to described egress PE, sends the function of OAM message.
In the possible implementation of the first of the described third aspect, described OAM solid element, also for when definite described egress OAM physical arrangements information is not mated with described source OAM physical arrangements information, adjust described source OAM physical arrangements information and described egress OAM physical arrangements information matches, enable described source OAM entity and to described egress PE, send the function of OAM message.
In the possible implementation of the first of the described third aspect or the described third aspect, the possible implementation of the second of the described third aspect is also provided, the described LSP Ping request message that described generation unit generates also comprises:
OAM management type, length, content OAM Administration TLV, for identifying described VPN sign; Described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE;
Send a described LSP Ping request message to described egress PE at described transmitting element before, described OAM solid element, also for configuring the OAM message receiving function of source OAM entity, and the described two-way detection that described OAM Administration TLV is set is masked as enabled state, so that described egress PE configures the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE transmission OAM message.
In the possible implementation of the second of the described third aspect, the third possible implementation of the described third aspect is also provided, alarm enabler flags in described OAM Administration TLV in the LSP Ping request message that described generation unit generates is illegal state, so that described egress PE is after the described egress OAM entity of configuration, suppress described egress OAM entity alarm report function;
At described OAM solid element, enable described source OAM entity after described egress PE sends the function of OAM message, described generation unit, also, for generating the 2nd LSP Ping request message, the alarm enabler flags in the OAM Administration TLV that described the 2nd LSP Ping request message comprises is enabled state;
Described transmitting element, also sends to described egress PE for described the 2nd LSP Ping request message that described generation unit is generated; So that described egress PE, after receiving described the 2nd LSP Ping request message, enables the alarm report function of described egress OAM entity.
In the third possible implementation of the described third aspect, the 4th kind of possible implementation of the described third aspect is also provided, described in receive unit, the 2nd LSP Ping response message also sending for receiving described egress PE;
Described OAM solid element, when the alarm enabler flags of the OAM Administration TLV also comprising for described the 2nd LSP Ping response message receiving when described receiving element is enabled state, enables the alarm report function of described source OAM entity.
Fourth aspect, provides a kind of egress PE, it is characterized in that, comprising:
Receiving element, for receiving the first label switched path the Internet packets survey meter LSP Ping request message of the source OAM physical arrangements information of carrying of source PE transmission; A described LSP Ping request message comprises the VPN sign of Layer3 Virtual Private Network L3VPN;
OAM solid element, for the described LSP Ping request message configuration egress OAM entity receiving according to described receiving element, and configure described egress OAM entity and described VPN is identified to corresponding VPN detect, start the message receiving function of described egress OAM entity;
Generation unit, for according to the egress OAM entity of described OAM solid element configuration, generates a LSP Ping response message, and a described LSP Ping response message carries described egress OAM physical arrangements information;
Transmitting element, sends to source PE for the described LSP Ping response message that generation unit is generated.
In the possible implementation of the first of described fourth aspect, the described LSP Ping request message that described receiving element receives also comprises OAM management type, length, content OAM Administration TLV, and described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE;
Described OAM solid element, while being also enabled state for the described two-way detection flag as described OAM Administration TLV, also configure the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE transmission OAM message.
In the possible implementation of the first of described fourth aspect or described fourth aspect, the possible implementation of the second of described fourth aspect is also provided, when the alarm enabler flags in the described OAM Administration TLV that described receiving element receives is illegal state, described OAM solid element, after the described egress OAM entity of configuration, suppresses described egress OAM entity alarm report function;
Described receiving element, also for receiving described the 2nd LSP Ping request message, in described the 2nd LSP Ping request message, comprise described OAM Administration TLV, and the alarm enabler flags in described OAM Administration TLV is enabled state;
Described OAM solid element, also for enabling the alarm report function of described egress OAM entity according to described the 2nd LSP Ping request message of described receiving element reception.
In the possible implementation of the second of described fourth aspect, the third possible implementation of the described third aspect is also provided, described generation unit, also for generating the 2nd LSPPing response message; Wherein, during two-way detection, the alarm enabler flags of the described OAM Administration TLV comprising in described the 2nd LSP Ping response message is enabled state;
Described transmitting element, described the 2nd LSP Ping response message also generating for send described generation unit to described source PE; So that described source PE, after receiving described the 2nd LSPPing response message, enables the alarm report function of described source OAM entity.
The 5th aspect, provides a kind of OAM configuration-system, and described system comprises:
The source PE providing in any one possible implementation that the described third aspect or the described third aspect provide;
The egress PE providing in any one possible implementation that described fourth aspect or described fourth aspect provide.
The embodiment of the present invention provides a kind of method, equipment and system of OAM configuration, after source PE equipment configuration source OAM entity, by expansion LSP Ping request message, the OAM configuration information of described source PE is sent to egress PE equipment, so that described egress PE configures the egress OAM entity of egress PE according to described source OAM configuration information, and start described egress OAM entity to the function of described source PE transmission OAM message, described LSP Ping request message has comprised the VPN sign that described egress PE need to carry out OAM detection, after the OAM physical arrangements of described source PE and egress PE is good, enable described source OAM entity and to described egress PE, send the function of OAM message, thus, completed the OAM configuration effort of source PE and egress PE, source OAM entity and egress OAM entity can enable corresponding alarm report function, by above-mentioned implementation, reduced the configuration effort amount of two ends configuration OAM, because completing OAM dynamically by mutual LSP Ping message, two ends configure, avoided the mistake occurring in manual configuration.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
OAM layoutprocedure schematic diagram between PE equipment in the VPN network that Fig. 1 provides for the embodiment of the present invention;
The schematic flow sheet of a kind of OAM collocation method that Fig. 2 provides for the embodiment of the present invention;
The OAM Function TLV schematic diagram that Fig. 3 provides for the embodiment of the present invention;
The VPNv4 OAM FEC Stack TLV form schematic diagram that Fig. 4 provides for the embodiment of the present invention;
The VPNv6OAM FEC Stack TLV form schematic diagram that Fig. 5 provides for the embodiment of the present invention;
The OAM Administration TLV form schematic diagram that Fig. 6 provides for the embodiment of the present invention;
The VPNv4 OAM Source Identifier TLV form schematic diagram that Fig. 7 provides for the embodiment of the present invention;
The VPNv6 OAM Source Identifier TLV form schematic diagram that Fig. 8 provides for the embodiment of the present invention;
The OAM Administration TLV that carries alarm enable bit position that Fig. 9 provides for the embodiment of the present invention;
The schematic flow sheet of the another kind of OAM collocation method that Figure 10 provides for the embodiment of the present invention;
The system schematic that a kind of OAM that Figure 11 provides for the embodiment of the present invention configures;
The system schematic that the another kind of OAM that Figure 12 provides for the embodiment of the present invention configures.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is only the present invention's part embodiment, rather than whole embodiment.Embodiment based in the present invention, those of ordinary skills, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
Fig. 1 is OAM layoutprocedure schematic diagram between PE equipment in VPN network, and PE1 10 represents source provider edge router PE, and PE211 represents egress provider edge router PE.PE211 issues label to PE110; PE110 is used these labels to carry out message encapsulation, to PE211 transmitting data flow.It is identical with the direction of forwarding data flow that OAM carries out the direction detecting.Under this scene, PE110 is as drive end---and be that source is initiated label switched path the Internet packets survey meter (English full name is Label Switched Path Packet Internet Grope, English referred to as LSP Ping) request message; PE211 is as Partner---and be egress response LSP Ping response message.
It should be noted that, said process is one-way process, if PE110 and PE211 two ends send label mutually, forms two-way converting, OAM is two-way execution, one end PE all can be used as source arbitrarily, and PE110 is that source PE is also egress PE, and PE211 is that egress PE is also source PE.
Referring to Fig. 2, the embodiment of the present invention provides a kind of method of OAM configuration, and the method comprises following content.
201, source PE configuration source OAM entity, and forbid that described source OAM entity sends OAM message to described egress PE.
In all embodiment of the present invention, the VPN of take in L3VPN network carries out OAM and detects as example and describe.The one end of initiatively initiating LSP Ping request message (LSP Ping Echo Request) is source PE; This LSP Ping request message of passive reception (LSP Ping Echo Reply), and the one end that responds LSP Ping response message is egress PE.
As the source PE that initiates LSP Ping request message, when configuration source OAM entity, configure source OAM sending function, for fear of source OAM entity and egress OAM entity before not consulting to configure, source OAM entity sends OAM message, and cause OAM entity and egress OAM physical arrangements unsuccessful, therefore, before source OAM entity and egress OAM entity are not being consulted to configure, forbid that described source OAM entity sends OAM message to described egress PE.
Exemplary, the same VPN under source PE and egress PE will carry out OAM detection, and now source PE and egress PE do not carry out the configuration of corresponding OAM entity, and source PE need be configured this source OAM entity.For example, can carry out following configuration to described source OAM entity: continuity detection, detection of connectivity, mismanage input, packet loss detection, delay detection, flow detection etc.
202, to described egress PE, send a LSP Ping request message that carries described source OAM physical arrangements information, so that described egress PE is according to the egress OAM entity of egress PE described in described source OAM physical arrangements information configuration, start the message receiving function of described egress OAM entity, a described LSP Ping request message also comprises the VPN sign of L3VPN, and described VPN sign is for identifying the VPN that described egress PE equipment need to carry out OAM detection.
Described egress PE can be according to the configuration information of source OAM physical arrangements information configuration egress OAM entity, for example, while comprising packet loss detection in described source OAM physical arrangements information, described egress PE also configures and carries out packet loss detection when the described egress OAM entity of configuration, but during the parameter of described egress PE configuration OAM packet loss detection, can be different with described source OAM physical arrangements information according to the ability of described egress PE.
Alternatively, described source OAM physical arrangements information can be carried by OAM(Operation Administration Maintenance) (Function) type, length, content TLV, described OAM Function TLV can be referring to [draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-03], as shown in Figure 3:
The continuity that is used for C flag bit identifying detects (English full name is Continuity Check, English referred to as CC);
V flag bit is used for identifying detection of connectivity (English full name is Connectivity Verification, English referred to as CV);
F flag bit is used for identifying mismanage input (English full name is Fault Management Signals, English referred to as FMS);
L flag bit is used for identifying packet loss detection (Loss);
D flag bit is used for identifying and postpones to detect (Delay);
T flag bit is used for identifying flow detection (English full name is Throughput Measurement, English referred to as TM).
Optionally, a described LSP Ping request message also comprises Virtual Private Network OAM forwarding equivalence class stack type, length, content (VPN OAM FEC Stack TLV), and a described LSP Ping request message carries described VPN by described VPN OAM FEC Stack TLV and identifies.Described VPN OAM FEC TLV comprises: the information of target World Wide ID (Target Global ID), destination node ID (Target Node ID) and target Route Distinguisher (Target Route Distinguisher), Fig. 4 is that described VPN OAM FEC Stack TLV carries the IPv4 VPN message format schematic diagram in when sign, and Fig. 5 is the message format schematic diagram of described VPN OAM FEC Stack TLV while carrying IPv6VPN sign.Described VPN can identify in the following manner:
Target Global ID::Target Node ID::Target Route Distinguisher (target Route Distinguisher).Alternatively, in described VPN OAM FEC Stack TLV, can also comprise: target interface ID (Target IF ID), the interface that need to carry out OAM detection for identifying described egress PE; For Fig. 4, described VPN OAM FEC Stack TLV also comprises prefix (Target IPv4 prefix) and the prefix length (Prefix Length) of Target IP v4, the IPv4VPN route that need to carry out OAM detection for identifying described egress PE; For Fig. 5, described VPN OAM FEC Stack TLV also comprises prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) of Target IP v6, for identifying described egress PE, need to carry out OAM detection IPv6VPN route.
The definition of [RFC6370] is followed in the setting of above Target Glob al_ID, Target Node_ID and Target IF_NUM, and the definition of [RFC4364] is followed in the setting of Target Route Distinguisher.
Alternatively, with reference to figure 4 and Fig. 5, the form of described VPN OAM FEC Stack TLV can be: 1-4 byte can be indicated Target Global ID, 5-8 byte can be indicated Target Node ID, 9-16 byte can be indicated Target Route Distinguisher, 17-20 byte can be indicated Target IF ID, 21-24 byte can be indicated Target IPv4prefix and Target IPv6 prefix, the 25th byte can be indicated prefix length, and 26-28 byte can be 0.
203, receive the LSP Ping response message that described egress PE sends, a described LSP Ping response message carries described egress OAM physical arrangements information, when definite described egress OAM physical arrangements information and described source OAM physical arrangements information matches, enable described source OAM entity and to described egress PE, send the function of OAM message.
When described egress PE configures after described egress OAM entity, to described source PE, send a described LSP Ping response message.Because limiting described egress OAM physical arrangements information, described egress PE self-ability may not mate with described source OAM physical arrangements information.
Alternatively, when definite described egress OAM physical arrangements information is not mated with described source OAM physical arrangements information, adjust described source OAM physical arrangements information and described egress OAM physical arrangements information matches, then, enable described source OAM entity and to described egress PE, send the function of OAM message.For instance, take packet loss detection as example, with reference to figure 3, if during the L flag bit set of sign packet loss detection, and the concrete packet loss detection mode in the configuration information of described source OAM entity is direct-detection mode (Direct), directly service message is tested, when egress PE receives after the configuration information of OAM entity, judgement egress PE only supports plug-in type detection mode (Inferred), the configuration parameter that described egress PE can only configure described egress OAM is Inferrer detection mode, described egress PE sends to described source PE to the OAM configuration information that described egress PE is supported by a described LSP Ping response message, when described source PE receives after a described LSP Ping response message, find that the OAM configuration information of described egress PE and the configuration information of described source OAM entity do not mate, the packet loss detection mode of adjusting in the configuration information of source OAM is Inferred mode.
Alternatively, source PE sends a LSP Ping request message to egress PE and also comprises: OAM management type, length, content (OAM Administration TLV), described OAM Administration TLV, Fig. 6 is described OAM Administration TLV message format schematic diagram, wherein:
Intermediate suppliers router P enables OAM and detects sign I, and whether in the middle of enabling for sign, P equipment OAM detects;
Whether alarm enabler flags A, enable OAM alarm report function for sign;
Two-way detection sign D, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE.
Optionally, shown in figure 6, the form of OAM Administration TLV can be: the type that the 1st, 2 bytes of OAM Administration TLV can be indicated OAM Administration TLV, the length that the 3rd, 4 bytes of OAM Administration TLV can be indicated OAM Administration TLV, the configuration information that the 5th to 8 bytes of OAM Administration TLV can indicate OAM to detect.
Wherein, the 1st bit of the 5th byte of OAM Administration TLV (I sign in Fig. 6) indication intermediate suppliers router P enables OAM and detects sign, whether in the middle of enabling for sign, P equipment OAM detects, if this bit set, represents to require described LSP Ping request message transmission node establishment on the way OAM Maintenance Entity intermediate point (MIP) entity.Whether the 2nd bit of the 5th byte of OAM Administration TLV (A sign in Fig. 6) enables OAM alarm report function for sign, when this bit set, receive the equipment of a described LSP Ping request message after configuring OAM entity, enable alarm report function, when detecting fault, OAM produces relevant trigger action, comprise report and alarm, when this bit resets, the suppressed and not triggering following action of alarm.D sign in the 3rd bit (Fig. 6) of the 5th byte of OAM Administration TLV) for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE, this bit set, expression need to be done two-way detection.All the other the 5th byte remaining bits and the 6th, the 7th, the 8th byte are for reserved, and convenient to OAM, configuration enables to expand in the future.
Further, for two-way detection, described source PE is before sending a described LSP Ping request message to described egress PE, described source PE also configures the OAM message receiving function of source OAM entity, and the two-way detection flag set of the OAM Administration TLV in a described LSP Ping request message is set, be about to described two-way detection sign and be set to the state of enabling, so that described egress PE also configures the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE transmission OAM message.
Optionally, for two-way detection, a described LSP Ping request message also comprises: VPN OAM source sign type, length, content (VPN OAM Source Identifier TLV), described VPN OAM Source Identifier TLV need to carry out the VPN sign of OAM detection for identifying described source PE, Fig. 7 is that described VPN OAM Source Identifier TLV carries the IPv4 VPN message format schematic diagram in when sign, Fig. 8 is that described VPN OAM Source Identifier TLV carries the IPv6VPN message format schematic diagram in when sign, wherein, described VPN OAM Source Identifier TLV comprises:
The information of the length of the type of VPN OAM Source Identifier TLV, VPN OAM Source Identifier TLV, source World Wide ID (Source Global ID), source node ID (Source Node ID) and source target Route Distinguisher (Source Route Distinguisher), the VPN that described source PE need to carry out OAM detection can identify in the following manner:
Source?Global?ID::Source?Node?ID::Source?Route?Distinguisher。
Alternatively, in described VPN OAM Source Identifier TLV, can also comprise: source interface ID (Source IF ID), the interface that need to carry out OAM detection for identifying described source PE; In Fig. 7, also comprise the prefix (Source IPv4 prefix) and the prefix length (Prefix Length) that also comprise source IPv4, the IPv4VPN route that need to carry out OAM detection for identifying described source PE; For Fig. 8, described VPN OAM FEC Stack TLV also comprises prefix information (Source IPv6 prefix) and the prefix length (Prefix Length) of source IPv6, for identifying described egress PE, need to carry out OAM detection IPv6VPN route.
Optionally, with reference to figure 7 and Fig. 8, the form of this VPN OAM Source Identifier TLV can be: 1-2 byte can be indicated the type of VPN OAM Source Identifier TLV, 3-4 byte can be indicated the length of VPN OAM Source Identifier TLV, 5-8 byte can be indicated Source Global ID, 9-16 byte can be indicated Source Node ID, 17-20 byte can be indicated Source IF ID, 21-24 byte can be indicated Source IPv4 (in Fig. 7)/IPv6prefix (in Fig. 8), the 25th byte can be indicated prefix length, 26-28 byte can be 0.
Alternatively, for preventing in described source OAM entity and described egress OAM physical arrangements process, described source OAM entity and described egress OAM entity be not before all completing configuration, or described source OAM entity and described egress OAM physical arrangements information cause described egress OAM entity to report fault alarm while not mating, further trigger described egress PE or source PE and according to false alarm, carry out the problem of faulty operation, the alarm enabler flags of OAM Administration TLV in a described LSP Ping request message can be illegal state, so that described egress PE is after the described egress OAM entity of configuration, suppress described egress OAM entity alarm report function, further, described, enable described source OAM entity after described egress PE sends the function of OAM message, comprise:
To described egress PE, send the 2nd LSP Ping request message, described the 2nd LSP Ping request message comprises OAM Administration TLV, alarm enabler flags in the OAM Administration TLV that described the 2nd LSP Ping request message comprises is enabled state, shown in figure 9, in the OAM Administration TLV carrying in described the 2nd LSP Ping request message, containing the bit 1 that enables of sign alarm (can be also any, as long as can identify, enable alarm), remaining two-way detection sign D and intermediate suppliers router P enable OAM detection sign I and all can be sky, described egress PE is after receiving described the 2nd LSP Ping request message, enable the alarm report function of described egress OAM entity.
Alternatively, described source PE receives the 2nd LSP Ping response message that described egress PE sends, described the 2nd LSP Ping response message is the response message for described the 2nd LSP Ping request message, described egress PE receives after described the 2nd LSP Ping response message, can start to send OAM detection messages to described egress PE, the VPN that described source PE and described egress PE start to comprise for a described LSP Ping request message identifies corresponding VPN and carries out OAM detection.
When the alarm enabler flags of the OAM Administration TLV comprising when described the 2nd LSP Ping response message is enabled state, enable the alarm report function of described source OAM entity.
The two-way detection flag set of OAM Administration TLV in a described LSP Ping request message, described egress PE is after the described egress OAM entity of configuration, also configure described egress OAM message sending function, start described egress PE to the OAM measuring ability of described source PE direction, and the alarm enabler flags of the OAM Administration TLV comprising in described the 2nd LSP Ping response message is set to the state of enabling, when the alarm enabler flags of the OAM Administration TLV that described the 2nd LSP Ping response message receiving as described source PE comprises is enabled state, enable the alarm report function of described source OAM entity.
In addition, it should be noted that, the process of deleting for renewal and the session of OAM configuration parameter, similar to the above process, all that source PE and egress PE carry LSP Ping request message and the LSP Ping response message of relevant information by transmission, by the negotiations process of source PE and egress PE, the parameter of intercorrelation is to carry out parameter renewal and session delete procedure.
The embodiment of the present invention provides a kind of method of OAM configuration, after source PE equipment configuration source OAM entity, by expansion LSP Ping request message, the OAM configuration information of described source PE is sent to egress PE equipment, so that described egress PE configures the egress OAM entity of egress PE according to described source OAM configuration information, and start described egress OAM entity to described source PE transmission OAM message, described LSP Ping request message has comprised the VPN sign that described egress PE need to carry out OAM detection, after the OAM physical arrangements of described source PE and egress PE is good, enable described source OAM entity and to described egress PE, send the function of OAM message, thus, completed the OAM configuration effort of source PE and egress PE, source OAM entity and egress OAM entity can enable corresponding alarm report function, by above-mentioned implementation, reduced the configuration effort amount of two ends configuration OAM, because completing OAM dynamically by mutual LSP Ping message, two ends configure, avoided the mistake occurring in manual configuration.
Referring to Figure 10, the embodiment of the present invention provides the method for another kind of OAM configuration, and the method comprises following content.
301, egress provider edge router PE receives the first label switched path the Internet packets survey meter LSP Ping request message of the source OAM physical arrangements information of carrying of source PE transmission; A described LSP Ping request message also comprises the VPN sign of Layer3 Virtual Private Network L3VPN.
302, according to a described LSP Ping request message configuration egress OAM entity, and configure described egress OAM entity and described VPN is identified to corresponding VPN detect, start the message receiving function of described egress OAM entity.
303, to described source PE, send a LSP Ping response message, a described LSPPing response message carries the configuration information of described egress OAM entity.
Alternatively, described source OAM physical arrangements information can be carried by OAM Function TLV, and described OAM Function TLV described at Fig. 3, repeated no more herein.
Optionally, a described LSP Ping request message also comprises virtual private network OAM FEC Stack TLV, and a described LSP Ping request message carries described VPN by described VPN OAM FEC Stack TLV and identifies.Described VPN OAM FEC TLV comprises: the information of target World Wide ID (Target Global ID), destination node ID (Target Node ID) and target Route Distinguisher (Target Route Distinguisher), Fig. 4 is that described VPN OAM FEC Stack TLV carries the IPv4VPN message format schematic diagram in when sign, and Fig. 5 is the message format schematic diagram of described VPN OAM FEC Stack TLV while carrying IPv6VPN sign.Described VPN can identify in the following manner:
Target Global ID::Target Node ID::Target Route Distinguisher (target Route Distinguisher).
Alternatively, in described VPN OAM FEC Stack TLV, can also comprise: target interface ID (Target IF ID), the interface that need to carry out OAM detection for identifying described egress PE; For Fig. 4, described VPN OAM FEC Stack TLV also comprises prefix (Target IPv4 prefix) and the prefix length (Prefix Length) of Target IP v4, the IPv4 VPN route that need to carry out OAM detection for identifying described egress PE; For Fig. 5, described VPN OAM FEC Stack TLV also comprises prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) of Target IP v6, for identifying described egress PE, need to carry out OAM detection IPv6VPN route.
The definition of [RFC6370] is followed in the setting of above Target Glob al_ID, Target Node_ID and Target IF_NUM, and the definition of [RFC4364] is followed in the setting of Target Route Distinguisher.
Optionally, for two-way detection, a described LSP Ping request message also comprises: VPN OAM Source Identifier TLV, described VPN OAM Source Identifier TLV need to carry out the VPN sign of OAM detection for identifying described source PE, Fig. 7 is that described VPNOAM Source Identifier TLV carries the IPv4VPN message format schematic diagram in when sign, and Fig. 8 is the message format schematic diagram of described VPN OAM Source Identifier TLV while carrying IPv6VPN sign.
Alternatively, in described VPN OAM Source Identifier TLV, can also comprise: source interface ID (Source IF ID), the interface that need to carry out OAM detection for identifying described source PE; In Fig. 7, also comprise the prefix (Source IPv4 prefix) and the prefix length (Prefix Length) that also comprise source IPv4, the IPv4VPN route that need to carry out OAM detection for identifying described source PE; For Fig. 8, described VPN OAM FEC Stack TLV also comprises prefix information (Source IPv6 prefix) and the prefix length (Prefix Length) of source IPv6, for identifying described egress PE, need to carry out OAM detection IPv6VPN route.
Alternatively, a described LSP Ping request message also comprises OAM Administration TLV, and Fig. 6, for for described OAM Administration TLV message format schematic diagram, had described, and repeated no more herein
When described two-way detection flag is enabled state, described egress PE configures the OAM message sending function of described egress OAM entity, and starts described egress OAM entity to the function of described source PE transmission OAM message.
Alternatively, when the alarm enabler flags in the OAM Administration TLV in the described LSP Ping request message receiving is illegal state, described egress PE, after the described egress OAM entity of configuration, suppresses described egress OAM entity alarm report function, and described method also comprises:
Receive the 2nd LSP Ping request message that described source PE sends, the alarm enabler flags of the OAM Administration TLV comprising in described the 2nd LSP Ping request message is enabled state, enables the alarm report function of described egress OAM entity.
Alternatively, when the two-way detection in the OAM Administration TLV also comprising in a described LSP Ping request message is masked as enabled state, to described source PE, send the 2nd LSP Ping response message, described the 2nd LSP Ping response message comprises OAM Administration TLV, in described the 2nd LSP Ping response message, the alarm enabler flags of OAM Administration TLV is enabled state, so that described source PE, after receiving described the 2nd LSP Ping response message, enables the alarm report function of described source OAM entity.
The embodiment of the present invention provides a kind of method of OAM configuration, after source PE equipment configuration source OAM entity, by expansion LSP Ping request message, the OAM configuration information of described source PE is sent to egress PE equipment, so that described egress PE configures the egress OAM entity of egress PE according to described source OAM configuration information, and start described egress OAM entity to described source PE transmission OAM message, described LSP Ping request message has comprised the VPN sign that described egress PE need to carry out OAM detection, after the OAM physical arrangements of described source PE and egress PE is good, enable described source OAM entity and to described egress PE, send the function of OAM message, thus, completed the OAM configuration effort of source PE and egress PE, source OAM entity and egress OAM entity can enable corresponding alarm report function, by above-mentioned implementation, reduced the configuration effort amount of two ends configuration OAM, because completing OAM dynamically by mutual LSP Ping message, two ends configure, avoided the mistake occurring in manual configuration.
Referring to Figure 11, the embodiment of the present invention provides a kind of system of OAM configuration, and described system comprises: source PE10 and egress PE20.
Described source PE10 comprises:
OAM solid element 101, for configuring source OAM entity, and forbids that described source OAM entity sends OAM message to described egress PE20.
Generation unit 102, for source OAM solid generation the one LSP Ping request message configuring according to described OAM solid element 101, a described LSP Ping request message carries described source OAM physical arrangements information, a described LSP Ping request message also comprises the VPN sign of L3VPN, and described VPN sign is for identifying the VPN that described egress PE equipment need to carry out OAM detection.
Transmitting element 103, sends to egress PE20 for the described LSP Ping request message that described generation unit 102 is generated.
Receiving element 104, the LSP Ping response message sending for receiving described egress PE20, a described LSP Ping response message carries described egress OAM physical arrangements information.
Described OAM solid element 101, the described egress OAM physical arrangements information of also carrying for the described LSP Ping response message receiving according to described receiving element 104, when definite described egress OAM physical arrangements information and described source OAM physical arrangements information matches, enable described source OAM entity and to described egress PE20, send the function of OAM message.
Described egress PE20 comprises:
Receiving element 201, for receiving a LSP Ping request message of the source OAM physical arrangements information of carrying that the transmitting element 103 of source PE10 sends, a described LSP Ping request message comprises the VPN sign of Layer3 Virtual Private Network L3VPN.
OAM solid element 202, for the described LSP Ping request message configuration egress OAM entity receiving according to described receiving element 201, starts the message receiving function of described egress OAM entity.
Generation unit 203, for according to the configuration information of the egress OAM entity of described OAM solid element 202 configurations, generates a LSP Ping response message, and a described LSP Ping response message carries described egress OAM physical arrangements information.
Transmitting element 204, sends to source PE10 for the described LSP Ping response message that generation unit 203 is generated.
Optionally, the OAM solid element 101 of described source P E10, also for when definite described egress OAM physical arrangements information is not mated with described source OAM physical arrangements information, adjust described source OAM physical arrangements information and described egress OAM physical arrangements information matches, enable described source OAM entity and to described egress PE20, send the function of OAM message.
Alternatively, described source OAM physical arrangements information can be carried by OAM Function TLV, and described OAM Function TLV form as shown in Figure 3.
Alternatively, the described LSP Ping request message that the generation unit 102 of described source PE10 generates also comprises VPN OAM FEC Stack TLV, and a described LSP Ping request message carries described VPN by described VPN OAM FEC Stack TLV and identifies.Described VPN OAM FEC TLV comprises: the information of target World Wide ID (Target Global ID), destination node ID (Target Node ID) and target Route Distinguisher (Target Route Distinguisher), Fig. 4 is that described VPN OAM FEC Stack TLV carries the IPv4 VPN message format schematic diagram in when sign, and Fig. 5 is the message format schematic diagram of described VPN OAM FEC Stack TLV while carrying IPv6 VPN sign.Described VPN can identify in the following manner:
Target Global ID::Target Node ID::Target Route Distinguisher (target Route Distinguisher).
Alternatively, in described VPN OAM FEC Stack TLV, can also comprise: target interface ID (Target IF ID), the interface that need to carry out OAM detection for identifying described egress PE20; For Fig. 4, described VPN OAM FEC Stack TLV also comprises prefix (Target IPv4 prefix) and the prefix length (Prefix Length) of Target IP v4, the IPv4 VPN route that need to carry out OAM detection for identifying described egress PE20; For Fig. 5, described VPN OAM FEC Stack TLV also comprises prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) of Target IP v6, for identifying described egress PE20, need to carry out OAM detection IPv6VPN route.
Alternatively, the described LSP Ping request message that the generation unit 102 of described source PE10 generates also comprises:
OAM Administration TLV, for identifying described VPN sign; Described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE;
The transmitting element 103 of described source P E10 sends a described LSP Ping request message to described egress PE20 before, the OAM solid element 101 of described source PE10, also for configuring the OAM message receiving function of source OAM entity, and the described two-way detection that described OAM Administration TLV is set is masked as enabled state, so that described egress PE20 configures the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE transmission OAM message.Correspondingly, the OAM solid element 202 of described egress PE20, while being also enabled state for the described two-way detection flag as described OAM Administration TLV, also configure the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE10 transmission OAM message.
Optionally, for two-way detection, a described LSP Ping request message also comprises: VPN OAM Source Identifier TLV, described VPN OAM Source Identifier TLV need to carry out the VPN sign of OAM detection for identifying described source PE10, Fig. 7 is that described VPN OAM Source Identifier TLV carries the IPv4VPN message format schematic diagram in when sign, and Fig. 8 is the message format schematic diagram of described VPN OAM Source Identifier TLV while carrying IPv6VPN sign.
Alternatively, in described VPN OAM Source Identifier TLV, can also comprise: source interface ID (Source IF ID), the interface that need to carry out OAM detection for identifying described source P E10; In Fig. 7, also comprise the prefix (Source IPv4 prefix) and the prefix length (Prefix Length) that also comprise source IPv4, the IPv4VPN route that need to carry out OAM detection for identifying described source PE10; For Fig. 8, described VPN OAM FEC Stack TLV also comprises prefix information (Source IPv6 prefix) and the prefix length (Prefix Length) of source IPv6, for identifying described egress PE10, need to carry out OAM detection IPv6 VPN route.
Alternatively, a described LSP Ping request message also comprises OAM Administration TLV, and Fig. 6, for for described OAM Administration TLV message format schematic diagram, had described, and repeated no more herein.
Alternatively, alarm enabler flags in described OAM Administration TLV in the LSP Ping request message that the generation unit 102 of described source PE10 generates is illegal state, when the alarm enabler flags in the described OAM Administration TLV that the receiving element 201 of described egress PE20 receives is illegal state, the OAM solid element 202 of described egress PE20, after the described egress OAM entity of configuration, suppresses described egress OAM entity alarm report function.
At the OAM of described source PE10 solid element 101, enable described source OAM entity after described egress PE sends the function of OAM message, the generation unit 102 of described source PE10, also, for generating the 2nd LSP Ping request message, the alarm enabler flags in the OAM Administration TLV that described the 2nd LSP Ping request message comprises is enabled state.
Correspondingly, described receiving element 201, also, for receiving described the 2nd LSP Ping request message, the OAM solid element 202 of described egress PE20, also for enabling the alarm report function of described egress OAM entity according to described the 2nd LSP Ping request message of described receiving element 201 receptions.
The transmitting element 103 of described source PE10, also for described the 2nd LSP Ping request message that described generation unit 102 is generated, send to described egress PE20, correspondingly the receiving element 201 of described egress PE20 is also for receiving described the 2nd LSP Ping request message, the OAM solid element 202 of described egress PE20 is also for when the described receiving element 201 of judgement is also when receiving the alarm enabler flags of the OAM Administration TLV that described the 2nd LSP Ping request message comprises and be enabled state, enable the alarm report function of described egress OAM entity.
Alternatively, described source PE10 receives unit 104, the 2nd LSP Ping response message also sending for receiving described egress PE20.
The generation unit 203 of described egress PE20, also for generating the 2nd LSP Ping response message; Wherein, during two-way detection, the alarm enabler flags of the described OAM Administration TLV comprising in described the 2nd LSP Ping response message is enabled state.
The transmitting element 204 of described egress PE20, described the 2nd LSP Ping response message also generating for send described generation unit 203 to described source PE10.
The OAM solid element 101 of described source PE10, when the alarm enabler flags of the OAM Administration TLV also comprising for described the 2nd LSP Ping response message receiving when described receiving element 104 is enabled state, enable the alarm report function of described source OAM entity.
The embodiment of the present invention provides a kind of system of OAM configuration, after source PE10 configuration source OAM entity, by expansion LSP Ping request message, the OAM configuration information of described source PE10 is sent to egress PE20 equipment, so that described egress PE20 configures the egress OAM entity of egress PE20 according to described source OAM configuration information, and start described egress OAM entity to described source PE10 transmission OAM message, described LSP Ping request message has comprised the VPN sign that described egress PE20 need to carry out OAM detection, after the OAM physical arrangements of described source PE10 and egress PE20 is good, enable described source OAM entity and to described egress PE20, send the function of OAM message, thus, completed the OAM configuration effort of source PE10 and egress PE20, source OAM entity and egress OAM entity can enable corresponding alarm report function, by above-mentioned implementation, reduced the configuration effort amount of two ends configuration OAM, because completing OAM dynamically by mutual LSP Ping message, two ends configure, avoided the mistake occurring in manual configuration.
Referring to Figure 12, the embodiment of the present invention provides the system of another kind of OAM configuration, and described system comprises: source PE30 and egress PE40.
Described source PE30 comprises:
Processor 301, be used for configuring source OAM entity, and forbid that described source OAM entity sends OAM message to described egress PE30, also for generating a LSP Ping request message, a described LSP Ping request message carries described source OAM physical arrangements information, a described LSP Ping request message also comprises the VPN sign of L3VPN, and described VPN sign is for identifying the VPN that described egress PE40 need to carry out OAM detection.
Transmitter 302, sends to egress PE40 for the described LSP Ping request message that described processor 301 is generated.
Receiver 303, the LSP Ping response message sending for receiving described egress PE40, a described LSP Ping response message carries described egress OAM physical arrangements information.
Described processor 301, the egress OAM physical arrangements information of also carrying for the described LSP Ping response message receiving according to described receiver 303, when definite described egress OAM physical arrangements information and described source OAM physical arrangements information matches, enable described source OAM entity and to described egress PE40, send the function of OAM message.
Described egress PE40 comprises:
Receiver 401, for receiving a LSP Ping request message of the source OAM physical arrangements information of carrying that the transmitter 302 of source PE30 sends; A described LSP Ping request message comprises the VPN sign of L3VPN.
Processor 402, for the described LSP Ping request message configuration egress OAM entity receiving according to described receiver 401, start the message receiving function of described egress OAM entity, and for generating a LSP Ping response message, a described LSP Ping response message carries described egress OAM physical arrangements information.
Transmitter 403, sends to source PE30 for the described LSP Ping response message that processor 402 is generated.
Optionally, described processor 301 is not also for when definite described egress OAM physical arrangements information is mated with described source OAM physical arrangements information, adjust described source OAM physical arrangements information and described egress OAM physical arrangements information matches, enable described source OAM entity and to described egress PE40, send the function of OAM message.
Alternatively, described source OAM physical arrangements information can be carried by OAM Function TLV, and described OAM Function TLV form as shown in Figure 3.
Alternatively, the described LSP Ping request message that the processor 301 of described source PE30 generates also comprises VPN OAM FEC Stack TLV, and a described LSP Ping request message carries described VPN by described VPN OAM FEC Stack TLV and identifies.Described VPN OAM FEC TLV comprises: the information of target World Wide ID (Target Global ID), destination node ID (Target Node ID) and target Route Distinguisher (Target Route Distinguisher), Fig. 4 is that described VPN OAM FEC Stack TLV carries the IPv4VPN message format schematic diagram in when sign, and Fig. 5 is the message format schematic diagram of described VPN OAM FEC Stack TLV while carrying IPv6 VPN sign.Described VPN can identify in the following manner:
Target Global ID::Target Node ID::Target Route Distinguisher (target Route Distinguisher).
Alternatively, in described VPN OAM FEC Stack TLV, can also comprise: target interface ID (Target IF ID), the interface that need to carry out OAM detection for identifying described egress PE40; For Fig. 4, described VPN OAM FEC Stack TLV also comprises prefix (Target IPv4 prefix) and the prefix length (Prefix Length) of Target IP v4, the IPv4 VPN route that need to carry out OAM detection for identifying described egress PE20; For Fig. 5, described VPN OAM FEC Stack TLV also comprises prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) of Target IP v6, for identifying described egress PE20, need to carry out OAM detection IPv6VPN route.
Alternatively, the described LSP Ping request message that the processor 301 of described source PE30 generates also comprises:
OAM Administration TLV, for identifying described VPN sign; Described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE.
The transmitter 303 of described source PE30 sends a described LSP Ping request message to described egress PE40 before, the processor 301 of described source PE30, also for configuring the OAM message receiving function of source OAM entity, and the described two-way detection that described OAM Administration TLV is set is masked as enabled state.Correspondingly, the processor 402 of described egress PE40, while being also enabled state for the described two-way detection flag as described OAM Administration TLV, also configure the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE30 transmission OAM message.
Optionally, for two-way detection, a described LSP Ping request message also comprises: VPN OAM Source Identifier TLV, described VPN OAM S ource Identifier TLV need to carry out the VPN sign of OAM detection for identifying described source PE30, Fig. 7 is that described VPN OAM Source Identifier TLV carries the IPv4VPN message format schematic diagram in when sign, and Fig. 8 is the message format schematic diagram of described VPN OAM Source Identifier TLV while carrying IPv6VPN sign.
Alternatively, in described VPN OAM Source Identifier TLV, can also comprise: source interface ID (Source IF ID), the interface that need to carry out OAM detection for identifying described source PE30; In Fig. 7, also comprise the prefix (Source IPv4 prefix) and the prefix length (Prefix Length) that also comprise source IPv4, the IPv4VPN route that need to carry out OAM detection for identifying described source PE30; For Fig. 8, described VPN OAM FEC Stack TLV also comprises prefix information (Source IPv6 prefix) and the prefix length (Prefix Length) of source IPv6, for identifying described egress PE30, need to carry out OAM detection IPv6 VPN route.
Alternatively, a described LSP Ping request message also comprises OAM Administration TLV, and Fig. 6 is described OAM Administration TLV message format schematic diagram, describes, and repeats no more herein.
Alternatively, alarm enabler flags in described OAM Administration TLV in the LSP Ping request message that the processor 301 of described source PE30 generates is illegal state, when the alarm enabler flags in the described OAM Administration TLV that described receiver 401 receives is illegal state, described processor 402, after the described egress OAM entity of configuration, suppresses described egress OAM entity alarm report function.
Processor 301 at described source PE30 enables described source OAM entity after described egress PE40 sends the function of OAM message, described processor 301 is also for generating the 2nd LSP Ping request message, and the alarm enabler flags in the OAMAdministration TLV that described the 2nd LSP Ping request message comprises is enabled state.
Correspondingly, the receiver 401 of described egress PE40 is also for receiving described the 2nd LSPPing request message, described processor 402, also for enabling the alarm report function of described egress OAM entity according to described the 2nd LSP Ping request message of described receiver 401 receptions.
The transmitter 302 of described source PE30, also for described the 2nd LSP Ping request message that described processor 301 is generated, send to described egress PE40, correspondingly described receiver 401 is also for receiving described the 2nd LSP Ping request message, described processor 402 also when receiving the alarm enabler flags of the OAM Administration TLV that described the 2nd LSP Ping request message comprises when the described receiver 401 of judgement and be enabled state, enables the alarm report function of described egress OAM entity.
Alternatively, described source PE30 receives device 303, the 2nd LSP Ping response message also sending for receiving described egress PE40.
The processor 402 of described egress PE40, also for generating the 2nd LSP Ping response message; Wherein, during two-way detection, the alarm enabler flags of the described OAM Administration TLV comprising in described the 2nd LSP Ping response message is enabled state.
The transmitter 403 of described egress PE40, described the 2nd LSP Ping response message also generating for send described processor 402 to described source PE30.
The processor 303 of described source PE30, when the alarm enabler flags of the OAM Administration TLV also comprising for described the 2nd LSP Ping response message of receiving when described receiver 303 is enabled state, enable the alarm report function of described source OAM entity.
The embodiment of the present invention provides a kind of system of OAM configuration, after source PE30 configuration source OAM entity, by expansion LSP Ping request message, the OAM configuration information of described source PE30 is sent to egress PE40 equipment, so that described egress PE40 configures the egress OAM entity of egress PE40 according to described source OAM configuration information, and start described egress OAM entity to described source PE30 transmission OAM message, described LSP Ping request message has comprised the VPN sign that described egress PE40 need to carry out OAM detection, after the OAM physical arrangements of described source PE30 and egress PE40 is good, enable described source OAM entity and to described egress PE40, send the function of OAM message, thus, completed the OAM configuration effort of source PE30 and egress PE40, source OAM entity and egress OAM entity can enable corresponding alarm report function, by above-mentioned implementation, reduced the configuration effort amount of two ends configuration OAM, because completing OAM dynamically by mutual LSP Ping message, two ends configure, avoided the mistake occurring in manual configuration.
Described source PE30 and described egress PE40 can be router or switch.
Alternatively, the processor 301 of above-mentioned source PE30 and the processor 402 of egress PE40 can be central processing unit (English full name is Central Processing Unit, English referred to as CPU).Receiver 401, the transmitter 403 of the receiver 303 of above-mentioned source PE30, transmitter 302, egress PE40 can comprise General Physics interface, described physical interface can be ether (Ethernet) interface or asynchronous transfer mode (English full name is Asynchronous Transfer Mode, English referred to as ATM) interface.The receiver 303 of above-mentioned source PE30, processor 301 and transmitter 302 can be integrated into one or more independently circuit or hardware, as: (English full name is Application Specific Integrated Circuit to application-specific integrated circuit (ASIC), English referred to as ASIC), the receiver 401 of above-mentioned egress PE40, processor 402, transmitter 403 can be integrated into one or more independently circuit or hardware, as: ASIC.
One of ordinary skill in the art will appreciate that: all or part of step that realizes said method embodiment can complete by the relevant hardware of program command, aforementioned program can be stored in a computer read/write memory medium, this program, when carrying out, is carried out the step that comprises said method embodiment; And aforesaid storage medium comprises: various media that can be program code stored such as read-only memory (English full name is read-only memory, English referred to as ROM), RAM, magnetic disc or CDs.
Finally it should be noted that: above embodiment only, in order to exemplary illustration technical scheme of the present invention, is not intended to limit; Although beneficial effect the present invention and the present invention being brought with reference to previous embodiment has been described in detail, those of ordinary skill in the art is to be understood that: its technical scheme that still can record aforementioned each embodiment is modified, or part technical characterictic is wherein equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution depart from the scope of the claims in the present invention.

Claims (23)

1. a method for Operations, Administration and Maintenance OAM configuration, is characterized in that, comprising:
Source provider edge router PE configuration source OAM entity, and forbid that described source OAM entity sends OAM message to described egress PE;
To described egress PE, send the first label switched path the Internet packets survey meter LSP Ping request message that carries described source OAM physical arrangements information, so that described egress PE is according to the egress OAM entity of egress PE described in described source OAM physical arrangements information configuration, start the message receiving function of described egress OAM entity, a described LSP Ping request message also comprises the VPN sign of Layer3 Virtual Private Network L3VPN, and described VPN sign is for identifying the VPN that described egress PE equipment need to carry out OAM detection;
Receive the LSP Ping response message that described egress PE sends, a described LSP Ping response message carries described egress OAM physical arrangements information, when definite described egress OAM physical arrangements information and described source OAM physical arrangements information matches, enable described source OAM entity and to described egress PE, send the function of OAM message.
2. method according to claim 1, is characterized in that, comprising:
When definite described egress OAM physical arrangements information is not mated with described source OAM physical arrangements information, adjust described source OAM physical arrangements information and described egress OAM physical arrangements information matches, enable described source OAM entity and to described egress PE, send the function of OAM message.
3. method according to claim 1 and 2, it is characterized in that, a described LSP Ping request message is carried described VPN and is identified by Virtual Private Network OAM forwarding equivalence class stack type, length, content VPN OAM FEC TLV, and described VPN OAM FEC TLV comprises:
Target World Wide ID Target Global ID, destination node ID Target Node ID and target Route Distinguisher Target Route Distinguisher.
4. method according to claim 3, is characterized in that, described VPN OAM FEC TLV also comprises:
Target interface ID Target IF ID, the interface that need to carry out OAM detection for identifying described egress PE;
Target ip address information, need to carry out OAM detection route for identifying described egress PE.
5. according to the method described in the arbitrary claim of claim 1 to 4, it is characterized in that,
In a described LSP Ping request message, also comprise OAM management type, length, content OAM Administration TLV, described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE.
6. method according to claim 5, is characterized in that, before sending a described LSP Ping request message, comprising to described egress PE:
The OAM message receiving function of described source PE configuration source OAM entity, and the two-way detection that described OAM Administration TLV is set is masked as enabled state, so that described egress PE configures the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE transmission OAM message;
A described LSP Ping request message also comprises VPN OAM source sign type, length, content VPN OAM S ource Identifier TLV, described VPN OAM Source Identifier TLV need to carry out the VPN sign of OAM detection for identifying described source PE, wherein, described VPN OAM Source Identifier TLV comprises:
The information of source World Wide ID Source Global ID, source node ID Source Node ID and source Route Distinguisher Source Route Distinguisher.
7. method according to claim 6, is characterized in that, described VPN OAM Source Identifier TLV also comprises:
Source interface ID Source IF ID, the interface that need to carry out OAM detection for identifying described source PE;
Source IP address information, need to carry out OAM detection route for identifying described source PE.
8. according to the method described in the arbitrary claim of claim 5 to 7, it is characterized in that, alarm enabler flags in the OAM Administration TLV comprising in a described LSP Ping request message is illegal state, so that described egress PE is after the described egress OAM entity of configuration, suppress described egress OAM entity alarm report function, described, enable described source OAM entity after described egress PE sends the function of OAM message, comprising:
To described egress PE, send the 2nd LSP Ping request message, described the 2nd LSP Ping request message comprises described OAM Administration TLV, alarm enabler flags in described OAM Administration TLV is enabled state, so that described egress PE, after receiving described the 2nd LSP Ping request message, enables the alarm report function of described egress OAM entity.
9. method according to claim 8, is characterized in that, comprising:
Receive the 2nd LSP Ping response message that described egress PE sends, described the 2nd LSP Ping response message is the response message for described the 2nd LSP Ping request message;
When the alarm enabler flags of the OAM Administration TLV comprising when described the 2nd LSP Ping response message is enabled state, enable the alarm report function of described source OAM entity.
10. a method for Operations, Administration and Maintenance OAM configuration, is characterized in that, comprising:
Egress provider edge router PE receives the first label switched path the Internet packets survey meter LSP Ping request message of the source OAM physical arrangements information of carrying of source PE transmission; A described LSP Ping request message also comprises the VPN sign of Layer3 Virtual Private Network L3VPN;
According to a described LSP Ping request message configuration egress OAM entity, and configure described egress OAM entity and described VPN is identified to corresponding VPN detect, start the message receiving function of described egress OAM entity;
To described source PE, send a LSP Ping response message, a described LSP Ping response message carries the configuration information of described egress OAM entity.
11. methods according to claim 10, is characterized in that, in a described LSP Ping request message, also comprise OAM management type, length, content OAM Administration TLV, and described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE;
When described two-way detection flag is enabled state, described egress PE configures the OAM message sending function of described egress OAM entity, and starts described egress OAM entity to the function of described source PE transmission OAM message.
12. according to the method described in claim 10 or 11, it is characterized in that, when the alarm enabler flags in the OAM Administration TLV in the described LSP Ping request message receiving is illegal state, described egress PE is after the described egress OAM entity of configuration, suppress described egress OAM entity alarm report function, described method also comprises:
Receive the 2nd LSP Ping request message that described source PE sends, the alarm enabler flags of the OAM Administration TLV comprising in described the 2nd LSPPing request message is enabled state, enables the alarm report function of described egress OAM entity.
13. methods according to claim 12, is characterized in that, comprising:
To described source PE, send the 2nd LSP Ping response message, described the 2nd LSP Ping response message comprises OAM Administration TLV, when the two-way detection in the OAM Administration TLV also comprising in a described LSP Ping request message is masked as enabled state, in described the 2nd LSP Ping response message, the alarm enabler flags of OAM Administration TLV is enabled state, so that described source PE, after receiving described the 2nd LSP Ping response message, enables the alarm report function of described source OAM entity.
14. 1 kinds of source provider edge router PE, is characterized in that, comprising:
OAM solid element, for configuring source OAM entity, and forbids that described source OAM entity sends OAM message to described egress PE;
Generation unit, for source OAM solid generation the one LSP Ping request message configuring according to described OAM solid element, a described LSP Ping request message carries described source OAM physical arrangements information, a described LSP Ping request message also comprises the VPN sign of Layer3 Virtual Private Network L3VPN, and described VPN sign is for identifying the VPN that described egress PE equipment need to carry out OAM detection;
Transmitting element, for the described LSP Ping request message that described generation unit is generated, send to egress PE, so that described egress PE, according to a described LSP Ping request message configuration egress OAM entity, starts the message receiving function of described egress OAM entity;
Receiving element, the LSP Ping response message sending for receiving described egress PE, a described LSP Ping response message carries the egress OAM physical arrangements information of described egress PE;
Described OAM solid element, also for when definite described egress OAM physical arrangements information and the described source OAM physical arrangements information matches, enables described source OAM entity and to described egress PE, sends the function of OAM message.
15. source PE according to claim 14, it is characterized in that, described OAM solid element, also for when definite described egress OAM physical arrangements information is not mated with described source OAM physical arrangements information, adjust described source OAM physical arrangements information and described egress OAM physical arrangements information matches, enable described source OAM entity and to described egress PE, send the function of OAM message.
16. according to the source PE described in claims 14 or 15, it is characterized in that, the described LSP Ping request message that described generation unit generates also comprises:
OAM management type, length, content OAM Administration TLV, for identifying described VPN sign; Described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE;
Send a described LSP Ping request message to described egress PE at described transmitting element before, described OAM solid element, also for configuring the OAM message receiving function of source OAM entity, and the described two-way detection that described OAM Administration TLV is set is masked as enabled state, so that described egress PE configures the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE transmission OAM message.
17. source PE according to claim 16, it is characterized in that, alarm enabler flags in described OAM Administration TLV in the LSP Ping request message that described generation unit generates is illegal state, so that described egress PE is after the described egress OAM entity of configuration, suppress described egress OAM entity alarm report function;
At described OAM solid element, enable described source OAM entity after described egress PE sends the function of OAM message, described generation unit, also, for generating the 2nd LSP Ping request message, the alarm enabler flags in the OAM Administration TLV that described the 2nd LSP Ping request message comprises is enabled state;
Described transmitting element, also sends to described egress PE for described the 2nd LSP Ping request message that described generation unit is generated; So that described egress PE, after receiving described the 2nd LSP Ping request message, enables the alarm report function of described egress OAM entity.
18. source PE according to claim 17, is characterized in that, comprising:
The described unit that receives, the 2nd LSP Ping response message also sending for receiving described egress PE;
Described OAM solid element, when the alarm enabler flags of the OAM Administration TLV also comprising for described the 2nd LSP Ping response message receiving when described receiving element is enabled state, enables the alarm report function of described source OAM entity.
19. 1 kinds of egress provider edge router PE, is characterized in that, comprising:
Receiving element, for receiving the first label switched path the Internet packets survey meter LSP Ping request message of the source OAM physical arrangements information of carrying of source PE transmission; A described LSP Ping request message comprises the VPN sign of Layer3 Virtual Private Network L3VPN;
OAM solid element, for the described LSP Ping request message configuration egress OAM entity receiving according to described receiving element, and configure described egress OAM entity and described VPN is identified to corresponding VPN detect, start the message receiving function of described egress OAM entity;
Generation unit, for according to the egress OAM entity of described OAM solid element configuration, generates a LSP Ping response message, and a described LSP Ping response message carries described egress OAM physical arrangements information;
Transmitting element, sends to source PE for the described LSP Ping response message that generation unit is generated.
20. according to the egress PE described in the arbitrary claim of claim 19, it is characterized in that,
The described LSP Ping request message that described receiving element receives also comprises OAM management type, length, content OAM Administration TLV, and described OAM Administration TLV comprises:
Whether alarm enabler flags, enable OAM alarm report function for sign;
Two-way detection sign, for identifying the two-way OAM measuring ability of whether setting up between described source PE and egress PE;
Described OAM solid element, while being also enabled state for the described two-way detection flag as described OAM Administration TLV, also configure the OAM message sending function of described egress OAM entity, and start described egress OAM entity to the function of described source PE transmission OAM message.
21. according to the egress PE described in claim 19 or 20, it is characterized in that,
When the alarm enabler flags in the described OAM Administration TLV that described receiving element receives is illegal state, described OAM solid element, after the described egress OAM entity of configuration, suppresses described egress OAM entity alarm report function;
Described receiving element, also for receiving described the 2nd LSP Ping request message, in described the 2nd LSP Ping request message, comprise described OAM Administration TLV, and the alarm enabler flags in described OAM Administration TLV is enabled state;
Described OAM solid element, also for enabling the alarm report function of described egress OAM entity according to described the 2nd LSP Ping request message of described receiving element reception.
22. egress PE according to claim 21, is characterized in that, comprising:
Described generation unit, also for generating the 2nd LSP Ping response message; Wherein, during two-way detection, the alarm enabler flags of the described OAM Administration TLV comprising in described the 2nd LSP Ping response message is enabled state;
Described transmitting element, described the 2nd LSP Ping response message also generating for send described generation unit to described source PE; So that described source PE, after receiving described the 2nd LSP Ping response message, enables the alarm report function of described source OAM entity.
23. 1 kinds of OAM configuration-systems, is characterized in that, comprising:
Source provider edge router PE described in the arbitrary claim of claim 14 to 18, and the egress provider edge router PE described in the arbitrary claim of claim 19 to 22.
CN201210268576.7A 2012-07-31 2012-07-31 Method, equipment and the system of Operations, Administration and Maintenance OAM configurations Active CN103580894B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201210268576.7A CN103580894B (en) 2012-07-31 2012-07-31 Method, equipment and the system of Operations, Administration and Maintenance OAM configurations
PCT/CN2013/070534 WO2014019348A1 (en) 2012-07-31 2013-01-16 Method, device and system for operation, management and maintenance of oam configuration

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201210268576.7A CN103580894B (en) 2012-07-31 2012-07-31 Method, equipment and the system of Operations, Administration and Maintenance OAM configurations

Publications (2)

Publication Number Publication Date
CN103580894A true CN103580894A (en) 2014-02-12
CN103580894B CN103580894B (en) 2017-09-29

Family

ID=50027186

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201210268576.7A Active CN103580894B (en) 2012-07-31 2012-07-31 Method, equipment and the system of Operations, Administration and Maintenance OAM configurations

Country Status (2)

Country Link
CN (1) CN103580894B (en)
WO (1) WO2014019348A1 (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103957213A (en) * 2014-05-05 2014-07-30 上海大亚科技有限公司 System and method for achieving network service opening and closing based on PING packet
CN104270280A (en) * 2014-09-02 2015-01-07 烽火通信科技股份有限公司 System and method for realizing LSP (Label Switching Path) ping and tracert on router
WO2015184771A1 (en) * 2014-10-17 2015-12-10 中兴通讯股份有限公司 Method and node device for operation, administration, and maintenance of service function chaining
WO2016058245A1 (en) * 2014-10-17 2016-04-21 中兴通讯股份有限公司 Processing method and apparatus for operation, administration and maintenance (oam) message
WO2018210213A1 (en) * 2017-05-18 2018-11-22 中兴通讯股份有限公司 Method and device for implementing ioam packaging and storage medium
CN105591798B (en) * 2015-07-24 2019-04-09 新华三技术有限公司 The method, apparatus of OAM Information is transmitted in DCN
CN110505035A (en) * 2018-05-16 2019-11-26 华为技术有限公司 Data processing method and device, communication system
CN110545196A (en) * 2018-05-28 2019-12-06 华为技术有限公司 data transmission method and related network equipment
CN110933002A (en) * 2019-11-25 2020-03-27 苏州盛科科技有限公司 Method and device for realizing switching chip of MPLS in-band detection OAM
WO2022048466A1 (en) * 2020-09-03 2022-03-10 华为技术有限公司 Operation administration and maintenance (oam) packet processing method and device

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015149353A1 (en) 2014-04-04 2015-10-08 华为技术有限公司 Oam packet processing method, network device and network system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1625176A (en) * 2003-12-03 2005-06-08 华为技术有限公司 Realization method of edge to edge pseudo-line simulation protocol
CN1848775A (en) * 2005-09-30 2006-10-18 华为技术有限公司 Multi-jumping pseudo-line fault detecting reporting and maintenance protocol controlling method
WO2008144606A1 (en) * 2007-05-19 2008-11-27 Cisco Technology, Inc. Interworking between mpls/ip and ethernet oam mechanisms
CN102332987A (en) * 2010-07-12 2012-01-25 中兴通讯股份有限公司 Method and system for configuration of OAM attribute of pseudowire

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355441B (en) * 2007-07-27 2012-04-04 华为技术有限公司 Method, system and equipment for configuring operation management maintain attribute
US7808919B2 (en) * 2008-03-18 2010-10-05 Cisco Technology, Inc. Network monitoring using a proxy

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1625176A (en) * 2003-12-03 2005-06-08 华为技术有限公司 Realization method of edge to edge pseudo-line simulation protocol
CN1848775A (en) * 2005-09-30 2006-10-18 华为技术有限公司 Multi-jumping pseudo-line fault detecting reporting and maintenance protocol controlling method
WO2008144606A1 (en) * 2007-05-19 2008-11-27 Cisco Technology, Inc. Interworking between mpls/ip and ethernet oam mechanisms
CN102332987A (en) * 2010-07-12 2012-01-25 中兴通讯股份有限公司 Method and system for configuration of OAM attribute of pseudowire

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103957213A (en) * 2014-05-05 2014-07-30 上海大亚科技有限公司 System and method for achieving network service opening and closing based on PING packet
CN104270280A (en) * 2014-09-02 2015-01-07 烽火通信科技股份有限公司 System and method for realizing LSP (Label Switching Path) ping and tracert on router
CN104270280B (en) * 2014-09-02 2017-11-07 烽火通信科技股份有限公司 LSP ping and tracert system and method is realized on the router
CN105577413B (en) * 2014-10-17 2019-09-10 中兴通讯股份有限公司 Operations, Administration and Maintenance OAM message processing method and processing device
WO2015184771A1 (en) * 2014-10-17 2015-12-10 中兴通讯股份有限公司 Method and node device for operation, administration, and maintenance of service function chaining
WO2016058245A1 (en) * 2014-10-17 2016-04-21 中兴通讯股份有限公司 Processing method and apparatus for operation, administration and maintenance (oam) message
CN105577413A (en) * 2014-10-17 2016-05-11 中兴通讯股份有限公司 OAM (Operation, Administration and Management) message processing method and device
CN105591798B (en) * 2015-07-24 2019-04-09 新华三技术有限公司 The method, apparatus of OAM Information is transmitted in DCN
WO2018210213A1 (en) * 2017-05-18 2018-11-22 中兴通讯股份有限公司 Method and device for implementing ioam packaging and storage medium
CN110505035A (en) * 2018-05-16 2019-11-26 华为技术有限公司 Data processing method and device, communication system
CN110545196A (en) * 2018-05-28 2019-12-06 华为技术有限公司 data transmission method and related network equipment
CN110933002A (en) * 2019-11-25 2020-03-27 苏州盛科科技有限公司 Method and device for realizing switching chip of MPLS in-band detection OAM
CN110933002B (en) * 2019-11-25 2021-12-28 苏州盛科科技有限公司 Method and device for realizing switching chip of MPLS in-band detection OAM
WO2022048466A1 (en) * 2020-09-03 2022-03-10 华为技术有限公司 Operation administration and maintenance (oam) packet processing method and device

Also Published As

Publication number Publication date
CN103580894B (en) 2017-09-29
WO2014019348A1 (en) 2014-02-06

Similar Documents

Publication Publication Date Title
CN103580894A (en) Method, device and system for operation, administration and maintenance (OAM) configuration
US11303564B2 (en) Packet forwarding method, apparatus, and system
EP3154227B1 (en) Packet transmission method, node, path management server and storage medium
WO2018210213A1 (en) Method and device for implementing ioam packaging and storage medium
US8023506B2 (en) Method and provider edge device for advertising and processing pseudo-wire information
CN102868569B (en) The method for testing performance of Layer3 Virtual Private Network, node and system
WO2013097459A1 (en) Service path detection method and device
WO2018210225A1 (en) Method and device for automatically implementing ioam encapsulation, and storage medium
CN101989947A (en) Associated channel capability negotiation method and network device
WO2018219303A1 (en) Defect detection in ip/mpls network tunnels
CN105812198B (en) Method and device for monitoring end-to-end of bridge network
EP2832061B1 (en) Pseudowire extended group messaging in a packet switched network
EP2832055B1 (en) Pseudowire groups in a packet switched network
WO2019165803A1 (en) Message processing method and apparatus, and message encapsulating method, apparatus and system
CN107666671B (en) Method and device for detecting wrong connection based on TWAMP
CN102025619B (en) Method and system as well as equipment for transmitting response message
CN104270280A (en) System and method for realizing LSP (Label Switching Path) ping and tracert on router
CN112737949A (en) Fault detection method and device, electronic equipment and computer readable medium
KR101888041B1 (en) Method and apparatus for network diagnosis processing
CN102624746A (en) Method, source port, destination port and system for detecting configuration of GRE (generic route encapsulation) headers at two ends of tunnel
WO2022000264A1 (en) Fault detection method and apparatus, and pe device
WO2020238799A1 (en) Twamp-based detection method and related device
EP2832056B1 (en) Pseudowire extended group actions in a packet switched network
CN117319270A (en) Network testing method and related device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant