WO2012145903A1 - Procédé et nœud permettant de demander des informations de configuration d'opération, d'administration et de maintenance - Google Patents

Procédé et nœud permettant de demander des informations de configuration d'opération, d'administration et de maintenance Download PDF

Info

Publication number
WO2012145903A1
WO2012145903A1 PCT/CN2011/073433 CN2011073433W WO2012145903A1 WO 2012145903 A1 WO2012145903 A1 WO 2012145903A1 CN 2011073433 W CN2011073433 W CN 2011073433W WO 2012145903 A1 WO2012145903 A1 WO 2012145903A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
configuration information
oam
response
message
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.)
Ceased
Application number
PCT/CN2011/073433
Other languages
English (en)
Chinese (zh)
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 CN201180000326.9A priority Critical patent/CN103609066B/zh
Priority to PCT/CN2011/073433 priority patent/WO2012145903A1/fr
Publication of WO2012145903A1 publication Critical patent/WO2012145903A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • 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
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information

Definitions

  • the present invention relates to the field of data communications, and in particular, to a method and a node for querying configuration information of an operation, management, and maintenance (OAM).
  • OAM operation, management, and maintenance
  • the video service is one of the important services for the growth of the operator's business in the future. Operators need to provide users with services that meet the quality requirements of users, improve user satisfaction, increase the number of users and avoid user churn, and improve operation and maintenance management capabilities.
  • the OAM of the multicast network can detect faults or performance bottlenecks of the network through proactive detection or monitoring. Before the fault occurs, the network performance can be detected to deteriorate, and corresponding measures can be taken to avoid the fault. After the fault occurs, Fast response, reduce the time taken for fault location, trigger the corresponding protection mechanism, and optimize the utilization of network resources.
  • the query of the OAM configuration information of each node may adopt a single-point query mode, and requires a single query on a node-by-node basis, which is cumbersome and not flexible enough.
  • An aspect of the present invention provides a method for querying OAM configuration information, which is used for querying OAM configuration information of each node in a multicast tree or a multicast forwarding path, which can effectively avoid the cumbersome operation of a single point query, and is convenient and fast for querying.
  • the query of the OAM configuration information of the node in the multicast tree or the multicast forwarding path is more flexible, and the other aspect of the present invention provides a node that can query the OAM configuration information.
  • the method for querying the OAM configuration information includes: the node acquires the first request packet, where the first request packet includes the type of the OAM configuration information to be queried; and saves the OAM configuration information corresponding to the type of the OAM configuration information in the node to the first In the request message, the second request message is obtained; determining whether the node is the root node; if the node is not the root node, forwarding the second request message to the previous hop node; if the node is the root node, according to the second request The message generates a response message containing the queried OAM configuration information, and sends a response message.
  • the node includes: an acquiring unit, configured to acquire a first request packet, where the first request packet includes an operation to be queried, a type of management and maintenance OAM configuration information, and a saving unit configured to use the OAM configuration information in the node
  • the OAM configuration information corresponding to the type is saved in the first request packet.
  • a requesting message a first determining unit, configured to determine whether the node is a root node, and a forwarding unit, configured to forward the second request packet to the previous hop node when the node is not the root node, and the response message unit,
  • the response packet containing the queried OAM configuration information is generated according to the second request packet, and the response packet is sent.
  • aspects of the present invention have the following advantages:
  • the OAM configuration information corresponding to the type in the node is saved in the request packet according to the request packet of the type of the OAM configuration information to be queried, so that the request packet is forwarded on the multicast tree or the multicast forwarding path.
  • the OAM configuration information of the node to be queried can be queried, the cumbersome single-point query mode is avoided, the OAM configuration information query efficiency is improved, and the OAM configuration information of the node in the multicast tree or the multicast forwarding path is used for querying.
  • FIG. 1 is a schematic diagram of a relationship between multicast tree OAM entities according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a method for querying OAM configuration information according to an embodiment of the present invention
  • FIG. 3 is another schematic diagram of a method for querying OAM configuration information according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a node according to an embodiment of the present invention
  • FIG. 5 is another schematic diagram of a node in an embodiment of the present invention.
  • the embodiment of the invention provides a method and a node for querying the OAM configuration information, which is used for querying the OAM configuration information of each node in the multicast tree or the multicast forwarding path, thereby avoiding the cumbersome single-point query mode and improving the efficiency and flexibility of the query. Sex.
  • FIG. 1 it is a schematic diagram of an OAM entity relationship in an embodiment of the present invention, where an entity group endpoint is maintained.
  • Maintenance Entity Group End Point Ingress MEP
  • Maintenance Entity Group End Point Egress MEP
  • Maintenance Entity Group Intermediate Point MIP
  • the entity is a type of OAM entity, and the MEP-I, MEP-E, and MIP are logical entities, which can be configured on the interface (incoming interface and/or outbound interface) of the NE (Net element), and the NE management
  • the system EMS, Element Maintenance System
  • the referenced node is a network element (NE, Net Element) or other device.
  • the forwarding direction of the OAM packet may refer to the direction of the arrow in FIG.
  • the interface of the MEP-I entity can be set to initiate an OAM operation from the node.
  • the node will perform multicast data. The flow is counted, and the count value is written into the packet loss measurement message for packet loss detection, and the packet loss measurement message is sent;
  • the MEP_E entity is set on the interface of the node, the node sets the MEP—
  • the interface of the E entity can terminate the OAM operation. For example, when performing the delay measurement, the node obtains the time stamp from the received delay measurement packet, calculates the delay, and completes the delay measurement.
  • the interface that sets the MIP entity of the node will be used to forward packets or transparently transmit OAM files.
  • FIG. 2 is a schematic diagram of a method for querying OAM configuration information according to an embodiment of the present invention, including:
  • the node acquires the first request packet.
  • the node on the path to be queried obtains the request packet for the OAM configuration information query, where the request is reported.
  • the text contains the type of OAM configuration information to be queried.
  • the node obtains the first request message, where the first request message includes the type of the OAM configuration information to be queried.
  • the request message obtained by the node may be referred to as the first request message of the node, and the request message that saves the OAM configuration information of the node may be referred to as the node of the node.
  • the second request message uses the first and second description request messages to better distinguish the two states of the request message in the node.
  • the node saves the OAM configuration information corresponding to the type of the OAM configuration information to be queried in the first request packet to the first request packet, and obtains a second request packet that includes the OAM configuration information of the node.
  • the OAM configuration information may be classified according to the content included in the OAM configuration information, and the type of the OAM configuration information may include any one of the following: an OAM entity configuration, The partial attribute status of the OAM entity, the attribute status of the OAM entity, the OAM entity configuration and routing status information, the partial attribute status and routing status information configured by the OAM entity, and all attribute status and routing status configured by the OAM entity. information.
  • the OAM configuration information may include an OAM entity configuration, an OAM entity attribute, and an OAM entity attribute status.
  • the corresponding OAM configuration information is obtained according to the type of the OAM configuration information in the request packet, for example:
  • the OAM entity configuration on the outbound interface and the inbound interface is obtained.
  • the OAM entity attribute and the corresponding OAM entity attribute status of the OAM entity configured on the node are obtained.
  • the OAM entity attributes and the corresponding OAM entity attribute status configured on the OAM entity are obtained.
  • the OAM entity configuration on the outbound interface and the inbound interface of the node and the routing state information of the node are obtained;
  • the OAM entity attribute and the corresponding OAM entity attribute status and the routing status information of the node are obtained.
  • the OAM entity configuration refers to the type of the OAM entity configured on the inbound or outbound interface of the node, for example, an MEP-I entity, or an MEP-E entity or a MIP entity;
  • the OAM attribute is an OAM attribute configured on the OAM entity of the node.
  • the OAM attribute may include packet loss measurement, delay measurement, throughput measurement, loopback, connectivity detection, alarm indication, protection switching, and the like.
  • the state of the OAM entity attribute is the state of the OAM entity attribute configured on the OAM entity. It can be enabled, disabled, blocked, etc.
  • the OAM entity attribute set on an interface of the node is the packet loss measurement.
  • the node When receiving a packet loss measurement packet from the interface, if the OAM entity belongs to If the status of the OAM entity is disabled, the node will transparently transmit the packet loss measurement packet. If the OAM entity attribute status is blocked, the node will be enabled. Suspending processing of the packet loss measurement message, and simultaneously aborting the packet loss measurement message to the downstream node;
  • the routing status information includes the inbound interface address, the outbound interface address, the running routing protocol, the number of incoming packets on the inbound interface, and the number of outgoing packets on the outbound interface.
  • step 203 determine whether the node is the root node, if not the root node, step 204 is performed, if it is the root node, step 205 is performed;
  • the node will determine whether the node is a root node.
  • the node determines whether the node is a root node, for example, the node can determine whether the node is a queryed multicast tree or multicast by using a running multicast routing protocol.
  • the root node of the forwarding path When the multicast tree is the source tree, the node can determine whether the node is the root node according to the source address of the multicast tree or the multicast forwarding path included in the received request message.
  • the method of determining whether the node is the root node may be determined according to the specific situation, and is not limited herein.
  • the node When the node is not the root node, the node forwards the second request packet to the previous hop.
  • the previous hop node refers to the multicast tree or multicast forwarding path and is sent with the OAM packet. In the opposite direction, the node closer to the root node connected to the node.
  • the root node When the node is the root node, the root node generates a response packet containing the OAM configuration information of each node in the queried multicast tree or the multicast forwarding path according to the second request packet, and sends the generated response packet.
  • each node in the multicast tree or the multicast forwarding path saves the OAM configuration information corresponding to the type of the OAM configuration information in the received request packet to the request packet, and forwards the packet.
  • the request message of the OAM configuration information of the local node is saved, and after the request packet reaches the root node, the root node generates and sends a response packet, so that the network administrator or the operator can obtain the multicast tree or multicast effectively.
  • the OAM configuration information of each node on the forwarding path avoids the cumbersome operation of the single-point query and improves the efficiency of OAM configuration information query.
  • the message used for the OAM configuration query may be the extended Mtrace message, or may be newly defined. In the actual application, you can determine whether to use the extended Mtrace message or the newly defined OAM configuration information to query the OAM configuration information. Not limited.
  • FIG. 3 is the present invention.
  • Another schematic diagram of the method for querying the OAM configuration information in the embodiment includes: 301: The node acquires the first request packet;
  • the node in the multicast tree or the multicast forwarding path to obtain the first request packet is received: the first request packet of the extended Mtrace sent by the downstream node is received. Or generating the first request message of the extended Mtrace according to the received Mtrace query message, where the first request message includes the type of the OAM configuration information to be queried and is used to save the OAM configuration information.
  • the response data block is generated.
  • Mtrace is a common tool for route detection on a multicast network. It is used to query the routing status information of each node on the multicast forwarding path of a built-in multicast tree from a leaf node to a root node.
  • the working principle of Mtrace is Any node on the multicast tree or the multicast tree sends a query message to the leaf node on the multicast forwarding path to be queried. After the query message arrives at the leaf node, the leaf node generates a request message of the Mtrace.
  • the routing state information of the leaf node is saved in the response data block corresponding to the request message, and the request message storing the routing state information of the leaf node is forwarded to the previous hop node, and the previous hop node is routing the local node.
  • the last hop node continues to forward the request message that has saved the routing state information of the local node.
  • the request message reaches the root node of the multicast forwarding path, The forwarding will be stopped, and the request message on the root node contains the routing state information of each node that has arrived on the multicast forwarding path.
  • the existing Mtrace also supports an exception handling mechanism when a node's route detection fails. For example, when an OAM configuration state of a node and a route state collection process are abnormal, the node transmits the interrupt request message to the upstream node, and advances to The node where the response address is located sends a response message.
  • the extended MTR is used, that is, the field for querying the OAM configuration information is added to the Mtrace packet, and the OAM configuration information on the multicast forwarding path is queried. Therefore, when the network administrator or the operator needs to query the OAM configuration information of the multicast tree or the multicast forwarding path, the leaf node on the multicast tree or multicast forwarding path to be queried will receive the extended Mtrace query. And the leaf node generates a request message including the type of the OAM configuration information to be queried according to the query text.
  • the extended Mtrace message is:
  • the content of the extended Mtrace packet can be a type-length-value structure.
  • the type is the specific type of the packet.
  • the type of the Mtrace packet can be a query packet, or a request packet, or a response packet.
  • the length is Refers to the length of the packet value field.
  • the value contains the common header and response data block of the Mtrace message.
  • the public header contains the packet type, length, hop count and group address, source address, destination address, response address, and response. TTL, Query ID (ID), OAM configuration information type, Maintenance Entity Group Identity (MEG_ID, Maintenance Entity Group Identity), etc.
  • the hop count is the maximum hop count that the packet can be queried.
  • the group address is Indicates the multicast address of the multicast tree or multicast forwarding path.
  • the source address refers to the source address of the multicast tree or multicast forwarding path.
  • the destination address refers to the address of the multicast receiver.
  • the response address is the response address.
  • the address of the node to be sent, the response time to live (TTL, Time To Live) is the maximum number of hops sent by the response packet.
  • the query ID is the ID that identifies the query.
  • OAM The type of the information is the type of the OAM configuration information to be queried.
  • the MEG-ID is an identifier of the maintenance group that identifies the group.
  • the ID is unique in the maintenance management domain.
  • the forwarding code is included, and the forwarding code is used to identify the state of the routing state information query of the node where the request packet is located, and the routing state information of the node is known according to the value of the forwarding code.
  • the query is faulty.
  • the format of the response data block used for saving the OAM configuration information in the extended Mtrace is related to the specific type of the OAM configuration information to be queried, and different types correspond to different response data block formats.
  • the type of the OAM configuration information includes, but is not limited to, the OAM entity configuration, the OAM entity configured partial attribute status, the OAM entity configured all attribute status, the OAM entity configuration and routing status information, and the OAM entity configured partial attribute status. And routing status information, all attribute status and routing status information that the OAM entity has configured.
  • the node Encapsulate the OAM configuration information corresponding to the type of the OAM configuration information in the node.
  • the node performs the node according to the type of the OAM configuration information to be queried in the first request packet.
  • the OAM configuration information corresponding to the type is encapsulated.
  • the node may parse the received first request packet, obtain the OAM configuration information corresponding to the type of the OAM configuration information in the first request packet, and encapsulate the OAM configuration information into the first request packet.
  • the format in which the data block can be saved is such that the OAM configuration information can be saved in the first request message.
  • the node before performing step 302, the node further determines whether the query of the OAM configuration information of the request packet on the node is faulty, wherein the fault condition includes but is not limited to: The node does not support OAM configuration information query, or the node routing information is incorrect, or the node is managed to prohibit the upstream hop node from forwarding the request message.
  • the node determines that the query of the OAM configuration information of the first request packet is faulty, the node generates a response packet according to the first request packet, and sends the generated response packet to the response packet.
  • the node After the information is encapsulated, the node saves the encapsulated information in the response data block of the first request message to obtain a second request message. It should be noted that, for different types of OAM configuration information, the format and length of the response data block included in the first request message may also be different.
  • the response data block for saving the OAM entity configuration information may include the query arrival time, the inbound interface address, the outbound interface address, the inbound interface configuration entity, the outbound interface configuration entity, the response code, and the like.
  • the format of the response data block may refer to the following table:
  • the inbound time of the query refers to the time when the request packet arrives at the node.
  • the inbound interface address and the outbound interface address are the inbound interface address and the outbound interface address of the multicast forwarding routing entry of the local node.
  • the outbound interface configuration entity refers to the OAM entity configured on the ingress/egress interface, and the length refers to the length of the response data block.
  • the response code is used to identify the status of the OAM configuration information query of the node where the request packet is located. For example, the status of the query may be normal, or an interface error, or a fatal error.
  • the forwarding code and the format definition of the response code defined by Mtrace are similar, only the same set of codes may be used in use, or a unique response code may be defined.
  • the request message is used to save the OAM entity.
  • the format of the response data block of the attribute can be referred to the following table:
  • the OAM entity attribute refers to the OAM attribute configured on the OAM entity of the node
  • the response data block format corresponding to the OAM entity attribute includes the format and attribute status block of the response data block corresponding to the OAM entity configuration information.
  • the response data block in the extended Mtrace message may include an attribute status block.
  • the attribute status block includes the attribute identification field and the attribute status subtype length value (TLV, Type
  • the attribute identifier field is used to indicate whether the OAM attribute to which the field belongs needs to be queried. If the attribute identifier field is 1, the corresponding attribute query is supported. If the attribute identifier is 0, the corresponding attribute is not supported.
  • the L and D fields are attribute identification fields, and L is the packet loss measurement identifier. When the value of this field is 1, the request message will be queried on the multicast forwarding tree or on the multicast forwarding path.
  • the packet loss measurement OAM configuration attribute status, D is the delay measurement identifier. When the value of the field is 1, the request message will query the delay measurement OAM configuration attribute status on the multicast tree or the multicast forwarding path.
  • the status sub-TLV of all valid attributes is included in the order of all valid attributes in the field (that is, the corresponding attribute identification field is set to 1), that is, the attribute status sub-TLV field, preferably, when the attribute identification field If the value is 0, the OAM entity is configured on the interface of the node, but no OAM attribute is supported.
  • the attribute status block may not contain the attribute status sub-TLV field.
  • the reserved field contained in the response data block for saving the OAM entity attribute can be used for setting other types of flag bits, and the reserved field has a value of 0 before being used.
  • each valid attribute status sub-TLV in the attribute status sub-TLV field may adopt a type-length-one-value format, and the type is used to distinguish different OAM entity attributes, and the length is a sub-TLV.
  • the length of the value is the value of the corresponding OAM entity attribute.
  • the content of the different attribute status in the attribute status field may also contain different content, which is not limited here.
  • the format of the response data block of all the attribute states that the OAM entity has configured may refer to the format of the foregoing response data block for saving the partial attribute state of the OAM entity.
  • the format of the response data block containing the OAM entity configuration and routing status information for the node is as follows:
  • the response data block for storing OAM entity configuration and routing state information includes a response data block for saving the OAM entity configuration and a Mtrace for saving the route.
  • a response data block for status information includes a response data block for status information.
  • the response data block for saving the OAM configuration information of the type in the request packet may be used. Adding a field for saving the routing state information on the response data block that is used to save the partial attribute state of the configured OAM entity. Similarly, if you need to query all attribute states and routes configured by the node's OAM entity.
  • the format of the response data block for the OAM configuration information of the request type in the request message may be added to the saved response data block for saving all the attribute states of the OAM entity configured. The field of the status information, the specific format of the response data block will not be described here.
  • the format of all the response data blocks mentioned above can be used as a reference format.
  • the content and format of the response data block can be set according to specific needs, which is not limited herein.
  • the OAM configuration information may be queried by defining a new OAM configuration information query protocol. In actual applications, it may be determined according to requirements.
  • the query of the OAM configuration information is implemented by using the extended Mtrace or the protocol of the newly defined OAM configuration information, which is not limited herein.
  • step 304 determining whether the node is the root node, if the node is not the root node, step 305 is performed, if the node is the root node, step 306 is performed;
  • the node determines whether the node is a root node.
  • the node that obtains the request message When the node that obtains the request message is not the root node, the node forwards the request message to the previous hop node. It should be noted that, after receiving the forwarded request message, the last hop node will also perform the method described in the embodiment of the present invention.
  • the root node Generate, according to the second request packet, a response packet that includes the queried OAM configuration information.
  • the root node When the request packet has arrived at the root node, the root node generates, according to the request packet, the queried message.
  • the root node sends the response packet to the node corresponding to the response address included in the response packet, where the node corresponding to the response address is the multicast tree that sends the query packet to the leaf node. Or a node outside the multicast tree.
  • the node in the multicast tree to be queried or the node in the multicast forwarding path is forwarded by using the request packet in the extended Mtrace, and the node corresponds to the node after receiving the request packet.
  • the OAM configuration information is saved in the request packet.
  • the root node ends the OAM configuration information query operation, and sends the response packet generated according to the request packet to the node corresponding to the response address.
  • the network administrator or the operator can obtain the OAM configuration information of each node in the multicast tree or the multicast forwarding path, because the response packet contains the OAM configuration information of the nodes in the multicast tree or the multicast forwarding path. It avoids the cumbersome and inflexible single-point query, improves the efficiency of OAM configuration information query, and is applicable to the query of OAM configuration information of the multicast tree and the multicast forwarding path.
  • FIG. 4 it is a schematic diagram of a node in an embodiment of the present invention, including:
  • the obtaining unit 401 is configured to obtain a first request message, where the first request message includes a type of operation, management, and maintenance OAM configuration information to be queried;
  • the saving unit 402 is configured to save the OAM configuration information corresponding to the type of the OAM configuration information in the node to the first request packet, to obtain the second request packet.
  • a first determining unit 403, configured to determine whether the node is a root node
  • the forwarding unit 404 is configured to: when the node is not the root node, forward the second request packet to the last hop node;
  • the response message unit 405 is configured to: when the node is the root node, generate a response message including the queried OAM configuration information according to the second request message, and send the response message.
  • the saving unit 402 saves the OAM configuration information corresponding to the type of the OAM configuration information in the first request message to the first request.
  • the second request message is obtained.
  • the first determining unit 403 determines whether the local node is the root node.
  • the forwarding unit 404 forwards the second request packet to the previous hop node.
  • the response message unit 405 generates a response message including the queried OAM configuration information according to the second request message, and sends a response message.
  • FIG. 5 is another schematic diagram of a node according to an embodiment of the present invention, including:
  • the obtaining unit 401, the saving unit 402, the first determining unit 403, the forwarding unit 404, and the response message unit 405 described in the embodiment shown in FIG. 4 are similar to the content described in the embodiment shown in FIG. Let me repeat.
  • the obtaining unit 401 includes:
  • the first receiving unit 501 is configured to receive the extended Mtrace query message.
  • the request message generating unit 502 is configured to generate, according to the extended query message of the Mtrace, the first request message of the extended Mtrace, where the first request message further includes a response data block for saving the OAM configuration information;
  • the second receiving unit 503 is configured to receive the first request message of the extended Mtrace.
  • the node may further include:
  • the second determining unit 504 is configured to determine whether the query of the OAM configuration information of the first request packet on the node is faulty.
  • the exception handling unit 505 is configured to: when the first request message is configured on the node, the OAM configuration information.
  • the response packet is generated according to the request packet, and the response packet is sent, and the response packet includes the queried OAM configuration information.
  • the first receiving unit 501 of the leaf node on the corresponding multicast tree or the multicast forwarding path receives the information.
  • the request message generating unit 502 After the extended Mtrace query message, the request message generating unit 502 generates a request message including the type of the OAM configuration information to be queried according to the extended Mtrace query message, and then the second determining unit 504 determines the extension. If the query of the OAM configuration information of the Mtrace request packet is faulty, when the query of the OAM configuration information fails, the exception handling unit 505 stops forwarding the request packet and sends a response report generated according to the request packet. Text.
  • the saving unit 402 of the node saves the corresponding OAM configuration information of the node into the request packet according to the type of the OAM configuration information included in the request packet, and
  • the first determining unit 403 determines whether the node is the root node. Since the node is not the root node, the forwarding unit 404 forwards the request message to the previous hop node, and the second receiving unit 503 of the last hop node receives the request report.
  • the second determining unit 504 of the previous hop node determines whether the query of the OAM configuration information of the request packet is faulty. If the query of the OAM configuration information of the request packet fails, the abnormality of the node is abnormal.
  • the processing unit 505 stops forwarding the request message and sends a response message generated according to the request message.
  • the saving unit 402 saves the corresponding OAM configuration information in the node to the request packet according to the type of the OAM configuration information included in the request packet, and the previous hop node
  • the first determining unit 403 determines whether the node is the root node. When the last hop node is not the root node, the forwarding unit 404 continues to forward the request message.
  • the message generating unit 405 When the last hop node is the root node, the response in the root node
  • the message generating unit 405 generates a response message including the OAM configuration information according to the request message, and the response unit 506 sends the generated response message to the node corresponding to the response address included in the response message.
  • FIG. 2 and FIG. 3 can be implemented by using the apparatus embodiment shown in FIG. 4 or FIG. 5.
  • the request message used for the OAM configuration information query is forwarded hop by hop on the multicast tree or the multicast forwarding path.
  • the node configures the OAM in the local node.
  • the OAM configuration information corresponding to the type of the information is saved in the request packet and forwarded.
  • the request message of the OAM configuration information of the local node is saved until the root node is reached or the query is faulty.
  • the node generates a response packet according to the request packet and sends a response packet, so that the OAM configuration information query operation is simple and flexible. Applicable to the query of OAM configuration information of the entire multicast tree node.
  • the medium can be a read only memory, a magnetic disk or a compact disk or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé et un nœud permettant de demander des informations de configuration d'opération, d'administration et de maintenance (OAM). Ledit procédé se déroule de la manière suivante : un nœud acquiert un premier message de demande qui contient le type des informations de configuration d'OAM à demander ; ce nœud insère les informations de configuration d'OAM qui correspondent au type des informations de configuration d'OAM dans le premier message de demande pour obtenir un second message de demande ; une évaluation est effectuée pour déterminer si le nœud est un nœud racine ; si le nœud n'est pas un nœud racine, il envoie le second message de demande à un nœud supérieur ; si le nœud est un nœud racine, il génère un message de réponse contenant les informations de configuration d'OAM demandées sur la base du second message de demande, puis il remet le message de réponse.
PCT/CN2011/073433 2011-04-28 2011-04-28 Procédé et nœud permettant de demander des informations de configuration d'opération, d'administration et de maintenance Ceased WO2012145903A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201180000326.9A CN103609066B (zh) 2011-04-28 2011-04-28 操作、管理、维护配置信息查询的方法及节点
PCT/CN2011/073433 WO2012145903A1 (fr) 2011-04-28 2011-04-28 Procédé et nœud permettant de demander des informations de configuration d'opération, d'administration et de maintenance

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/073433 WO2012145903A1 (fr) 2011-04-28 2011-04-28 Procédé et nœud permettant de demander des informations de configuration d'opération, d'administration et de maintenance

Publications (1)

Publication Number Publication Date
WO2012145903A1 true WO2012145903A1 (fr) 2012-11-01

Family

ID=47071558

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/073433 Ceased WO2012145903A1 (fr) 2011-04-28 2011-04-28 Procédé et nœud permettant de demander des informations de configuration d'opération, d'administration et de maintenance

Country Status (2)

Country Link
CN (1) CN103609066B (fr)
WO (1) WO2012145903A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240214315A1 (en) * 2021-12-06 2024-06-27 Cisco Technology, Inc. Platform independent on demand network management and monitoring

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108964943B (zh) * 2017-05-18 2022-01-28 中兴通讯股份有限公司 一种实现ioam封装的方法及装置
CN108965204B (zh) * 2017-05-18 2022-01-25 中兴通讯股份有限公司 一种自动实现ioam封装的方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159688A (zh) * 2007-11-08 2008-04-09 华为技术有限公司 组播路由跟踪的方法和路由器
CN101741592A (zh) * 2008-11-13 2010-06-16 华为技术有限公司 多业务传送网中管理gpon支路的方法、设备及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7996559B2 (en) * 2007-10-12 2011-08-09 Nortel Networks Limited Automatic MEP provisioning in a link state controlled Ethernet network
CN101789900B (zh) * 2009-11-19 2012-08-15 福建星网锐捷网络有限公司 组播转发路径的查询方法、中间节点和管理节点
CN101980473B (zh) * 2010-10-09 2014-06-11 中兴通讯股份有限公司 一种组播路径跟踪方法和系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159688A (zh) * 2007-11-08 2008-04-09 华为技术有限公司 组播路由跟踪的方法和路由器
CN101741592A (zh) * 2008-11-13 2010-06-16 华为技术有限公司 多业务传送网中管理gpon支路的方法、设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
YANG MIN ET AL.: "A Management Tool for IPv 6 Multicast Monitor Based on M trace", MODERN ELECTRICS TECHNOLOGY, vol. 27, no. 2, January 2004 (2004-01-01), pages 39 - 42 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240214315A1 (en) * 2021-12-06 2024-06-27 Cisco Technology, Inc. Platform independent on demand network management and monitoring
US12348423B2 (en) * 2021-12-06 2025-07-01 Cisco Technology, Inc. Platform independent on demand network management and monitoring

Also Published As

Publication number Publication date
CN103609066B (zh) 2017-04-26
CN103609066A (zh) 2014-02-26

Similar Documents

Publication Publication Date Title
CN113411834B (zh) 报文处理方法、装置、设备及存储介质
CN110120900B (zh) 通信方法、网络的集中控制器设备及网络中的网络设备
KR102364803B1 (ko) 통신 방법, 통신 장치 및 저장 매체
CN103580894B (zh) 操作、管理和维护oam配置的方法、设备及系统
WO2021227561A1 (fr) Procédé et appareil de communication
CN102647312B (zh) 一种整网组播拓扑的探测方法及装置
WO2019184752A1 (fr) Procédé, appareil et système de gestion de dispositifs de réseau
WO2008037203A1 (fr) Procédé et dispositif noeud destinés à réaliser une découverte de topologie réseau
CN103078791B (zh) Oam报文处理方法、设备及系统
WO2020168854A1 (fr) Procédé, appareil, et système de multidiffusion evpn
US9998364B2 (en) Method for processing packet and forwarder
CN113055293B (zh) 软件定义广域网中的选路方法及装置、通信系统
WO2021000752A1 (fr) Procédé et dispositif associé pour l'acheminement de paquets dans un réseau de centre de données
WO2008028384A1 (fr) Procédé et système de mise en oeuvre de commande de transmission pour messages oam
WO2011144158A1 (fr) Procédé et système de mise en œuvre indépendante d'une localisation de dérangement par un nœud intermédiaire
WO2022121638A1 (fr) Procédé et dispositif de traitement de paquets
WO2019157802A1 (fr) Procédé, dispositif, et système de réseau pour mesurer la performance d'un réseau
WO2007073649A1 (fr) Procede et systeme pour obtenir une unite de transfert maximale de voie dans un reseau
CN102088417B (zh) 实现ip报文环回的方法及设备
WO2011127849A2 (fr) Procédé et dispositif de réseau pour la transmission de flux de données
CN110380966B (zh) 一种发现转发路径的方法及其相关设备
US9537672B2 (en) Method for managing customer edge device automatically and PE device
WO2012145903A1 (fr) Procédé et nœud permettant de demander des informations de configuration d'opération, d'administration et de maintenance
WO2012142753A1 (fr) Procédé et dispositif de surveillance des performances d'un réseau support ip
CN105790984B (zh) 一种操作维护管理功能的配置、实现方法及转发设备

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: 11864238

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: 11864238

Country of ref document: EP

Kind code of ref document: A1