WO2014019348A1 - Procédé, dispositif et système pour l'exploitation, la gestion et la maintenance de configuration oam - Google Patents

Procédé, dispositif et système pour l'exploitation, la gestion et la maintenance de configuration oam Download PDF

Info

Publication number
WO2014019348A1
WO2014019348A1 PCT/CN2013/070534 CN2013070534W WO2014019348A1 WO 2014019348 A1 WO2014019348 A1 WO 2014019348A1 CN 2013070534 W CN2013070534 W CN 2013070534W WO 2014019348 A1 WO2014019348 A1 WO 2014019348A1
Authority
WO
WIPO (PCT)
Prior art keywords
oam
source
sink
entity
lsp ping
Prior art date
Application number
PCT/CN2013/070534
Other languages
English (en)
Chinese (zh)
Inventor
古锐
董杰
郑莲淑
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2014019348A1 publication Critical patent/WO2014019348A1/fr

Links

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

Definitions

  • the present invention relates to the field of network communications, and in particular, to a method, a device, and a system for configuring an OAM.
  • OAM Operations, Administration and Maintenance
  • OAM is an important symbol of a carrier-class network. It is extremely important for operators. OAM can reduce the complexity of operators. Degrees and operation and maintenance costs can enhance the availability of the carrier network. It can also help the carrier network to verify the SLA (Service Level Agreement).
  • the OAM mechanism mainly includes three aspects: fault management, performance monitoring, and protection switching.
  • Fault management can be divided into four aspects: fault detection, fault verification, fault localization and fault notification.
  • Performance monitoring mainly provides packet loss and delay. And monitoring of the three indicators of jitter.
  • IP/MPLS Internet Protocol/Multiprotocol Label Switching
  • Ethernet Ethernet
  • MPLS-TP Packet switching network technology
  • the former includes IEEE 802.3ah, IEEE 802. lag, ITU-T Y.1731 and some Metro Ethernet Forums (English called Metro Ethernet Forum, English abbreviated as MEF).
  • MEF Metro Ethernet Forum
  • a virtual private network (English for Virtual Private Network, English abbreviated as VPN) is a virtual private network that operators provide to users through their public networks. That is, VPN is a proprietary network of users from the perspective of users.
  • the public network includes public Backbone network and public carrier border equipment.
  • the geographically separated VPN member sites are connected to the corresponding carrier edge routers (English Provider Edge, referred to as PEs) through the client device (CPE), and form the customer's VPN network through the operator's public network.
  • PEs International Provider Edge, referred to as PEs
  • CPE client device
  • the Layer 3 Virtual Private Network (L3VPN in English) is a three-layer VPN technology based on MPLS.
  • L3VPN On the L3VPN network, you need to manually create the OAM entity of the source PE and the sink PE, and configure the parameters of the OAM entity of the source PE and the sink PE respectively.
  • the configuration parameters of the OAM entity of the sink PE are the same as those of the OAM entity of the source PE. This not only makes the OAM configuration work much larger, but also is prone to configuration errors.
  • the embodiments of the present invention provide a method, a device, and a system for configuring an OAM to solve the problem of large configuration and configuration errors caused by manual configuration when a PE device is configured to detect a VPN by an OAM in an L3 VPN network. The problem.
  • a method for configuring an OAM includes: configuring, by a source end operator, an edge router, a source OAM entity, and disabling the source OAM entity from sending an OAM packet to the sink PE. ;
  • a first label switching path Internet packet explorer LSP ping request message carrying the source OAM entity configuration information, so that the sink PE configures the information according to the source OAM entity configuration information.
  • the sinking OAM entity of the sinking PE starts the packet receiving function of the sinking OAM entity, and the first LSP ping request message further includes a VPN identifier of the Layer 3 virtual private network L3 VPN, where the VPN identifier is used to identify The sink PE device needs a VPN for OAM detection;
  • the sinking end PE Receiving a first LSP ping response message sent by the sinking end PE, where the first LSP ping response message carries the configuration information of the sink OAM entity, and determining the configuration information of the sink OAM entity and the source OAM entity When the configuration information is matched, the function of the OAM entity sent by the source OAM entity to the sink PE is enabled.
  • the method further includes: when determining the sink OAM entity configuration information and the source OAM entity configuration If the information is not matched, the source OAM entity configuration information is matched with the configuration of the sink OAM entity, and the function of the source OAM entity to send the OAM packet to the sink PE is enabled.
  • the second possible implementation manner of the first aspect is further provided, where the first LSP ping request message is virtual private
  • the network OAM forwarding equivalence class stack type, length, and content VPN OAM FEC TLV carries the VPN identifier, and the VPN OAM FEC TLV includes: a target global ID, a target global ID, a target node ID, a target node ID, and a target route identifier, Target Route Distinguishes.
  • the VPN OAM FEC TLV further includes:
  • the target interface ID is used to identify an interface that the sink PE needs to perform OAM detection.
  • the destination IP address is used to identify the sink end PE to perform OAM detection.
  • the fourth possible implementation manner of the first aspect is further provided, where the first LSP ping request message is Also includes the OAM Management Type, Length, and Content OAM Administration TLV, which includes:
  • the alarm enable flag is used to identify whether the OAM alarm reporting function is enabled.
  • the two-way detection flag is used to identify whether the two-way OAM detection function between the source PE and the sink PE is established.
  • the fifth possible implementation manner of the first aspect is further provided, where the method further includes:
  • the method Before sending the first LSP ping request message to the sink PE, the method includes: configuring, by the source PE, a function of receiving a source OAM entity, and setting a bidirectional detection flag of the 0 An enable state, so that the sink PE configures a function of sending the OAM entity of the sink OAM entity, and starts a function of the sink entity to send an OAM message to the source end;
  • the first L SP ping request message further includes a VPN 0 AM source identifier type, a length, and a content VPN OAM Source Identifier TLV, where the VPN OAM Source Identifier TLV is used to identify the VPN label that the source PE needs to perform OAM detection.
  • the VPN OAM Source Identifier TLV includes: a source global ID source global ID, a source node ID source node ID, and a source routing identifier Source Route Distinguisher.
  • the sixth possible implementation manner of the first aspect is further provided, where the VPN 0 AM Source Identifier TLV further includes:
  • the source interface ID source IF ID is used to identify the interface that the source PE needs to perform OAM detection.
  • the source IP address is used to identify that the source PE needs to perform OAM detection.
  • a seventh possible implementation manner of the first aspect is further provided, in the first LSP Ping request message
  • the alarm enable flag in the included OAM Administration TLV is in a forbidden state, so that the sinking PE suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity, where the enabling After the source OAM entity sends the OAM packet to the sink PE, the method includes:
  • the end PE After receiving the second LSP ping request message, the end PE enables the alarm reporting function of the sink OAM entity.
  • the eighth possible implementation manner of the first aspect is further provided, where the method further includes:
  • the alarm reporting function of the source OAM entity is enabled when the alarm enable flag of the OAM Administration TLV is enabled in the second LSP ping response message.
  • a method for configuring an OAM includes: receiving, by a sink operator, an edge router, a first label switching path, an Internet packet explorer LSP, that carries source-origin 0 MME configuration information sent by a source PE. Ping request message; the first LSP ping request message further includes a VPN of a three-layer virtual private network L3VPN Identification
  • the first LSP ping request message further includes an 0 AM management type, a length, and a content 0 AM Administration TLV, where the OAM Administration TLV includes:
  • the alarm enable flag is used to identify whether the OAM alarm reporting function is enabled.
  • the two-way detection flag is used to identify whether the two-way OAM detection function between the source PE and the sink PE is established.
  • the sink PE configures the ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ function of the sink OAM entity, and starts the sink OAM entity to send the OAM to the source PE ⁇ The function of the text.
  • the second possible implementation manner of the second aspect is further provided, when the first LSP is received When the alarm enable flag in the OAM Administration TLV in the ping request message is in the forbidden state, the sink PE suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity, and the method further includes :
  • a third possible implementation manner of the second aspect is further provided, that: sending, by the source PE, a second LSP ping response message, where The second LSP ping response message includes an OAM Administration TLV, and when the two-way detection flag in the OAM Administration TLV included in the first LSP ping request message is enabled, the second LSP Ping response message is in the OAM Administration TLV.
  • the alarm enable flag is enabled, so that the source PE can enable the alarm reporting function of the source OAM entity after receiving the second LSP ping response message.
  • a source PE configured to: An OAM entity unit, configured to configure a source OAM entity, and prohibit the source OAM entity from sending an OAM packet to the sink PE;
  • a generating unit configured to generate a first LSP ping request message according to the source OAM entity configured by the OAM entity unit, where the first LSP ping request message carries the source OAM entity configuration information, the first LSP ping request
  • the message further includes a VPN identifier of the Layer 3 virtual private network L3VPN, where the VPN identifier is used to identify the VPN that the sink PE device needs to perform OAM detection;
  • a sending unit configured to send the first LSP ping request message generated by the generating unit to a sinking PE, so that the sinking PE configures a sink OAM entity according to the first LSP ping request message, and starts Packet receiving work of the OAM entity
  • a receiving unit configured to receive a first LSP ping response message sent by the sinking PE, where the first LSP ping response message carries the sink OAM entity configuration information of the sink PE;
  • the OAM entity unit is further configured to: when it is determined that the configuration information of the sink OAM entity matches the configuration information of the source OAM entity, enable the source OAM entity to send an OAM ⁇ message to the sink PE.
  • the OAM entity unit is further configured to: when determining that the sink OAM entity configuration information does not match the source OAM entity configuration information, The source OAM entity configuration information is matched with the sink OAM entity configuration information, and the function of the source OAM entity to send the OAM packet to the sink PE is enabled.
  • the first LSP generated by the generating unit also includes:
  • OAM Administration TLV used to identify the VPN identifier;
  • the 0 AM Admini stration TLV includes:
  • the alarm enable flag is used to identify whether the OAM alarm reporting function is enabled.
  • the two-way detection flag is used to identify whether the two-way OAM detection function between the source PE and the sink PE is established.
  • the OAM entity unit is further configured to configure an OAM report of the source OAM entity. Receiving a function, and setting the bidirectional detection flag of the 0 Administration TLV to an enabled state, so that the sink PE configures an OAM packet sending function of the sink OAM entity, and starts the sink end The OAM entity sends the OAM packet to the source PE.
  • the third possible implementation manner of the foregoing third aspect is further provided, where the 0 in the first LSP Ping request message generated by the generating unit is The alarm enable flag in the AM Administration TLV is in a forbidden state, so that the sinking PE suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity;
  • the generating unit is further configured to generate a second LSP Ping request message, where the second LSP Ping The alarm enable flag in the OAM Administration TLV included in the request message is enabled.
  • the sending unit is further configured to send the second LSP ping request message generated by the generating unit to the sink PE, so that the sink PE after receiving the second LSP ping request message
  • the alarm reporting function of the sink OAM entity is enabled.
  • the fourth possible implementation manner of the foregoing third aspect is further provided, where the receiving unit is further configured to receive the sending by the sink PE a second LSP Ping response message;
  • the OAM entity unit is further configured to: when the alarm enable flag of the OAM Administration TLV included in the second LSP ping response message received by the receiving unit is enabled, enable the source OAM entity Alarm reporting function.
  • a sink PE is provided, and the method includes:
  • a receiving unit configured to receive a first label switching path Internet packet explorer LSP ping request message that is sent by the source PE and carries the source OAM entity configuration information; the first LSP ping request message includes a VPN of a three-layer virtual private network L3VPN Identification
  • An OAM entity unit configured to configure a sink OAM entity according to the first LSP ping request message received by the receiving unit, and configure the sink OAM entity to detect a VPN corresponding to the VPN identifier, and start the The receiving function of the sink OAM entity;
  • a generating unit configured to generate a first LSP Ping response message according to the sink OAM entity configured by the OAM entity unit, where the first LSP Ping response message carries the Slot OAM entity configuration information;
  • a sending unit configured to send the first LSP Ping response message generated by the generating unit to the source PE.
  • the first LSP ping request message received by the receiving unit further includes an OAM management type, a length, and a content OAM Administration TLV, where the OAM Administration TLV includes :
  • the alarm enable flag is used to identify whether the 0AM alarm reporting function is enabled.
  • the two-way detection flag is used to identify whether the two-way OAM detection function between the source PE and the sink PE is established.
  • the OAM entity unit is further configured to: when the bidirectional detection flag in the OAM Administration TLV is set to an enabled state, configure an OAM file sending function of the sink OAM entity, and start the sink OAM The function of sending an OAM packet to the source PE.
  • a second possible implementation manner of the fourth aspect is further provided, when the receiving unit receives the 0 AM When the alarm enable flag in the Administration TLV is in the forbidden state, the OAM entity unit, after configuring the sink OAM entity, suppresses the alarm reporting function of the sink OAM entity;
  • the receiving unit is further configured to receive the second LSP ping request message, where the second LSP ping request message includes the OAM Administration TLV, and the alarm enable flag in the 0 AM Administration TLV is enabled. State
  • the OAM entity unit is further configured to enable the alarm reporting function of the sink OAM entity according to the second LSP ping request message received by the receiving unit.
  • a third possible implementation manner of the foregoing third aspect is further provided, where the generating unit is further configured to generate a second LSP Ping response message, where The two-way detection, the alarm enable flag of the OAM Administration TLV included in the second L SP Ping response message is an enabled state, and the sending unit is further configured to send the generated to the source PE
  • the second LSP ping response message generated by the unit is configured to enable the source end PE to enable the alarm reporting function of the source OAM entity after receiving the second LSP ping response message.
  • the fifth aspect provides an OAM configuration system, where the system includes: the third aspect or any one of the possible implementation manners provided by the third aspect The source PE provided in the middle;
  • the fourth aspect or the sink PE provided in any one of the possible implementation manners provided by the fourth aspect.
  • the embodiment of the present invention provides a method, a device, and a system for configuring an OAM.
  • the OAM configuration information of the source PE is sent to the sink PE device by using the extended LSP ping request message.
  • the function of the sinking end PE to configure the sink OAM entity of the sink PE according to the source OAM configuration information, and the function of the OAM entity to send the OAM packet to the source PE;
  • the request message includes the VPN identifier that the sink PE needs to perform OAM detection.
  • the source OAM entity is enabled to send the OAM to the sink PE.
  • the function of the spoofing text, thereby completing the OAM configuration of the source PE and the sink PE, the source OAM entity and the sink OAM entity can enable the corresponding alarm reporting function, and the implementation manner reduces the configuration of the two ends.
  • the OAM configuration workload is implemented by the two ends through the interactive LSP ping message to dynamically complete the OAM configuration, which avoids errors in manual configuration.
  • FIG. 1 is a schematic diagram of an OAM configuration process between PE devices in a VPN network according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of an OA configuration method according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of an OAM Function TLV according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a VPNv4 OAM FEC Stack TLV format according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a VPNv6 OAM FEC Stack TLV format according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of an OAM Administration TLV format according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a format of a VPNv4 OAM Source Identifier TLV according to an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram of a format of a VPNv6 OAM Source Identifier TLV according to an embodiment of the present disclosure
  • FIG. 9 is an OAM Administration TLV carrying an alarm enable bit according to an embodiment of the present invention.
  • FIG. 10 is a schematic flow chart of another OAM configuration method according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of a system for configuring an OAM according to an embodiment of the present invention
  • FIG. 12 is a schematic diagram of another system for configuring an OAM according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of OAM configuration process between PEs in a VPN network.
  • PE1 10 indicates the source carrier edge router PE and PE2 11 indicates the sink operator edge router PE.
  • PE2 11 issues a label to PE1 10; PE1 10 uses these labels for encapsulation and forwards the data stream to PE2 11.
  • the direction in which the OAM performs the detection is the same as the direction in which the data stream is forwarded.
  • PE1 10 acts as the active end—that is, the source end initiates the label switching path Internet packet explorer (English name is Label Switched Path Packet Internet Grope, LSP for short), and the PE2 11 acts as the passive end—that is, The sink responds to the LSP Ping response message.
  • the label switching path Internet packet explorer English name is Label Switched Path Packet Internet Grope, LSP for short
  • LSP Label Switched Path Packet Internet Grope
  • the foregoing process is a one-way process. If the two ends of the PE1 10 and the PE 2 are mutually forwarded to form a bidirectional forwarding, the OAM is performed in both directions, and the PE at either end can serve as the source end, that is, the PE1 10 is the source PE. It is also a sink PE, and PE2 11 is a sink. The end PE is also the source PE.
  • an embodiment of the present invention provides a method for OAM configuration, which includes the following content.
  • the source PE configures the source OAM entity, and the source OAM entity is prohibited from sending an OAM packet to the sink PE.
  • the OAM detection performed by the VPN in the L3 VPN network is taken as an example for description.
  • One end of the LSP ping request request (LSP Ping Echo Request) is the source PE; the LSP Ping Echo Reply is received passively, and one end of the LSP Ping response message is the sink PE.
  • the source OAM entity As the source PE that initiates the LSP ping request message, you need to configure the source OAM sending function when configuring the source OAM entity. To prevent the source OAM entity and the sink OAM entity from being negotiated and configured, the source OAM entity sends the source OAM entity. The OAM entity and the sink OAM entity are unsuccessful. Therefore, the source OAM entity and the sink OAM entity are prohibited from being configured to the sink PE after the negotiation is configured. Send OAM packets.
  • the source PE when the source PE and the same VPN to which the sink PE belongs are to perform OAM detection, and the source PE and the sink PE do not perform the corresponding OAM entity configuration, the source PE needs to be the source.
  • 0 AM entity is configured.
  • the source 0 AM entity may be configured as follows: continuity detection, connectivity detection, error management signal detection, packet loss detection, delay detection, traffic detection, and the like.
  • the sinking PE sends, to the sinking PE, a first LSP ping request message that carries the configuration information of the source OAM entity, so that the sink PE configures the sink of the sink PE according to the source OAM entity configuration information.
  • the end OAM entity starts the packet receiving function of the sink OAM entity, and the first LSP ping request message further includes a VPN identifier of the L3VPN, where the VPN identifier is used to identify that the sink PE device needs to perform OAM detection.
  • VPN VPN.
  • the sink PE may configure the configuration information of the sink OAM entity according to the source OAM entity configuration information. For example, when the source OAM entity configuration information includes packet loss detection, the sink PE configures the sink. The OAM entity is configured to perform packet loss detection. However, when the sink PE configures the OAM packet loss detection parameter, the sink PE may be different from the source OAM entity configuration information.
  • the source OAM entity configuration information may be carried by an OAM function type, a length, and a content TLV.
  • OAM Function TLV refer to [draft-ietf-mpls-lsp-ping-mpls-tp- Oam-conf-03], ⁇ mouth shown in Figure 3:
  • the C flag is used to identify continuity detection (English full name Continuity Check, English abbreviated as CC);
  • the V flag is used to identify connectivity detection (English full name is Connectivity Verification, English abbreviated as CV);
  • the F flag is used to identify the error management signal detection (English name is Fault Management Signals, English abbreviated as FMS);
  • the L flag is used to identify the packet loss detection ( Loss );
  • the D flag is used to identify the delay detection (Delay);
  • the T flag is used to identify traffic detection (English full name is Throughput Measurement, English abbreviated as ⁇ ).
  • the first LSP ping request message further includes a virtual private network OAM forwarding equivalent class stack type, length, content (VPN OAM FEC Stack TLV), the first identifier.
  • the VPN OAM FEC TLV includes: a target global ID (Target Global ID), a target node ID (Target Node ID), and a target route identifier (Target Route Distinguisher), and FIG. 4 shows that the VPN OAM FEC Stack TLV carries an IPv4 VPN.
  • Figure 4 is a schematic diagram of the format of the packet when the IPv6 VPN identifier is carried in the VPN OAM FEC Stack TLV.
  • the VPN can be identified by:
  • the VPN OAM FEC Stack TLV may further include: a target interface ID (Target IF ID), which is used to identify an interface that the sink PE needs to perform OAM detection; for FIG. 4, the VPN OAM FEC Stack The TLV further includes a target IPv4 prefix (Target IPv4 prefix) and a prefix length (Prefix Length), which are used to identify an IPv4 VPN route that the sink PE needs to perform OAM detection.
  • a target interface ID (Target IF ID)
  • Prefix Length prefix length
  • the VPN OAM FEC Stack TLV further includes
  • the target IPv6 prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) are used to identify that the sink PE needs to perform OAM to detect an IPv6 VPN route.
  • Target IPv6 prefix The above settings of Target Global lD , Target Node lD and Target IF NUM follow the definition of [RFC6370], and the setting of Target Route Distinguisher follows the definition of [RFC4364].
  • the format of the VPN OAM FEC Stack TLV may be: the first 1-4 bytes may indicate the Target Global ID, and the 5th-8th byte may indicate the Target Node ID, the 9th 16 bytes can indicate Target Route Distinguisher, the 17th-20th byte can indicate the Target IF ID, the 21st-24th byte can indicate the Target IPv4prefix and the Target IPv6 prefix, and the 25th byte can indicate the refix length, the 26th-28th word
  • the section can be 0.
  • the first LSP ping response message is sent to the source PE.
  • the configuration information of the sink OAM entity may not match the configuration information of the source OAM entity due to the capability of the sink PE.
  • the sink PE when determining that the sink OAM entity configuration information does not match the source OAM entity configuration information, adjusting the source OAM entity configuration information to match the sink OAM entity configuration information, and then, The function of the OAM packet sent by the source OAM entity to the sink PE.
  • the packet loss detection is taken as an example. Referring to FIG. 3, if the L flag of the packet loss detection is located, and the specific packet loss detection mode in the configuration information of the source OAM entity is a direct detection mode (Direct ), that is, the service text is directly tested.
  • the sink PE After receiving the configuration information of the OAM entity, the sink PE determines that the sink PE supports only the in-line detection mode (Inferred), and the sink PE can only configure the sink OAM.
  • Direct direct detection mode
  • the configuration parameter is an Inferrer detection mode
  • the sink PE sends the OAM configuration information that is supported by the sink PE to the source PE through the first LSP Ping response message, when the source PE receives the After the first LSP ping response message is sent, the OAM configuration information of the sinking PE is not matched with the configuration information of the source OAM entity, and the packet loss detection mode in the configuration information of the source OAM is adjusted to the Inferred mode.
  • the sending, by the source PE, the first L SP ping request message to the sink PE further includes: an OAM management type, an OAM Administration TLV, and the OAM Administration TLV.
  • the intermediate provider router P is enabled with the OAM detection flag I, which is used to identify whether the intermediate P device OAM detection is enabled.
  • the alarm enable flag A is used to identify whether the OAM alarm reporting function is enabled.
  • the two-way detection flag D is used to identify whether the two-way 0 AM detection function between the source PE and the sink PE is established.
  • the format of the OAM Administration TLV may be:
  • the first and second bytes of the OAM Administration TLV may indicate the type of the OAM Administration TLV, and the third and fourth bytes of the OAM Administration TLV may indicate OAM Administration.
  • the length of the TLV, the 5th to 8th bytes of the OAM Administration TLV can indicate the configuration information of the OAM detection.
  • the first bit of the 5th byte of the OAM Administration TLV (I flag in FIG. 6) indicates that the intermediate provider router P enables the OAM detection flag to identify whether the intermediate P device OAM detection is enabled, if the bit is set. Indicates that the first LSP ping request message is required to create an OAM Maintenance Entity Group Intermediate Point (MIP) entity along the transit node.
  • the second bit of the fifth byte of the OAM Administration TLV (the A flag in FIG. 6) is used to identify whether the OAM alarm reporting function is enabled. When the bit is set, the device that receives the first LSP ping request message is configured. After the OAM entity is complete, the alarm reporting function is enabled.
  • the OAM detects the fault
  • the related triggering action is generated, including the alarm.
  • the bit is reset, the alarm is suppressed and the subsequent actions are not triggered.
  • the D flag in the 3rd bit of the 5th byte of the OAM Administration TLV (Fig. 6) is used to identify whether to establish a bidirectional OAM detection function between the source PE and the sink PE, the bit is set, indicating that Do two-way detection.
  • the remaining 5th byte and the 6th, 7th, and 8th bytes are reserved, which is convenient for future OAM configuration enable extension.
  • the source PE before the source PE sends the first LSP ping request message to the sink PE, the source PE further configures an OAM packet receiving function of the source OAM entity, and sets The bidirectional detection flag of the 0 AM Administration TLV in the first LSP ping request message is set, that is, the bidirectional detection flag is set to an enabled state, so that the sink PE further configures the sink OAM entity.
  • the OAM file sending function is configured to start the function of sending the OAM message to the source PE by the sink OAM entity.
  • the first LSP ping request message further includes: a VPN OAM source identifier type, a length, and a content (VPN OAM Source Identifier TLV), where the VPN OAM Source Identifier TLV is used to identify the source end
  • Figure 5 is a schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv4 VPN identifier
  • Figure 8 is a schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv6 VPN identifier.
  • the VPN OAM Source Identifier TLV includes:
  • VPN OAM Source Identifier TLV type VPN OAM Source
  • the source PE needs to perform OAM detection. It can be identified by:
  • the VPN OAM Source Identifier TLV may further include: a source IF ID, which is used to identify that the source PE needs to perform OAM.
  • a source IF ID which is used to identify that the source PE needs to perform OAM.
  • the source IPv4 prefix and the prefix length (Prefix Length) are further included to identify the IPv4 VPN route that the source PE needs to perform OAM detection;
  • the VPN OAM FEC Stack TLV further includes a source IPv6 prefix (Source IPv6 prefix) and a prefix length (Prefix Length), and is used to identify that the sink PE needs to perform OAM to detect an IPv6 VPN route.
  • the format of the VPN OAM Source Identifier TLV may be:
  • the 1-2th byte may indicate the type of the VPN OAM Source Identifier TLV
  • the 3-4th byte may indicate the VPN OAM Source Identifier.
  • the length of the TLV, the 5th-8th byte can indicate the Source Global ID, the 9th to 16th bytes can indicate the Source Node ID, the 17th to 20th bytes can indicate the Source IF ID, and the 21st to 24th bytes can indicate the Source IPv4 (in Figure 7) / IPv6 prefix (in Figure 8), the 25th byte can indicate the prefix length, and the 26th-28th byte can be 0.
  • the source OAM entity and the sink OAM entity are not completed in the process of configuring the source OAM entity and the sink OAM entity.
  • the configuration of the source OAM entity and the sink OAM entity does not match, causing the sink OAM entity to report an error alarm, further triggering the sink PE or the source PE to perform an error operation according to the error alarm.
  • the alarm enable flag of the OAM Administration TLV in the first LSP ping request message may be in a forbidden state, so that the sink PE suppresses the sink OAM entity after configuring the sink OAM entity.
  • the second LSP ping request message includes an OAM Administration TLV
  • the alarm enable flag in the OAM Administration TLV included in the second LSP ping request message is enabled.
  • the OAM Administration TLV carried in the second LSP ping request message includes a bit 1 for identifying an alarm enablement (may be any, as long as the enable alarm can be identified), and the remaining two-way
  • the detection flag D and the intermediate provider router P enable the OAM detection flag I can be empty, and the sink PE enables the alarm reporting function of the sink OAM entity after receiving the second LSP ping request message.
  • the source end PE receives a second LSP ping response message sent by the sink PE, where the second LSP ping response message is a response message to the second LSP ping request message, where the sink end
  • the PE may start sending an OAM detection message to the sink PE, where the source PE and the sink PE start to ping the request message for the first LSP.
  • the VPN corresponding to the VPN ID is used for OAM detection.
  • the alarm reporting function of the source OAM entity is enabled when the alarm enable flag of the OAM Administration TLV is enabled in the second LSP ping response message.
  • the sink PE configures the sink end to send the function, that is, after the configuration of the sink OAM entity, that is, And starting the detection function of the sink end to the source end direction, and setting an alarm enable flag of the 0 AM Administration TLV included in the second LSP Ping response message to an enable state, when the source The alarm reporting function of the source OAM entity is enabled when the alarm enable flag of the OAM Administration TLV is enabled in the second LSP ping response message.
  • the source PE and the sink PE send the LSP ping request message and the LSP ping response message carrying the relevant information.
  • the negotiation process between the source PE and the sink PE, and the related parameters are exchanged for parameter update and session deletion.
  • the embodiment of the present invention provides a method for configuring an OAM.
  • the OAM configuration information of the source PE is sent to the sink PE device by using the extended LSP ping request message, so that the The sink PE configures the sink OAM entity of the sink PE according to the source OAM configuration information, and starts the sink OAM entity to send an OAM packet to the source PE;
  • the LSP Ping request message includes the The sinking PE needs to perform the OAM detection of the VPN identifier.
  • the source OAM entity is enabled to send the OAM function to the sink PE.
  • the source OAM entity and the sink OAM entity can be configured with the corresponding alarm reporting function. Because the two ends dynamically complete the OAM configuration by using the interactive LSP ping message, the errors in the manual configuration are avoided.
  • an embodiment of the present invention provides another method for OAM configuration, which includes the following content.
  • the sinker operator edge router PE receives the first label switching path Internet packet explorer LSP ping request message that is sent by the source PE and carries the source OAM entity configuration information.
  • the first LSP ping request message further includes three layers of virtual VPN ID of the private network L3VPN.
  • the source OAM entity configuration information may be carried by an OAM Function TLV, which has been described in FIG. 3, and details are not described herein again.
  • the first LSP ping request message further includes a virtual private network VPN OAM FEC Stack TLV, where the first LSP ping request message passes the VPN
  • the OAM FEC Stack TLV carries the VPN identifier.
  • the VPN OAM FEC TLV includes: a target global ID (Target Global ID), a target node ID (Target Node ID), and a target route identifier (Target Route Distinguisher), and FIG. 4 shows that the VPN OAM FEC Stack TLV carries an IPv4 VPN.
  • Figure 5 is a schematic diagram of a packet format when the IPv6 VPN identifier is carried in the VPN OAM FEC Stack TLV.
  • the VPN can be identified by:
  • Target Global ID : Target Node ID: : Target Route Distinguisher.
  • the VPN OAM FEC Stack TLV may further include: a target interface ID (Target IF ID), configured to identify an interface that the sink PE needs to perform OAM detection; for FIG. 4, the VPN OAM FEC Stack The TLV also includes a target IPv4 prefix (Target IPv4 prefix) and a prefix length (Prefix Length), which is used to identify an IPv4 VPN route that the sink PE needs to perform OAM detection.
  • the VPN OAM FEC Stack TLV further includes The target IPv6 prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) are used to identify that the sink PE needs to perform OAM to detect an IPv6 VPN route.
  • Target Global lD Target Node lD and Target IF NUM follow the definition of [RFC6370]
  • Target Route Distinguisher follows the definition of [RFC4364].
  • the first LSP ping request message further includes:
  • the VPN OAM Source Identifier TLV is used to identify the VPN identifier that the source PE needs to perform the OAM detection.
  • FIG. 7 is a schematic diagram of the packet format when the VPN OAM Source Identifier TLV carries the IPv4 VPN identifier.
  • FIG. 8 is a schematic diagram of a format of a message when the VPN OAM Source Identifier TLV carries an IPv6 VPN identifier.
  • the VPN OAM Source Identifier TLV may further include: a source IF ID, which is used to identify an interface that the source PE needs to perform OAM detection.
  • the method further includes The source IPv4 prefix and the prefix length (Prefix Length) are used to identify the IPv4 VPN route that the source PE needs to perform OAM detection.
  • the VPN OAM FEC Stack TLV further includes the source IPv6.
  • the source IPv6 prefix and the prefix length (prefix length) are used to identify that the sink PE needs to perform OAM to detect an IPv6 VPN route.
  • the first LSP ping request message further includes an OAM Administration TLV
  • FIG. 6 is a schematic diagram of the OAM Administration TLV format, which has been described, and is not described herein again.
  • the sink PE configures the ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ function of the sink OAM entity, and starts the sink OAM entity to send the OAM to the source PE ⁇ The function of the text.
  • the sink PE suppresses the The sinking OAM entity alarms the function, and the method further includes:
  • the bidirectional detection flag in the OAM Administration TLV that is further included in the first LSP ping request message is in an enabled state
  • sending a second LSP ping response message to the source PE the second LSP
  • the ping response message includes an OAM Administration TLV
  • the alarm enable flag of the OAM Administration TLV in the second LSP ping response message is enabled, so that after the source PE receives the second LSP ping response message, Enable the alarm reporting function of the source OAM entity.
  • the embodiment of the present invention provides a method for configuring an OAM.
  • the OAM configuration information of the source PE is sent to the sink PE device by using the extended LSP ping request message, so that the The sink PE configures the sink OAM entity of the sink PE according to the source OAM configuration information, and starts the sink OAM entity to send an OAM packet to the source PE;
  • the LSP Ping request message includes the The sinking PE needs to perform the OAM detection of the VPN identifier.
  • the source OAM entity is enabled to send the OAM function to the sink PE. As a result, the OAM configuration of the source PE and the sink PE is completed.
  • an embodiment of the present invention provides a system for configuring an OAM, where the system includes: a source end PE 10 and a sink end PE 20.
  • the source PE10 includes:
  • the OAM entity unit 101 is configured to configure a source OAM entity, and the source OAM entity is prohibited from sending an OAM packet to the sink PE20.
  • the generating unit 102 is configured to generate, according to the source OAM entity configured by the OAM entity unit 101, a first LSP ping request message, where the first LSP ping request message carries the source MME entity configuration information, where the first The L SP Ping request message further includes a VPN identifier of the L3VPN, where the VPN identifier is used to identify a VPN that the sink PE device needs to perform OAM detection.
  • the sending unit 103 is configured to send the first LSP ping request message generated by the generating unit 102 to the sink PE20.
  • the receiving unit 104 is configured to receive a first LSP ping response message sent by the sink PE20, where the first LSP ping response message carries the sink OAM entity configuration information.
  • the OAM entity unit 101 is further configured to: according to the configuration information of the sink OAM entity carried in the first LSP ping response message received by the receiving unit 104, when determining the configuration information and location of the OAM entity of the sink end When the source OAM entity configuration information is matched, the function of the OAM packet sent by the source OAM entity to the sink PE20 is enabled.
  • the sink PE 20 includes:
  • the receiving unit 201 is configured to receive a first LSP ping request message that is sent by the sending unit 103 of the source PE 10 and that carries the source OAM entity configuration information, where the first LSP ping request message includes a VPN identifier of the Layer 3 virtual private network L3VPN.
  • the OAM entity unit 202 is configured to configure a sink OAM entity according to the first LSP ping request message received by the receiving unit 201, and start a packet receiving function of the sink OAM entity.
  • the generating unit 203 is configured to generate a first LSP ping response message according to the configuration information of the sink OAM entity configured by the OAM entity unit 202, where the first LSP ping response message carries the sink OAM entity configuration information.
  • the sending unit 204 is configured to ping the first LSP generated by the generating unit 203.
  • the response message is sent to the source PE 10.
  • the OAM entity unit 101 of the source PE 10 is further configured to: when determining that the configuration information of the sink OAM entity does not match the configuration information of the source OAM entity, adjust the configuration information of the source OAM entity. Matching with the configuration information of the sink OAM entity, the function of the OAM packet sent by the source OAM entity to the sink PE20 is enabled.
  • the source OAM entity configuration information may be carried by an OAM Function TLV, and the OAM Function TLV format is as shown in FIG. 3.
  • the first LSP ping request message generated by the generating unit 102 of the source PE10 further includes a VPN OAM FEC Stack TLV, where the first LSP ping request message is carried by the VPN OAM FEC Stack TLV.
  • VPN ID The VPN OAM FEC TLV includes: a target global ID (Target Global ID), a target node ID (Target Node ID), and a target route identifier (Target Route Distinguisher), and FIG. 4 shows that the VPN OAM FEC Stack TLV carries an IPv4 VPN.
  • Figure 4 is a schematic diagram of the format of the packet when the IPv6 VPN identifier is carried in the VPN OAM FEC Stack TLV.
  • the VPN can be identified by:
  • Target Global ID : Target Node ID: : Target Route Distinguisher.
  • the VPN OAM FEC Stack TLV may further include: a target interface ID (Target IF ID), configured to identify an interface that the sink PE 20 needs to perform OAM detection; for FIG. 4, the VPN OAM FEC Stack The TLV further includes a target IPv4 prefix (Target IPv4 prefix) and a prefix length (Prefix Length), which are used to identify the IPv4 VPN route that the sink PE20 needs to perform OAM detection.
  • the VPN OAM FEC Stack TLV further includes The target IPv6 prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) are used to identify that the sink PE 20 needs to perform OAM to detect an IPv6 VPN route.
  • the first LSP ping request message generated by the generating unit 102 of the source PE10 further includes:
  • the Administration TLV includes: The alarm enable flag is used to identify whether the OAM alarm reporting function is enabled.
  • the two-way detection flag is used to identify whether the two-way OAM detection function between the source PE and the sink PE is established.
  • the OAM entity unit 101 of the source PE 10 is further configured to configure the OAM of the source OAM entity.
  • Receiving a function, and setting the bidirectional detection flag of the OAM Administration TLV to an enabled state so that the sink PE20 configures an OAM function of the sink OAM entity, and starts the sink end
  • the OAM entity sends the function of the OAM ⁇ message to the source PE.
  • the OAM entity unit 202 of the sink PE20 is further configured to: when the bidirectional detection flag in the OAM Administration TLV is set to an enabled state, configure the OAM packet sending of the sink OAM entity. And functioning, and starting the function of sending the OAM ⁇ message to the source PE10 by the sinker OAM entity.
  • the first LSP ping request message further includes: a VPN OAM Source Identifier TLV, where the VPN OAM Source Identifier TLV is used to identify the VPN identifier that the source PE 10 needs to perform OAM detection, and
  • Figure 7 A schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv4 VPN identifier
  • FIG. 8 is a schematic diagram of a format of the IPv4 VPN identifier when the VPN OAM Source Identifier TLV carries an IPv6 VPN identifier.
  • the VPN OAM Source Identifier TLV may further include: a source IF ID, which is used to identify an interface that the source PE 10 needs to perform OAM detection.
  • the method further includes The source IPv4 prefix and the prefix length (Prefix Length) are used to identify the IPv4 VPN route that the source PE 10 needs to perform the 0 AM detection.
  • the VPN OAM FEC Stack TLV further includes the source IPv6.
  • the source IPv6 prefix and the prefix length (prefix length) are used to identify that the sink PE10 needs to perform OAM to detect an IPv6 VPN route.
  • the first LSP ping request message further includes an OAM Administration TLV
  • FIG. 6 is a schematic diagram of the format of the OAM Administration TLV, which has been described, and details are not described herein again.
  • the alarm enable flag in the OAM Administration TLV in the first LSP ping request message generated by the generating unit 102 of the source PE 10 is prohibited.
  • the generating unit 102 of the source PE 10 is further configured to generate the second The LSP ping request message, the alarm enable flag in the 0 AM Administration TLV included in the second LSP ping request message is an enabled state.
  • the receiving unit 201 is further configured to receive the second LSP ping request message, where the OAM entity unit 202 of the sink PE20 is further configured to receive the second L SP according to the receiving unit 201.
  • the ping request message enables the alarm reporting function of the sink 0 AM entity.
  • the sending unit 103 of the source PE 10 is further configured to send the second LSP ping request message generated by the generating unit 102 to the sink PE20, and correspondingly, the receiving unit 201 of the sink PE20 further uses Upon receiving the second LSP ping request message, the OAM entity unit 202 of the sink PE 20 is further configured to: when determining that the receiving unit 201 is further configured to receive the OAM Administration TLV included in the second LSP ping request message When the alarm enable flag is enabled, the alarm reporting function of the sink OAM entity is enabled.
  • the receiving unit 104 of the source PE 10 is further configured to receive a second LSP ping response message sent by the sink PE20.
  • the generating unit 203 of the sink PE20 is further configured to generate a second LSP ping response message, where the alarm enable flag of the 0 AM Administration TLV included in the second LSP ping response message is Enable status.
  • the sending unit 204 of the sink PE20 is further configured to send the second LSP ping response message generated by the generating unit 203 to the source end PE10.
  • the OAM entity unit 101 of the source PE 10 is further configured to: when the alarm enable flag of the OAM Administration TLV included in the second LSP ping response message received by the receiving unit 104 is enabled, the enabling station The alarm reporting function of the source OAM entity.
  • the embodiment of the invention provides a system for configuring OAM, and the source end of the PE10 is configured.
  • the OAM configuration information of the source PE 10 is sent to the sink PE20 by using the extended LSP ping request message, so that the sink PE 20 configures the sink OAM of the sink PE 20 according to the source OAM configuration information.
  • An entity, and the sinking OAM entity is configured to send an OAM packet to the source PE 10;
  • the LSP ping request message includes a VPN identifier that the sink PE 20 needs to perform OAM detection, when the source PE 10 and the sink
  • the OAM function is enabled to send the OAM packet to the sink PE20.
  • the OAM configuration of the source PE 10 and the sink PE 20 is completed.
  • the entity and the sink OAM entity can be configured with the corresponding alarm reporting function.
  • the implementation of the OAM configuration is implemented on the two ends. The two ends perform dynamic OAM configuration through the LSP ping message. An error has occurred.
  • an embodiment of the present invention provides another OAM configuration system, where the system includes: a source PE30 and a sink PE40.
  • the source PE 30 includes:
  • the processor 301 is configured to configure the source OAM entity, and the source OAM entity is prohibited from sending the OAM ⁇ message to the sink PE30, and is also used to generate a first LSP ping request message, the first LSP ping request
  • the message carries the source OAM entity configuration information, and the first L SP ping request message further includes a VPN identifier of the L3 VPN, where the VPN identifier is used to identify the VPN that the sink PE 40 needs to perform OAM detection.
  • the sender 302 is configured to send the first LSP ping request message generated by the processor 301 to the sink PE40.
  • the receiver 303 is configured to receive a first LSP Ping response message sent by the sink PE 40, where the first L SP Ping response message carries the sink 0 AM entity configuration information.
  • the processor 301 is further configured to: according to the configuration information of the sink OAM entity carried in the first LSP ping response message received by the receiver 303, when determining the configuration information of the sink OAM entity and the source end When the OAM entity configuration information is matched, the function of the OAM packet sent by the source OAM entity to the sink PE 40 is enabled.
  • the sink PE40 includes:
  • the receiver 401 is configured to receive a first LSP ping request message that is sent by the transmitter 302 of the source PE 30 and that carries the source OAM entity configuration information.
  • the first LSP ping request message includes a VPN identifier of the L3 VPN.
  • the processor 402 is configured to configure, according to the first LSP ping request message received by the receiver 401, a sink OAM entity, and enable the receiving function of the sink OAM entity, and generate the first LSP ping.
  • the first LSP Ping response message carries the sink OAM entity configuration information.
  • the transmitter 403 is configured to send the first LSP ping response message generated by the processor 402 to the source PE 30.
  • the processor 301 is further configured to: when determining that the sink OAM entity configuration information does not match the source OAM entity configuration information, adjusting the source OAM entity configuration information and the sink OAM The entity configuration information is matched, and the function of the OAM packet sent by the source OAM entity to the sink PE 40 is enabled.
  • the source OAM entity configuration information may be carried by an OAM Function TLV, and the OAM Function TLV format is as shown in FIG. 3.
  • the first LSP ping request message generated by the processor 301 of the source PE 30 further includes a VPN 0 AM FEC Stack TLV, where the first L SP ping request message is carried by the VPN OAM FEC Stack TLV.
  • the VPN OAM FEC TLV includes: a target global ID (Target Global ID), a target node ID (Target Node ID), and a target route identifier (Target Route Distinguisher), and FIG. 4 shows that the VPN OAM FEC Stack TLV carries an IPv4 VPN.
  • Figure 4 is a schematic diagram of the format of the packet when the IPv6 VPN identifier is carried in the VPN OAM FEC Stack TLV.
  • the VPN can be identified by:
  • Target Global ID : Target Node ID: : Target Route Distinguisher.
  • the VPN OAM FEC Stack TLV may further include: a target interface ID (Target IF ID), configured to identify an interface that the sink PE 40 needs to perform OAM detection; for FIG. 4, the VPN OAM FEC Stack The TLV further includes a target IPv4 prefix (Target IPv4 prefix) and a prefix length (Prefix Length), which are used to identify the IPv4 VPN route that the sink PE20 needs to perform OAM detection.
  • the VPN OAM FEC Stack TLV further includes The target IPv6 prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) are used to identify that the sink PE 20 needs to perform OAM to detect an IPv6 VPN route.
  • the first LSP ping request message generated by the processor 301 of the source PE 30 further includes:
  • the 0 AM Administration TLV used to identify the VPN identifier; the 0 AM Administration TLV includes:
  • the alarm enable flag is used to identify whether the OAM alarm reporting function is enabled.
  • the two-way detection flag is used to identify whether the two-way OAM detection function between the source PE and the sink PE is established.
  • the processor 301 of the source PE 30 is further configured to configure the OAM file receiving function of the source OAM entity. And setting the bidirectional detection flag of the OAM Administration TLV to an enabled state.
  • the processor 402 of the sinker PE40 is further configured to: when the bidirectional detection flag in the OAM Administration TLV is set to an enabled state, configure the sending of the sink OAM entity And functioning, and starting the function of sending the message to the source port 30 by the sink entity.
  • the first LSP ping request message further includes: a VPN OAM Source Identifier TLV, where the VPN OAM Source Identifier TLV is used to identify the VPN identifier that the source PE 30 needs to perform OAM detection, and
  • Figure 7 A schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv4 VPN identifier
  • FIG. 8 is a schematic diagram of a format of the IPv4 VPN identifier when the VPN OAM Source Identifier TLV carries an IPv6 VPN identifier.
  • the VPN OAM Source Identifier TLV may further include: a source IF ID, which is used to identify an interface that the source PE 30 needs to perform OAM detection.
  • the method further includes The source IPv4 prefix and the prefix length (Prefix Length) are used to identify the IPv4 VPN route that the source PE 30 needs to perform the 0 AM detection.
  • the VPN OAM FEC Stack TLV further includes the source IPv6.
  • the source IPv6 prefix and the prefix length (prefix length) are used to identify that the sink PE 30 needs to perform OAM to detect an IPv6 VPN route.
  • the first LSP ping request message further includes an OAM Administration
  • FIG. 6 is a schematic diagram of the OAM Administration TLV format, which has been described and will not be described here.
  • the alarm enable flag in the OAM Administration TLV in the first LSP ping request message generated by the processor 301 of the source PE 30 is in a disabled state, and the OAM Administration received by the receiver 401
  • the processor 402 after configuring the sink OAM entity, suppress the alarm on the sink OAM entity.
  • the processor 301 of the source PE 30 After the processor 301 of the source PE 30 enables the source OAM entity to send an OAM packet to the sink PE 40, the processor 301 is further configured to generate a second LSP ping request message, where The alarm enable flag in the OAM Administration TLV included in the second LSP ping request message is enabled.
  • the receiver 401 of the sinker PE40 is further configured to receive the second LSP ping request message, where the processor 402 is further configured to use the second LSP ping request message received by the receiver 401. Enable the alarm reporting function of the sink OAM entity.
  • the transmitter 302 of the source PE 30 is further configured to send the second LSP ping request message generated by the processor 301 to the sink PE 40, and the receiver 401 is further configured to receive the The second LSP ping request message is used, the processor 402 is further configured to: when determining that the receiver 401 receives the alarm enable flag in the 0 Administration TLV included in the second LSP ping request message to be enabled The alarm reporting function of the sink OAM entity is enabled.
  • the receiver 303 of the source PE 30 is further configured to receive a second LSP ping response message sent by the sink PE 40.
  • the processor 402 of the sinker PE40 is further configured to generate a second LSP ping response message, where, in the two-way detection, the alarm enable flag of the OAM Administration TLV included in the second LSP ping response message is Can state.
  • the transmitter 403 of the sinker PE40 is further configured to send the second LSP ping response message generated by the processor 402 to the source PE 30.
  • the processor 303 of the source PE 30 is further configured to: when the alarm enable flag of the OAM Administration TLV included in the second LSP ping response message received by the receiver 303 is enabled, enable the Alarm reporting function of the source OAM entity.
  • the embodiment of the present invention provides a system for configuring an OAM.
  • the source end OAM entity After the source end OAM entity is configured with the source OAM entity, the source end PE 30 sends the OAM configuration information of the source PE 30 to the sink PE 40 device to make the sink.
  • End PE40 according to the source
  • the OAM configuration information is configured to configure a sink OAM entity of the sink PE 40, and the sink OAM entity is configured to send an OAM packet to the source PE 30.
  • the LSP Ping request message includes the OAM detection of the sink PE 40.
  • the OAM entity After the OAM entity of the source PE 30 and the sink PE 40 is configured, the OAM entity is enabled to send an OAM packet to the sink PE 40, thereby completing the source PE 30.
  • the OAM configuration works with the sinking PE40.
  • the source OAM entity and the sink OAM entity can be configured with the corresponding alarm reporting function.
  • the implementation of the OAM configuration is implemented on the two ends. To complete the OAM configuration dynamically
  • the source PE 30 and the sink PE 40 may be routers or switches.
  • the processor 301 of the source PE30 and the processor 402 of the sink PE40 may be a central processing unit (referred to as a Central Processing Unit in English, abbreviated as CPU in English).
  • the receiver 303, the transmitter 302, the receiver 401, and the transmitter 403 of the source PE 30 may include a common physical interface, and the physical interface may be an Ethernet interface or an asynchronous transmission mode (English name is Asynchronous). Transfer Mode, English abbreviated as ATM) interface.
  • the receiver 303, the processor 301, and the transmitter 302 of the source PE 30 may be integrated into one or more independent circuits or hardware, such as: an application specific integrated circuit (English called Application Specific Integrated Circuit, ASIC for short).
  • the receiver 401, the processor 402, and the transmitter 403 of the sink PE 40 may be integrated into one or more independent circuits or hardware, such as an ASIC.
  • the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes
  • the foregoing storage medium includes: a read-only memory (referred to as a read-only memory in English), a RAM, a magnetic disk, or an optical disk, and the like, which can store program codes.

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

La présente invention concerne un procédé, un dispositif et un système pour une configuration OAM (exploitation, gestion et maintenance). Le procédé comprend les étapes suivantes : une PE source configure une entité OAM source et interdit à l'entité OAM source d'envoyer des paquets OAM à une PE de destination ; le premier message de demande 'LSP Ping' transportant les informations de configuration de l'entité OAM source est envoyé à la PE de destination ; le premier message de réponse 'LSP Ping' transportant les informations de configuration de l'entité OAM de destination OAM envoyé par la PE de destination est reçu ; lorsque les informations de configuration de l'entité OAM de destination correspondent aux informations de configuration de l'entité OAM source, l'entité OAM source peut avoir une fonction pour envoyer les paquets OAM à la PE de destination. La présente invention concerne en outre des systèmes de configuration de la PE source, de la PE de destination et de l'OAM. Par la solution technique fournie par des modes de réalisation de la présente invention, la charge de travail pour la configuration de la source et de la destination OAM est réduite, les deux extrémités complètent dynamiquement la configuration OAM par un message 'LSP Ping' interactif et les erreurs de configuration manuelle sont évitées.
PCT/CN2013/070534 2012-07-31 2013-01-16 Procédé, dispositif et système pour l'exploitation, la gestion et la maintenance de configuration oam WO2014019348A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210268576.7 2012-07-31
CN201210268576.7A CN103580894B (zh) 2012-07-31 2012-07-31 操作、管理和维护oam配置的方法、设备及系统

Publications (1)

Publication Number Publication Date
WO2014019348A1 true WO2014019348A1 (fr) 2014-02-06

Family

ID=50027186

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/070534 WO2014019348A1 (fr) 2012-07-31 2013-01-16 Procédé, dispositif et système pour l'exploitation, la gestion et la maintenance de configuration oam

Country Status (2)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3116160A4 (fr) * 2014-04-04 2017-01-11 Huawei Technologies Co., Ltd Procédé de traitement de paquets oam, dispositif de réseau, et système de réseau

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103957213A (zh) * 2014-05-05 2014-07-30 上海大亚科技有限公司 基于ping包实现网络服务开启和关闭的系统及方法
CN104270280B (zh) * 2014-09-02 2017-11-07 烽火通信科技股份有限公司 在路由器上实现LSP ping和tracert的系统及方法
CN105577416B (zh) * 2014-10-17 2020-03-10 中兴通讯股份有限公司 一种业务功能链操作、管理和维护方法及节点设备
CN105577413B (zh) * 2014-10-17 2019-09-10 中兴通讯股份有限公司 操作、管理和维护oam报文处理方法及装置
CN105591798B (zh) * 2015-07-24 2019-04-09 新华三技术有限公司 Dcn中传输oam信息的方法、装置
CN108964943B (zh) * 2017-05-18 2022-01-28 中兴通讯股份有限公司 一种实现ioam封装的方法及装置
CN110505035B (zh) * 2018-05-16 2022-04-29 华为技术有限公司 数据处理方法和装置、通信系统
CN110545196A (zh) * 2018-05-28 2019-12-06 华为技术有限公司 一种数据传输方法及相关网络设备
CN110933002B (zh) * 2019-11-25 2021-12-28 苏州盛科科技有限公司 一种mpls带内检测oam的交换芯片实现方法及装置
CN114221867A (zh) * 2020-09-03 2022-03-22 华为技术有限公司 一种操作管理维护oam报文处理方法及设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355441A (zh) * 2007-07-27 2009-01-28 华为技术有限公司 一种配置操作管理维护属性的方法、系统及设备
US20090238084A1 (en) * 2008-03-18 2009-09-24 Cisco Technology, Inc. Network monitoring using a proxy
CN102332987A (zh) * 2010-07-12 2012-01-25 中兴通讯股份有限公司 一种伪线oam属性配置的方法和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1625176B (zh) * 2003-12-03 2010-04-28 华为技术有限公司 基于边缘到边缘伪线仿真协议的通信方法
CN100396023C (zh) * 2005-09-30 2008-06-18 华为技术有限公司 维护多跳伪线的协商控制方法
US8804534B2 (en) * 2007-05-19 2014-08-12 Cisco Technology, Inc. Interworking between MPLS/IP and Ethernet OAM mechanisms

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355441A (zh) * 2007-07-27 2009-01-28 华为技术有限公司 一种配置操作管理维护属性的方法、系统及设备
US20090238084A1 (en) * 2008-03-18 2009-09-24 Cisco Technology, Inc. Network monitoring using a proxy
CN102332987A (zh) * 2010-07-12 2012-01-25 中兴通讯股份有限公司 一种伪线oam属性配置的方法和系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3116160A4 (fr) * 2014-04-04 2017-01-11 Huawei Technologies Co., Ltd Procédé de traitement de paquets oam, dispositif de réseau, et système de réseau
US10116546B2 (en) 2014-04-04 2018-10-30 Huawei Technologies Co., Ltd. OAM packet processing method, network device, and network system

Also Published As

Publication number Publication date
CN103580894A (zh) 2014-02-12
CN103580894B (zh) 2017-09-29

Similar Documents

Publication Publication Date Title
WO2014019348A1 (fr) Procédé, dispositif et système pour l'exploitation, la gestion et la maintenance de configuration oam
US10686698B2 (en) Packet forwarding method, apparatus, and system
US8982710B2 (en) Ethernet operation and maintenance (OAM) with flexible forwarding
EP3223461B1 (fr) Communication de chemin de réseau et informations d'état dans des réseaux à rattachement multiple
US9059902B2 (en) Procedures, apparatuses, systems, and computer-readable media for operating primary and backup network elements
WO2013182059A1 (fr) Procédé et dispositif pour établir un tunnel d'ingénierie de trafic de commutation multiprotocole par étiquette
WO2013097459A1 (fr) Procédé et dispositif de détection de chemin de service
WO2010069175A1 (fr) Procédé, système et équipement d'établissement d'une détection de réexpédition bidirectionnelle
WO2012106869A1 (fr) Procédé de traitement de messages et dispositif associé
WO2013071801A1 (fr) Procédé, dispositif et système pour détecter un réseau en anneau à commutation multiprotocole par étiquette
WO2014032435A1 (fr) Procédé et dispositif de traitement des informations de localisation d'un point de défaut
WO2017000802A1 (fr) Procédé et dispositif de localisation d'anomalie de service
WO2016041379A1 (fr) Procédé et appareil pour mettre en œuvre un nni ping
WO2012024952A1 (fr) {0> procédé et système de commutation de chemin sur la base d'un service point à multipoint <}0{><0}
WO2020001389A1 (fr) Procédé de communication, dispositif et système pour éviter une boucle
WO2009092257A1 (fr) Procédé de détection de défaut et dispositif pour réseau 'provider backbone transport'
EP2634978B1 (fr) Procédé de réexpédition de message et dispositif en réseau
WO2015184868A1 (fr) Dispositif et procédé pour détecter une défaillance de signal dans une couche de service
WO2020036983A9 (fr) Protection d'entrée de tunnel de routage de source
WO2006089490A1 (fr) Méthode d’implémentation de fec bfd
CN105812198B (zh) 桥接网络端到端的监测方法和装置
WO2011127849A2 (fr) Procédé et dispositif de réseau pour la transmission de flux de données
WO2019196914A1 (fr) Procédé de découverte de trajet de réacheminement, et dispositif associé
WO2021052280A1 (fr) Système et procédé de mesure de réseau, dispositif et support de stockage
EP2832055B1 (fr) Groupes de pseudo-fils dans un réseau à commutation de paquets

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13826233

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13826233

Country of ref document: EP

Kind code of ref document: A1