CN102299815B - Configuration method and node of OAM (operation, administration and maintenance) - Google Patents
Configuration method and node of OAM (operation, administration and maintenance) Download PDFInfo
- Publication number
- CN102299815B CN102299815B CN201010213835.7A CN201010213835A CN102299815B CN 102299815 B CN102299815 B CN 102299815B CN 201010213835 A CN201010213835 A CN 201010213835A CN 102299815 B CN102299815 B CN 102299815B
- Authority
- CN
- China
- Prior art keywords
- oam
- node
- configuration information
- intermediate node
- multicast
- 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.)
- Expired - Fee Related
Links
Images
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明实施例提供一种运营管理和维护的配置方法和节点，所述运营管理和维护的配置方法包括：组播树的中间节点接收所述中间节点的下游节点发送的组播加入报文，所述组播加入报文包括运营、管理和维护(OAM)配置信息；所述中间节点根据所述OAM配置信息配置所述中间节点的OAM属性，并将所述组播加入报文发送给所述中间节点的上游节点，以便所述中间节点的上游节点根据所述组播加入报文中的OAM配置信息配置自身的OAM属性，并发送所述组播加入报文，直至将所述组播加入报文逐跳发送至所述组播树的根节点。本发明实施例实现了对组播树上节点的OAM属性的自动配置，减少了人为配置的工作量，避免和减少了人为错误，可操作性好。
Embodiments of the present invention provide a configuration method and node for operation management and maintenance, wherein the configuration method for operation management and maintenance includes: an intermediate node of the multicast tree receives a multicast join message sent by a downstream node of the intermediate node, The multicast join message includes operation, management and maintenance (OAM) configuration information; the intermediate node configures the OAM attribute of the intermediate node according to the OAM configuration information, and sends the multicast join message to all The upstream node of the intermediate node, so that the upstream node of the intermediate node configures its own OAM attributes according to the OAM configuration information in the multicast join message, and sends the multicast join message until the multicast The join message is sent to the root node of the multicast tree hop by hop. The embodiment of the present invention realizes the automatic configuration of the OAM attributes of the nodes on the multicast tree, reduces the workload of manual configuration, avoids and reduces human errors, and has good operability.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a configuration method and a node for operation management and maintenance.
Background
The video service is one of important services for service growth of operators in the future, and the operators need to provide services meeting the quality requirements of users for users, so that the satisfaction degree of the users is improved, the number of the users is increased, the loss of the users is avoided, and the operation and maintenance management capacity of a video network is improved. The operation, administration and Maintenance (OAM) of the multicast network can find the fault point or the performance bottleneck point of the network by active detection or monitoring, detect the deterioration of the network performance before the fault occurs, and take corresponding measures to avoid the fault; after the fault occurs, the method can quickly respond, reduce the time for fault location, trigger a corresponding protection mechanism and optimize the utilization of network resources.
OAM-defined functions typically include both fault management and performance measurement. The fault management comprises connectivity detection, connectivity verification, loopback, alarm indication signals, remote defect indication, locking signals, automatic protection switching and the like; the performance measurement includes packet loss measurement, delay measurement, throughput measurement, and the like.
Video service of Internet Protocol Television (IPTV) has the characteristic of unidirectional, point-to-multipoint multicast transmission, and OAM of a multicast network is usually completed by unidirectional OAM message transmission. For example, for performance measurement, a packet loss measurement OAM message may be sent by a sending end, the OAM message carries the number of sent messages counted by the sending end, a receiving end counts the number of actually received messages, and then compares the number of sent messages carried in the OAM message to obtain the number of lost messages; similarly, delay measurement can measure the time delay of a message reaching a receiving end by a method of stamping a time stamp on a delay measurement message sent by a sending end. When the message loss rate or the delay measurement value in a certain time interval exceeds the normal threshold, the performance of the multicast network is judged to be reduced or abnormal.
The performance measurement and other OAM detection means can be carried out not only between the root node and the leaf nodes of the multicast tree, but also on intermediate nodes between the root node and the leaf nodes. Before measurement, the network needs to configure the root node, leaf node, and intermediate node of the multicast tree participating in measurement, and configure the processing mode of these nodes on the OAM packet, for example: enable and disable, etc.
In the prior art, each node on the multicast tree may be configured by a manual configuration or management protocol to complete OAM configuration on a root node, a leaf node, and an intermediate node of the multicast tree participating in measurement.
Disclosure of Invention
The embodiment of the invention provides a configuration method and nodes for operation management and maintenance, which are used for realizing automatic configuration of OAM attributes of nodes on a multicast tree, reducing the workload of manual configuration and avoiding and reducing manual errors.
The embodiment of the invention provides a configuration method for operation management and maintenance, which comprises the following steps:
an intermediate node of a multicast tree receives a multicast adding message sent by a downstream node of the intermediate node, wherein the multicast adding message comprises operation, administration and maintenance (OAM) configuration information;
and the intermediate node configures the OAM attribute of the intermediate node according to the OAM configuration information and sends the multicast adding message to an upstream node of the intermediate node, so that the upstream node of the intermediate node configures the OAM attribute of the intermediate node according to the OAM configuration information in the multicast adding message and sends the multicast adding message until the multicast adding message is sent to a root node of the multicast tree hop by hop.
The embodiment of the invention also provides a configuration method for operation management and maintenance, which comprises the following steps:
a root node of a multicast tree receives a multicast adding message sent by a downstream node of the root node, wherein the multicast adding message comprises operation, administration and maintenance (OAM) configuration information;
and the root node configures the OAM attribute of the root node according to the OAM configuration information.
The embodiment of the present invention further provides an intermediate node of a multicast tree, including:
a receiving module, configured to receive a multicast join packet sent by a downstream node of the intermediate node, where the multicast join packet includes operation, administration and maintenance (OAM) configuration information;
the configuration module is used for configuring the OAM attribute of the intermediate node according to the OAM configuration information;
and the sending module is used for sending the multicast adding message to the upstream node of the intermediate node so that the upstream node of the intermediate node configures the OAM attribute of the upstream node according to the OAM configuration information in the multicast adding message and sends the multicast adding message until the multicast adding message is sent to the root node of the multicast tree hop by hop.
An embodiment of the present invention further provides a root node of a multicast tree, including:
a message receiving module, configured to receive a multicast join message sent by a downstream node of the root node, where the multicast join message includes operation, administration and maintenance (OAM) configuration information;
and the attribute configuration module is used for configuring the OAM attribute of the root node according to the OAM configuration information.
An embodiment of the present invention further provides a leaf node of a multicast tree, including:
a node attribute configuration module, configured to configure an operation, administration and maintenance (OAM) attribute of the leaf node according to OAM configuration information configured on the leaf node;
and the message sending module is used for sending a multicast adding message to an upstream node of the leaf node, wherein the multicast adding message comprises the OAM configuration information.
Through the embodiment of the invention, after the intermediate node of the multicast tree receives the multicast adding message sent by the downstream node of the intermediate node, the OAM attribute of the intermediate node is configured according to the OAM configuration information in the multicast adding message, and then the multicast adding message is sent to the upstream node of the intermediate node; after receiving the multicast join message, the root node of the multicast tree configures the OAM attribute of the root node according to the OAM configuration information in the multicast join message; therefore, automatic configuration of OAM attributes of nodes on the multicast tree is realized, workload of manual configuration is reduced, manual errors are avoided and reduced, and operability is good.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
FIG. 1 is a flow chart of an embodiment of a configuration method for operation administration and maintenance of the present invention;
fig. 2 is a flowchart of another embodiment of the configuration method for operation administration and maintenance according to the present invention;
FIG. 3 is a flow chart of a configuration method for operation administration and maintenance according to still another embodiment of the present invention;
fig. 4 is a schematic diagram of the relationship of the OAM entities of the multicast tree according to the present invention;
FIG. 5 is a diagram illustrating one embodiment of an encoded source address format for adding attributes in accordance with the present invention;
fig. 6 is a diagram illustrating an embodiment of an OAM adding attribute format according to the present invention;
FIG. 7 is a diagram illustrating one embodiment of a format of a MIP configuration TLV of the present invention;
fig. 8 is a diagram illustrating an embodiment of a format of a MEP _ I configuration TLV according to the present invention;
fig. 9 is a diagram illustrating an embodiment of a format of a MEP _ E configuration TLV according to the present invention;
fig. 10 is a diagram illustrating an embodiment of a format of an OAM configuration option in a Hello message according to the present invention;
FIG. 11 is a diagram illustrating a structure of a leaf node of a multicast tree according to an embodiment of the present invention;
FIG. 12 is a diagram illustrating an intermediate node of a multicast tree according to an embodiment of the present invention;
FIG. 13 is a diagram illustrating an intermediate node of a multicast tree according to another embodiment of the present invention;
FIG. 14 is a structural diagram of a root node of a multicast tree according to an embodiment of the present invention;
fig. 15 is a schematic structural diagram of an embodiment of the configuration system for operation management and maintenance according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
Fig. 1 is a flowchart of an embodiment of an operation management and maintenance configuration method according to the present invention, and as shown in fig. 1, the operation management and maintenance configuration method may include:
In this embodiment, the OAM configuration information is configured in advance at a leaf node of the multicast tree, and specifically, the OAM configuration information may be configured in advance at the leaf node of the multicast tree through a Command Line Interface (CLI), a network management protocol, or another control protocol.
Of course, the embodiment of the present invention is not limited to this, and other manners may also be used to configure the OAM configuration information at the leaf node of the multicast tree.
Specifically, configuring the OAM attribute of a leaf node of the multicast tree according to the OAM configuration information configured on the leaf node may be: the leaf node configures an OAM attribute on an ingress interface and/or an egress interface of the leaf node according to the OAM configuration information, for example: a Maintenance Entity Group End point (MEP _ E) enabling or MEP _ E de-enabling can be configured on an input interface and/or an output interface of the leaf node; that is, the OAM attribute may be configured on the ingress interface and/or the egress interface of the leaf node, and the supported function may be packet loss measurement enable, delay measurement enable, or other types of OAM functions.
In this embodiment, after configuring the OAM attribute of the leaf node according to the OAM configuration information, in order to enable the OAM attribute configured at the leaf node to dynamically track the change of the multicast tree topology, an association between the configured OAM attribute and the multicast tree state needs to be established. When the multicast state of a leaf node is deleted due to the change of the multicast tree topology, the OAM attributes configured to the ingress interface and the egress interface of the leaf node are also deleted, so that the residue of useless OAM attributes on the jointless nodes is avoided.
Specifically, the sending of the multicast join packet to the upstream node of the leaf node may be: the leaf node of the multicast tree may periodically send or send the multicast join packet as needed to the upstream node of the leaf node.
In the above embodiment, the leaf node of the multicast tree configures the OAM attribute of the leaf node according to the OAM configuration information, and sends the multicast join packet carrying the OAM configuration information to the upstream node of the leaf node, so that the upstream node of the leaf node configures the OAM attribute of itself according to the OAM configuration information, thereby implementing automatic configuration of the OAM attribute of the node on the multicast tree, reducing workload of manual configuration, avoiding and reducing manual errors, and having good operability.
Fig. 2 is a flowchart of another embodiment of the configuration method for operation management and maintenance of the present invention, and as shown in fig. 2, the configuration method for operation management and maintenance may include:
In this embodiment, the downstream node of the intermediate node may be a leaf node and/or an upstream node of the leaf node.
Specifically, the intermediate node may configure an OAM attribute on an ingress interface and/or an egress interface of the intermediate node according to the OAM configuration information, for example: maintenance Entity Group Intermediate Point (MIP) enabling or MIP disabling can be configured on the input interface and/or the output interface of the Intermediate node; the OAM attributes may be configured on an ingress interface and/or an egress interface of the intermediate node, and the supported functions may be packet loss measurement enable, delay measurement enable, or other types of OAM functions.
Specifically, in this embodiment, the sending of the multicast join packet to the upstream node of the intermediate node may be: the intermediate node may send the multicast join message periodically or on demand to an upstream node of the intermediate node.
In an implementation manner of this embodiment, the intermediate node may include an ingress interface and at least two egress interfaces, and when OAM configuration information received by at least two egress interfaces is different, the intermediate node may configure different OAM attributes on the at least two egress interfaces according to the OAM configuration information received by the at least two egress interfaces, and then perform fusion processing on the OAM configuration information received by the at least two egress interfaces, and if the OAM configuration information received by the at least two egress interfaces is capable of being fused, configure an OAM attribute on the ingress interface of the intermediate node according to the OAM configuration information after the fusion processing. At this time, the intermediate node needs to send a multicast join packet including the OAM configuration information after the fusion processing to the upstream node of the intermediate node. The OAM configuration information received by the at least two egress interfaces may be fused as follows: the OAM configuration information received by the at least two outgoing interfaces is not contradictory, and the intermediate node can form the OAM configuration information which is consistent with the upstream node of the intermediate node according to the OAM configuration information received by the at least two outgoing interfaces. For example, assume that OAM configuration information received by an egress interface of an intermediate node configures packet loss measurement attribute enablement for a forwarding branch where a downstream node connected to the egress interface is located, and configures the OAM configuration information on the ingress interface and the egress interface; the OAM configuration information received by the other outgoing interface of the intermediate node is the delay measurement attribute enabling of the forwarding branch where the downstream node connected with the outgoing interface is located, and is also configured on the incoming interface and the outgoing interface; at this time, the OAM configuration information received by the two outgoing interfaces of the intermediate node may be fused, and after the intermediate node performs fusion processing on the OAM configuration information received by the two outgoing interfaces of the intermediate node, the obtained OAM configuration information is enabled for the packet loss measurement attribute and the delay measurement attribute.
In another implementation manner of this embodiment, the multicast join packet may include, in addition to the OAM configuration information, other join attributes except for the OAM configuration information, and the intermediate node may perform fusion processing on the OAM configuration information and the other join attributes except for the OAM configuration information first, and then configure the attribute of the intermediate node according to a result of the fusion processing.
In addition, after the intermediate node configures the OAM attribute of the intermediate node according to the OAM configuration information, in order to enable the OAM attribute configured at the intermediate node to dynamically track the change of the multicast tree topology, an association between the configured OAM attribute and the multicast tree state needs to be established. When the multicast state of the intermediate node is deleted due to the change of the multicast tree topology, the OAM attributes configured to the ingress interface and the egress interface of the leaf node are also deleted, so that the residue of useless OAM attributes on the jointless nodes is avoided.
In the above embodiment, after receiving a multicast join message sent by a downstream node of the intermediate node, an intermediate node of the multicast tree configures an OAM attribute of the intermediate node according to OAM configuration information in the multicast join message, and sends the multicast join message to an upstream node of the intermediate node; therefore, automatic configuration of OAM attributes of nodes on the multicast tree is realized, workload of manual configuration is reduced, manual errors are avoided and reduced, and operability is good.
Fig. 3 is a flowchart of a configuration method for operation management and maintenance according to still another embodiment of the present invention, and as shown in fig. 3, the configuration method for operation management and maintenance may include:
step 301, a root node of a multicast tree receives a multicast join message sent by a downstream node of the root node, where the multicast join message includes OAM configuration information.
Step 302, the root node configures the OAM attribute of the root node according to the OAM configuration information.
Specifically, the root node may configure an OAM attribute at an ingress interface and/or an egress interface of the root node according to the OAM configuration information; for example: maintenance Entity Group entry End Point (MEP _ I) enabling or MEP _ I disabling can be configured at an Ingress interface and/or an egress interface of the root node; the OAM attributes may be configured on an ingress interface and/or an egress interface of the root node, and the supported functions may be packet loss measurement enable, delay measurement enable, or other types of OAM functions.
In an implementation manner of this embodiment, a root node may include one ingress interface and at least two egress interfaces, where when OAM configuration information received by at least two egress interfaces is different, the root node may configure different OAM attributes on the at least two egress interfaces according to the OAM configuration information received by the at least two egress interfaces, and then perform fusion processing on the OAM configuration information received by the at least two egress interfaces, and if the OAM configuration information received by the at least two egress interfaces is capable of being fused, configure an OAM attribute on the ingress interface of the root node according to the OAM configuration information after the fusion processing. The method for determining that the OAM configuration information received by the at least two egress interfaces can be merged according to the embodiment shown in fig. 2 of the present invention, which is not described herein again.
In another implementation manner of this embodiment, the multicast join packet includes, in addition to the OAM configuration information, other join attributes except for the OAM configuration information, and then the root node may perform a fusion process on the OAM configuration information and the other join attributes except for the OAM configuration information, and then configure the attribute of the root node according to a result of the fusion process.
In this embodiment, after configuring the OAM attribute of the root node according to the OAM configuration information, in order to enable the OAM attribute configured at the root node to dynamically track the change of the multicast tree topology, an association between the configured OAM attribute and the multicast tree state needs to be established. When the multicast state of the root node is deleted due to the change of the multicast tree topology, the OAM attributes configured to the input interface and the output interface of the root node are also deleted, and the residue of useless OAM attributes on the jointless nodes is avoided.
In the above embodiment, after receiving the multicast join packet, the root node of the multicast tree configures an OAM attribute of the root node according to OAM configuration information in the multicast join packet; therefore, automatic configuration of OAM attributes of nodes on the multicast tree is realized, workload of manual configuration is reduced, manual errors are avoided and reduced, and operability is good.
In the embodiments shown in fig. 1, fig. 2, and fig. 3 of the present invention, MEP _ I, MIP and MEP _ E are 3 types of OAM entities, and an OAM message is usually sent in MEP _ I, forwarded by MIP, and terminated in MEP _ E. Fig. 4 is a schematic diagram of a relationship between OAM entities of a multicast tree according to the present invention, and as shown in fig. 4, the multicast tree includes MEP _ I, MIP, MEP _ E, and Network Equipment (Network Equipment; hereinafter, referred to as NE).
The MEP _ I is used for sending an OAM message, for example, when packet loss is measured, the MEP _ I counts multicast data streams, writes a count value into a packet loss measurement message for packet loss detection, and sends the packet loss measurement message; and/or, during delay measurement, the MEP _ I may timestamp the delay measurement message for transmission;
the MEP _ E is used for terminating the OAM message, for example, when packet loss measurement is performed, the MEP _ E may count a data stream, obtain packet loss numbers from MEP _ I to MEP _ E, and calculate packet loss rates from MEP _ I to MEP _ E within a period of time; and/or, the MEP _ E can read a timestamp carried in the delay measurement message during delay measurement, record a local time value when the delay measurement message is received, and calculate the time delay from the MEP _ I to the MEP _ E;
the MIP is used for monitoring the OAM message and forwarding the OAM message to a downstream node or transparently transmitting the OAM message. For example, for packet loss measurement and delay measurement, the processing principle of MIP is the same as that of MEP _ E, but the packet loss rate and delay from MEP _ I to MIP are calculated.
MEP _ I, MIP and MEP _ E are both logical entities that may be located on the ingress and/or egress interfaces of the NE. The enabling and disabling of the OAM function of MEP _ I, MIP and MEP _ E may be configured through a Protocol Independent Multicast (PIM) Protocol. The advantage of expanding the PIM protocol is that complicated manual configuration can be avoided when nodes are more in the middle of the multicast tree, extra control layer burden can not be increased, the change of the multicast tree topology can be adapted, and the reliability of configuration can be ensured by utilizing the reliability processing mechanism of the PIM protocol.
The basic principle of the PIM protocol is: downstream nodes (including leaf nodes) of the multicast tree send PIM join messages or PIM prune messages hop by hop to upstream nodes (including root nodes). The upstream node can construct a multicast forwarding table entry of the downstream node according to the PIM adding message of the downstream node, and delete the multicast forwarding table entry through overtime or downstream pruning messages. And forming a multicast tree according to the connection of all nodes with multicast forwarding table items from the root node to the leaf nodes.
The embodiment of the present invention extends an original PIM join message, where the extended PIM join message is referred to as an extended PIM join message, and a multicast join message in the embodiments shown in fig. 1, fig. 2, and fig. 3 of the present invention may be an extended PIM join message, but the embodiment of the present invention is not limited thereto, and the multicast join message may also be a join message in any multicast routing protocol.
The embodiment of the invention defines new adding attributes in the extended PIM adding message and carries OAM configuration information to complete the configuration of the OAM attributes of the multicast tree or some forwarding branches on the multicast tree.
The extended PIM join packet may be sent periodically or as needed, and what sending method is used depends on the implementation manner of the PIM protocol itself and/or the configuration on the leaf node of the multicast tree, which is not limited in the embodiment of the present invention.
According to the characteristic that a PIM protocol establishes a multicast tree from bottom to top, an administrator can configure OAM configuration information which is to be implemented on a forwarding branch from a root node to a leaf node in the multicast tree, wherein the OAM configuration information can be used for monitoring the performance of all intermediate nodes between the root node and a certain leaf node; and configuring the OAM attribute of the leaf node according to the OAM configuration information. And then, carrying the OAM configuration information in an extended PIM adding message, and transmitting the extended PIM adding message carrying the OAM configuration information from the leaf node to the root node hop by hop, namely, the extended PIM adding message is transmitted from a downstream node to an upstream node in sequence and is stopped at the root node. Each hop node configures the OAM attribute of the hop node according to the OAM configuration information in the extended PIM adding message, and if the configuration of a certain node fails, configuration failure information can be fed back to a network manager or a downstream node.
When configuring the OAM attributes of the nodes of the multicast tree by the extended PIM protocol, different leaf nodes are usually required to configure the same OAM configuration information, specifically, an intermediate node having at least two outgoing interfaces, OAM configuration information in an extended PIM join message sent to an upstream node of the intermediate node is the same as OAM configuration information of a plurality of downstream nodes of the intermediate node, and at this time, the intermediate node only needs to transmit the OAM configuration information to the upstream node of the intermediate node through the extended PIM join message.
However, if different leaf nodes configure different OAM configuration information, then the OAM configuration information received by different egress interfaces of the intermediate node having at least two egress interfaces is different, and the intermediate node may configure different OAM attributes on the at least two egress interfaces according to the different OAM configuration information received by the at least two egress interfaces, then perform fusion processing on the different OAM configuration information received by the at least two egress interfaces, and then transmit the fused OAM configuration information to an upstream node of the intermediate node. For example, the downstream node 1 wants to configure the forwarding branch where the downstream node 1 is located to enable the packet loss measurement attribute, and configure the forwarding branch where the downstream node 1 is located to enable the delay measurement attribute, and also configure the forwarding branch where the downstream node 2 is located to enable the delay measurement attribute, and also configure the forwarding branch and the downstream node 2 to enable the ingress interface and the egress interface, so that after the intermediate node receives the OAM configuration information sent by the downstream node 1 and the downstream node 2, the intermediate node configures the egress interface corresponding to the downstream node 1 to enable the packet loss measurement attribute, configures the egress interface corresponding to the downstream node 2 to enable the delay measurement attribute, then performs fusion processing on the received OAM configuration information, and configures the ingress interface of the intermediate node to enable the packet loss measurement attribute and the delay measurement attribute according to the OAM configuration information after the fusion processing. In the embodiment of the present invention, if the extended PIM join packet is not spread to an unnecessary branch, the egress interface of the downstream node 2 may also be configured to be in a blocking state, so that the extended PIM join packet carrying OAM configuration information that is enabled by the ingress interface and the egress interface for the delay measurement attribute is sent from the ingress interface to the upstream node.
In the embodiment of the invention, OAM configuration information is carried in an extended PIM adding message and is sent to an upstream node hop by hop from a leaf node. And if the intermediate node receives different OAM configuration information sent by different downstream nodes, the extended PIM adding message sent by the intermediate node to the upstream node carries the configuration information of the OAM after the fusion processing. If the OAM configuration information of different downstream nodes of the intermediate node cannot be fused, the intermediate node gives up configuring the OAM attribute corresponding to the OAM configuration information which cannot be fused, and reports the failure of sending the relevant OAM configuration information to the downstream node or the network manager of the intermediate node. In order to reduce the processing load of the PIM protocol and avoid error generation, the same OAM configuration information may be configured on different leaf nodes as much as possible. The OAM configuration information of different downstream nodes of the intermediate node cannot be fused as follows: the OAM configuration information of different downstream nodes of the intermediate node is inconsistent, and the intermediate node cannot form the OAM configuration information which is consistent with the upstream node of the intermediate node according to the OAM configuration information of the different downstream nodes. For example, suppose that the downstream node 1 of the intermediate node wants to configure the forwarding branch where the downstream node 1 is located to enable the attribute of packet loss measurement, and configure the forwarding branch on which the downstream node 1 is located on the ingress interface and the egress interface, and the downstream node 2 of the intermediate node wants to configure the forwarding branch on which the downstream node 2 is located to be in a blocking state for packet loss measurement, and also configure the forwarding branch on the ingress interface and the egress interface, at this time, since the downstream node 1 wants to send the packet loss measurement packet from the ingress interface of the intermediate node to the egress interface connected to the downstream node 1, and the downstream node 2 wants to block the entry of the packet loss measurement packet from the ingress interface of the intermediate node, the OAM configuration information of the downstream node 1 and the downstream node 2 of the intermediate node cannot be fused at this time.
In the embodiment of the present invention, MEP _ E and MEP _ I may be respectively configured on a leaf node and a root node of a multicast tree, and MIP may be configured on an intermediate node between the leaf node and the root node of the multicast tree, so as to implement configuration of the entire multicast tree or one multicast forwarding branch. In this case, the OAM message is still inserted from MEP _ I to MEP _ E; the extended PIM adding message is still sent to the root node hop by hop from the leaf node, and the implementation of the embodiment of the invention is not influenced. If the extended PIM protocol supports the configuration of subtrees and partial forwarding branches, the extended PIM join message also needs to carry the interface addresses of the MEP _ I and the MEP _ E to be configured.
Depending on different application scenarios, the extended PIM join packet may carry different OAM configuration information, which may be, for example, MIP configuration, MIP enable, or MIP disable, taking the OAM configuration information of the intermediate node of the multicast tree as an example. Moreover, configuring the OAM attribute of the intermediate node may be performed selectively at an ingress interface and/or an egress interface of the intermediate node, and the supported OAM function may be packet loss measurement enable and/or delay measurement enable, or enable/disable of other types of OAM functions, which is not described herein again.
The above mainly takes the intermediate node as an example to introduce the configuration mode of the OAM attribute, and the mode of configuring the OAM attribute on the root node is similar to the mode of configuring the OAM attribute on the intermediate node, and is not described herein again.
The format of the extended PIM join message carrying the OAM configuration information may adopt the format of the PIM join message, but a new attribute field needs to be defined. FIG. 5 is a diagram illustrating an embodiment of an encoded source address format for adding attributes according to the present invention. The fields in fig. 5 are described below.
The address family: internet Protocol version 4(Internet Protocol version 4; hereinafter, abbreviated as IPv4) or Internet Protocol version 6(Internet Protocol version 6; hereinafter, abbreviated as IPv 6);
the coding type is as follows: setting to be 1, representing carrying the join attribute;
s bit: when the value is set to 1, the protocol supports a Sparse Mode independent Multicast protocol (PIM-SM);
w bit: PIM join message or PIM prune message to use to mark the bit of the source group or sharing group;
r bits: set to 1 when the W bit is set to 1;
mask length: the mask length of the source subnet;
source address: a multicast source address;
f bits: transition attribute bit, which indicates that the node does not support the processing of the attribute, and when the bit is set to 1, the bit indicates that the message is continuously forwarded to the upstream node, and when the bit is set to 0, the bit indicates that the message needs to be discarded;
e bit: attribute end bit, which indicates that the attribute is the last attribute field carried by the encoding source address;
the attribute types are: the type of the attribute;
length: the length of the value field;
the value: the value range of the attribute.
A new attribute type needs to be defined for the extended PIM join packet, fig. 6 is a schematic diagram of an embodiment of an OAM join attribute format of the present invention, and in fig. 6, F, E and the definition of the length field are as described above; other fields are described below.
OAM attribute type: defining a new value, and distributing The value by an Internet Assigned Numbers Authority (IANA), wherein The attribute is an attribute for OAM configuration parameters;
version number: OAM version number;
ME _ ID: an identifier identifying the maintenance group to which MEP _ I, MIP and MEP _ E belong, being unique within a maintenance management domain;
MIP configuration Type Length Value (Type Length Value; hereinafter, TLV), MEP _ I configuration TLV, and MEP _ E configuration TLV: configuring contents by adopting a length-type-value structure; for example: the type may be defined as:
0X 01: MIP configuration TLV;
0X 02: MEP _ I configuration TLV;
0X 03: MEP _ E configures TLV.
Fig. 7 is a diagram illustrating an embodiment of the format of the MIP configuration TLV of the present invention, and the meaning of the fields in fig. 7 is as follows:
type (2): 01;
length: length of the value range field starting after the length field;
a mark field: each bit indicates which OAM function is configured, e.g.: l may be defined as a packet loss measurement and D may be defined as a delay measurement, each OAM function being fixed in position in the flag field;
the function configuration type is as follows: can be defined as config MIP (0 × 01), de-config MIP (0 × 02), MIP enable (0 × 03), MIP de-enable (0 × 04), MIP block (0 × 05), config + enable MIP (0 × 06), config + de-enable MIP (0 × 07), and config + block MIP (0 × 08), and so on;
function configuration position: support at the ingress interface (0 x 01), support at the egress interface (0 x 02), and support at both the ingress and egress interfaces (0 x 03), and so on.
Fig. 8 is a diagram illustrating an embodiment of a format of MEP _ I configuration TLV according to the present invention, where the meaning of each field in fig. 8 is as follows:
type (2): 0X 02;
length: length of the value range field starting after the length field;
a mark field: each bit indicates which OAM function is configured, e.g.: l may be defined as a packet loss measurement and D may be defined as a delay measurement, each OAM function being fixed in position in the flag field;
configuring an interface address: the node is used during non-integral tree and non-integral path configuration, after receiving an extended PIM adding message, the node judges whether an interface address is the address of the node, if so, the node is configured, and the OAM message is stopped from being continuously transmitted upstream;
function configuration position: the function is configured at the input interface (0 x 01) or the output interface (0 x 02) of the node;
the function configuration type is as follows: configuration (0 × 01), enable (0 × 02), deconfigure (0 × 03), disable (0 × 04), configure + enable (0 × 06), configure + disable (0 × 07), and carry only configuration parameters (0 × 08), etc.; when the value is 0 × 06, assuming that MEP _ I is already enabled, only the configuration parameters are transferred to MEP _ I;
the functional operation type is as follows: configuring periodically transmitted (0 × 01) or transmitted (0 × 02) OAM configuration information as needed; this field is used by MEP _ I;
and a function OAM message sending period: the unit is millisecond, the sending period when the OAM message period is sent is used by MEP _ I, and is invalid when the sending period is set to be 0 Xffffffff.
The method comprises the following steps of (1) sending a function OAM message at a starting time and a sending ending time: the period of sending the OAM message is determined, and when the period is set to be 0 Xffffffff, the period is invalid, and a Network Time Protocol (NTP) time scale can be used and used by MEP _ I.
Fig. 9 is a diagram illustrating an embodiment of a format of the MEP _ E configuration TLV of the present invention, where the meaning of the fields in fig. 9 is as follows:
type (2): 0X 03;
length: length of the value range field starting after the length field;
a mark field: each bit indicates which OAM function is configured, e.g.: l may be defined as a packet loss measurement and D may be defined as a delay measurement, each OAM function being fixed in position in the flag field;
configuring an interface address: the MEP _ E is only used when configured on a non-leaf node, is not set under the default condition, and adopts a root node as a bearing node of the MEP _ E; after receiving the extended PIM adding message, the MEP _ E judges whether the interface address is the address of the node, if so, the MEP _ E of the node is configured, and the extended PIM adding message carrying OAM configuration information is continuously transmitted to an upstream node.
Function configuration position: an ingress interface (0 × 01) or an egress interface (0 × 02) on a leaf node;
the function configuration type is as follows: configuration (0 × 01), deconfiguration (0 × 02), enable (0 × 03), disable (0 × 04), configuration + enable (0 × 06), configuration + disable (0 × 07), and the like.
In this embodiment of the present invention, the extended PIM protocol further supports processing of other PIM join attributes except the OAM configuration information, for example, the other PIM join attributes except the OAM configuration information may include: a topology identification attribute and/or a reverse forwarding path vector attribute that identifies multi-topology information. The transmission of multi-topology information can be realized by identifying the topology identification attribute of the multi-topology information, and the setting and transmission of the reverse forwarding path vector on the boundary equipment can be realized by the reverse forwarding path vector attribute. The topology identification attribute for identifying multi-topology information is used for constructing different virtual topologies in the same physical network, and the reverse forwarding path vector attribute is used for establishing a multicast tree between two boundary network devices.
When the OAM configuration information and the two attributes are included in the same extended PIM join message at the same time, the intermediate node or the root node needs to perform fusion processing on the attributes. For example, when a topology identification attribute identifying multi-topology information and OAM configuration information exist in an extended PIM join message at the same time, an intermediate node or root node may perform OAM configuration on the nodes in the identified virtual topology to enable or disable the OAM functions of the virtual topology multicast tree and multicast forwarding branches. For another example, when the reverse forwarding path vector attribute and OAM configuration information are both present in an extended PIM join message, an intermediate node or root node may perform OAM configuration on a core network node between two edge devices to enable or disable the OAM function of the core network node.
If the same node receives different attribute messages from different downstream interfaces, for example: the node receives OAM configuration information at an interface 1 and receives multi-topology join attributes and the like at an interface 2, the node needs to judge whether the attributes are fused, and if the attributes cannot be fused, different join attributes need to be processed respectively. If different adding attributes cause contradiction or error operation, the node does not process the adding attributes and reports error to a downstream node or a network manager.
If part of nodes on the configuration path do not support the OAM function, the node sending the extended PIM adding message can set the F bit in the extended PIM adding message, namely the value of the F bit is set to be 1, after the node which does not support the OAM configuration information receives the extended PIM adding message with the set F bit, the OAM attribute of the node is not configured, and the extended PIM adding message is continuously transmitted to an upstream node.
In this embodiment of the present invention, a multicast tree neighbor node may perform OAM configuration capability negotiation by expanding a Hello packet and carrying a new Hello option, fig. 10 is a schematic diagram of an embodiment of a format of an OAM configuration option in the Hello packet, and the meaning of each field in fig. 10 is as follows:
the option types are: defining a value different from other defined PIM Hello options, for example, the value is 39;
option length: length of the option value field;
option values: for example, the value 01 is a normal OAM configuration, and other values are not defined yet.
In the embodiment of the invention, the neighbor nodes of the multicast tree can determine whether the neighbor nodes have the capability of OAM configuration by using PIM protocol through transmitting the Hello message.
The embodiment of the invention provides a configuration method for operation management and maintenance, which completes automatic configuration of nodes on a multicast tree by expanding a PIM protocol and carrying OAM configuration information in an expanded PIM joining message, and has the following advantages:
(1) the configuration nodes are few, the PIM protocol is used for automatically completing the configuration, the operability is good, the workload of manual configuration is reduced, and the manual errors are avoided and reduced;
(2) the existing PIM protocol is expanded, and the OAM configuration information is carried by the PIM adding message through expansion, so that the burden of a control layer is not increased, and the expandability is good;
(3) the PIM protocol design itself implements a reliable transport mechanism for the messages, such as: the OAM attribute configuration is realized by means of periodical refreshing or Transmission Control Protocol (TCP) bearing and the like, so that the method has natural advantages;
(4) the OAM configuration can automatically track the change of the multicast topology, and has larger flexibility.
The configuration method for operation management and maintenance provided by the embodiment of the invention is not only suitable for the PIM (PIM-Sparse Mode; PIM-SM) in the Sparse Mode and the PIM-source specific Multicast (PIM-SSM) in the PIM, but also suitable for other protocols of the PIM protocol family, such as the two-way PIM protocol and the like.
The configuration method for operation management and maintenance provided by the embodiment of the invention can be used for an IPv4 multicast network and can also be used for an IPv6 multicast network. In the IPv6 multicast network, a multicast routing protocol in the IPv6 network may be adopted to complete configuration of OAM attributes of nodes of the IPv6 multicast tree.
In addition, the configuration method for operation management and maintenance provided in the embodiment of the present invention may also be used in a Multi-Protocol Label Switching Point-to-Multi-Point (hereinafter, referred to as MPLS P2MP) network, and at this time, a multicast routing Protocol in an MPLS P2MP network may be used to complete configuration of OAM attributes of nodes of an MPLS P2MP multicast tree.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Fig. 11 is a schematic structural diagram of an embodiment of a leaf node of a multicast tree according to the present invention, where the leaf node in this embodiment may implement the flow of the embodiment shown in fig. 1 of the present invention, and as shown in fig. 11, the leaf node may include: a node attribute configuration module 1101 and a message sending module 1102;
the node attribute configuration module 1101 is configured to configure an OAM attribute of the leaf node according to the OAM configuration information configured on the leaf node; specifically, the node attribute configuration module 1101 may configure an OAM attribute on an ingress interface and/or an egress interface of the leaf node according to the OAM configuration information; for example: the ingress and/or egress interface of the leaf node may be configured as MEP _ E enabled, or MEP _ E disabled, the OAM attribute may be configured on the egress interface of the leaf node, and the supported function may be packet loss measurement enabled, delay measurement enabled, or other types of OAM functions.
A message sending module 1102, configured to send a multicast join message to an upstream node of the leaf node, where the multicast join message includes the OAM configuration information; specifically, the message sending module 1102 may send the multicast join message to an upstream node of the leaf node periodically or on demand.
In addition, in an implementation manner of this embodiment, the intermediate node may further include: a setup module 1103 and/or a delete module 1104;
the setting module 1103 is configured to set a timer; at this time, the node attribute configuration module 1101 may further reconfigure the OAM attribute of the leaf node according to the updated OAM configuration information if the updated OAM configuration information is obtained within the valid time of the timer set by the setting module 1103.
A deleting module 1104, configured to delete the configured OAM attribute of the leaf node if the updated OAM configuration information is not obtained after the timer set by the setting module 1103 expires.
In the leaf node of the multicast tree, the node attribute configuration module 1101 configures the OAM attribute of the leaf node according to the OAM configuration information, and the message sending module 1102 sends a multicast join message carrying the OAM configuration information to the upstream node of the leaf node, so that the upstream node of the leaf node configures the OAM attribute of itself according to the OAM configuration information, thereby implementing automatic configuration of the OAM attribute of the node on the multicast tree, reducing the workload of manual configuration, avoiding and reducing manual errors, and having good operability.
Fig. 12 is a schematic structural diagram of an embodiment of an intermediate node of a multicast tree according to the present invention, where the intermediate node in this embodiment may implement the flow of the embodiment shown in fig. 2 of the present invention, and as shown in fig. 12, the intermediate node may include: a receiving module 1201, a configuration module 1202 and a sending module 1203;
the receiving module 1201 is configured to receive a multicast join packet sent by a downstream node of the intermediate node, where the multicast join packet includes OAM configuration information, and the downstream node of the intermediate node includes a leaf node and/or an upstream node of the leaf node;
a configuration module 1202, configured to configure an OAM attribute of the intermediate node according to the OAM configuration information; specifically, the configuration module 1202 may configure OAM attributes on an ingress interface and/or an egress interface of the intermediate node according to the OAM configuration information, for example: MIP enable or MIP disable may be configured on an ingress interface and/or an egress interface of the intermediate node; the OAM attributes may be configured on an ingress interface and/or an egress interface of the intermediate node, and the supported functions may be packet loss measurement enable, delay measurement enable, or other types of OAM functions;
a sending module 1203, configured to send the multicast join packet to an upstream node of the intermediate node, so that the upstream node of the intermediate node configures its own OAM attribute according to the OAM configuration information in the multicast join packet, and sends the multicast join packet until the multicast join packet is sent to a root node of a multicast tree hop by hop; specifically, the sending module 1203 may send the multicast join packet periodically or on demand to an upstream node of the intermediate node.
In an intermediate node of the multicast tree, after the receiving module 1201 receives a multicast join message sent by a downstream node of the intermediate node, the configuration module 1202 configures an OAM attribute of the intermediate node according to OAM configuration information in the multicast join message, and the sending module 1203 sends the multicast join message to an upstream node of the intermediate node; therefore, automatic configuration of OAM attributes of nodes on the multicast tree is realized, workload of manual configuration is reduced, manual errors are avoided and reduced, and operability is good.
Fig. 13 is a schematic structural diagram of another embodiment of an intermediate node of a multicast tree according to the present invention, and compared with the intermediate node of the multicast tree shown in fig. 12, the difference is that, in the intermediate node of the multicast tree shown in fig. 13, the configuration module 1202 may include: a fusion processing submodule 12021 and an attribute configuration submodule 12022;
the attribute configuration submodule 12022 is configured to, when the intermediate node includes one ingress interface and at least two egress interfaces, and OAM configuration information received by the at least two egress interfaces is different, configure different OAM attributes on the at least two egress interfaces according to OAM configuration information received by the at least two egress interfaces;
the fusion processing submodule 12021 is configured to perform fusion processing on the OAM configuration information received by the at least two egress interfaces; in this case, when the OAM configuration information received by at least two outgoing interfaces can be merged, the attribute configuration submodule 12022 may further configure an OAM attribute on the incoming interface of the intermediate node according to the OAM configuration information merged by the merging processing submodule 12021.
At this time, the sending module 1203 is specifically configured to send a multicast join packet including the OAM configuration information after the merging processing by the merging processing sub-module 12021 to the upstream node of the intermediate node.
In this embodiment, the convergence processing sub-module 12021 may further perform convergence processing on the OAM configuration information and the other PIM join attributes except the OAM configuration information when the multicast join packet further includes the other PIM join attributes except the OAM configuration information; at this time, the attribute configuration submodule 12022 may also configure the attribute of the intermediate node according to the result of the fusion processing by the fusion processing submodule 12021.
In this embodiment, the intermediate node may further include: a timer setting module 1204 and/or an attribute deletion module 1205;
the timer setting module 1204 is configured to set a timer; at this time, the configuration module 1202 may also reconfigure the OAM attribute of the intermediate node according to the updated OAM configuration information if the updated OAM configuration information is received within the validity time of the timer set by the timer setting module 1204.
An attribute deleting module 1205, configured to delete the OAM attribute configured by the intermediate node if the updated OAM configuration information is not received after the timer set by the timer setting module 1204 expires.
The intermediate node of the multicast tree realizes automatic configuration of the OAM attribute of the nodes on the multicast tree, reduces the workload of manual configuration, avoids and reduces human errors, and has good operability.
Fig. 14 is a schematic structural diagram of an embodiment of a root node of a multicast tree according to the present invention, where the root node in this embodiment may implement the flow of the embodiment shown in fig. 3 of the present invention, and as shown in fig. 14, the root node of the multicast tree may include: a message receiving module 1401 and an attribute configuration module 1402;
the message receiving module 1401 is configured to receive a multicast join message sent by a downstream node of a root node, where the multicast join message includes OAM configuration information;
an attribute configuration module 1402, configured to configure the OAM attribute of the root node according to the OAM configuration information; specifically, the attribute configuration module 1402 may configure an OAM attribute on an ingress interface and/or an egress interface of the root node according to the OAM configuration information; for example: MEP _ I enable or MEP _ I disable may be configured on an ingress interface and/or an egress interface of the root node; the OAM attributes may be configured on the ingress interface and/or at the root node, and the supported functions may be packet loss measurement enable, delay measurement enable, or other types of OAM functions.
In an implementation manner of this embodiment, the attribute configuration module 1402 may include: a configuration submodule 14021 and a processing submodule 14022;
the configuration submodule 14021 is configured to, when the root node includes one ingress interface and at least two egress interfaces, and OAM configuration information received by the at least two egress interfaces is different, respectively configure different OAM attributes on the at least two egress interfaces according to OAM configuration information received by the at least two egress interfaces;
the processing submodule 14022 is configured to perform fusion processing on the OAM configuration information received by the at least two egress interfaces; in this case, when the OAM configuration information received by the at least two outgoing interfaces is able to be merged, the configuration submodule 14021 may further configure an OAM attribute on the incoming interface of the root node according to the OAM configuration information merged by the processing submodule 14022.
In this embodiment, the processing sub-module 14022 may further perform fusion processing on the OAM configuration information and the other PIM addition attributes except the OAM configuration information when the multicast addition packet further includes the other PIM addition attributes except the OAM configuration information; at this time, the configuration submodule 14021 may also configure the attribute of the root node according to the result of the fusion processing by the processing submodule 14022.
In another implementation manner of this embodiment, the root node may further include: a node timer setting module 1403 and/or a node attribute deletion module 1404;
a node timer setting module 1403, configured to set a timer; at this time, the attribute configuration module 1402 may further reconfigure the OAM attribute of the root node according to the updated OAM configuration information if the updated OAM configuration information is received within the valid time of the timer set by the node timer setting module 1403.
A node attribute deleting module 1404, configured to, after the timer set by the node timer setting module 1403 expires, delete the configured OAM attribute of the root node if updated OAM configuration information is not received.
In the root node of the multicast tree, after the message receiving module 1401 receives the multicast join message, the attribute configuration module 1402 configures the OAM attribute of the root node according to the OAM configuration information in the multicast join message; therefore, automatic configuration of OAM attributes of nodes on the multicast tree is realized, workload of manual configuration is reduced, manual errors are avoided and reduced, and operability is good.
Fig. 15 is a schematic structural diagram of an embodiment of an operation management and maintenance configuration system of the present invention, and as shown in fig. 15, the operation management and maintenance configuration system may include: a leaf node 1501, an intermediate node 1502, and a root node 1503 of the multicast tree;
the leaf node 1501 is configured to configure an OAM attribute of the leaf node 1501 according to OAM configuration information configured on the leaf node, and send a multicast join packet to an upstream node of the leaf node, where the multicast join packet includes the OAM configuration information; specifically, the leaf node 1501 may be implemented by a leaf node of the multicast tree shown in fig. 11 of the present invention;
the intermediate node 1502 is configured to receive a multicast join packet sent by a downstream node of the intermediate node 1502, and configure an OAM attribute of the intermediate node 1502 according to the OAM configuration information; sending the multicast join message to an upstream node of the intermediate node 1502, so that the upstream node of the intermediate node 1502 configures its own OAM attribute according to the OAM configuration information in the multicast join message, and sending the multicast join message until the multicast join message is sent to a root node 1503 of a multicast tree hop by hop; specifically, the intermediate node 1502 may be implemented by an intermediate node of the multicast tree shown in fig. 12 or fig. 13 of the present invention; wherein, the downstream node of the intermediate node 1502 includes the leaf node 1501 and/or the upstream node of the leaf node 1501;
a root node 1503, configured to receive a multicast join packet sent by a downstream node of the root node 1503, and configure an OAM attribute of the root node 1503 according to the OAM configuration information; specifically, the root node 1503 may be implemented by the root node of the multicast tree shown in fig. 14 of the present invention.
The configuration system for operation management and maintenance provided in this embodiment logically forms a multicast tree, and for a multicast tree established by different protocols of a PIM protocol family, a root node, an intermediate node, and a leaf node of the multicast tree correspond to different devices.
For example: for the multicast tree established by PIM-SSM, the root node of the multicast tree may be a source-Designated Router (DR) connected to the multicast source, the leaf nodes of the multicast tree may be receivers DR connected to the receivers, and the intermediate nodes may be routers between the source DR and the receivers DR.
For a multicast tree built by PIM-SM, the multicast tree includes three states: a shared tree state, a shared tree and source tree coexistence state, and a source tree state. In these three states, when a receiver wishes to join a multicast group, a shared tree is established from the receiver DR to a Rendezvous Point (RP); when the multicast traffic reaches the RP of the multicast tree at the same time, establishing a source tree from the RP to the source DR at the same time; a source tree is established from the recipient DR to the source DR when traffic to the recipient exceeds a predetermined threshold. In the shared tree state, the root node of the multicast tree may be the RP, the leaf nodes may be the receivers DR, and the intermediate nodes may be routers between the RP and the receivers DR. In the coexistence state of the shared tree and the source tree, the multicast tree is divided into two sections, wherein the first section is the shared tree and the second section is the source tree; the root node of the first segment of the shared tree is an RP, the leaf nodes are receivers DR, and the middle nodes are routers between the RP and the receivers DR; the root node of the second section of the source tree is a source DR, the leaf nodes are RPs, and the middle node is a router between the source DR and the RP. In the source tree state, the root node of the multicast tree is a source DR, the leaf nodes are receivers DR, and the intermediate nodes are routers between the source DR and the receivers DR.
For a multicast tree established through PIM-SSM, a multicast tree of a source tree state or a shared tree state established through PIM-SM, a multicast adding message is transmitted hop by hop from a leaf node to a root node, and the configuration of the multicast tree is completed; for the multicast tree of the coexistence state of the shared tree and the source tree established by PIM-SM, the multicast join message is transmitted from a receiver DR to an RP hop by hop in the shared tree and transmitted from the RP to the source DR hop by hop in the source tree, and the configuration of the source tree and the shared tree is respectively completed.
In the configuration system for operation administration and maintenance, after a leaf node 1501 of a multicast tree configures an OAM attribute of the leaf node according to OAM configuration information, a multicast join packet carrying the OAM configuration information is sent to an upstream node of the leaf node 1501; after receiving a multicast join message sent by a downstream node of the intermediate node 1502, the intermediate node 1502 of the multicast tree configures an OAM attribute of the intermediate node 1502 according to OAM configuration information in the multicast join message, and then sends the multicast join message to an upstream node of the intermediate node 1502; after receiving the multicast join message, the root node 1503 of the multicast tree configures the OAM attribute of the root node 1503 according to the OAM configuration information in the multicast join message; therefore, automatic configuration of OAM attributes of nodes on the multicast tree is realized, workload of manual configuration is reduced, manual errors are avoided and reduced, and operability is good.
The multicast join message in the embodiments shown in fig. 11 to fig. 15 of the present invention may be an extended PIM join message, although the embodiment of the present invention is not limited thereto, and the multicast join message may also be a join message in any multicast routing protocol, which is not limited in this embodiment of the present invention, but the embodiment of the present invention is described by taking the multicast join message as an extended PIM join message as an example.
Those skilled in the art will appreciate that the drawings are merely schematic representations of one preferred embodiment and that the blocks or flow diagrams in the drawings are not necessarily required to practice the present invention.
Those skilled in the art will appreciate that the modules in the devices in the embodiments may be distributed in the devices in the embodiments according to the description of the embodiments, and may be correspondingly changed in one or more devices different from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (6)
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010213835.7A CN102299815B (en) | 2010-06-22 | 2010-06-22 | Configuration method and node of OAM (operation, administration and maintenance) |
| PCT/CN2011/073729 WO2011160498A1 (en) | 2010-06-22 | 2011-05-06 | Configuration method and node for operation administration and maintenace |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010213835.7A CN102299815B (en) | 2010-06-22 | 2010-06-22 | Configuration method and node of OAM (operation, administration and maintenance) |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102299815A CN102299815A (en) | 2011-12-28 |
| CN102299815B true CN102299815B (en) | 2014-04-30 |
Family
ID=45360002
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010213835.7A Expired - Fee Related CN102299815B (en) | 2010-06-22 | 2010-06-22 | Configuration method and node of OAM (operation, administration and maintenance) |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102299815B (en) |
| WO (1) | WO2011160498A1 (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102739448A (en) * | 2012-06-28 | 2012-10-17 | 华为技术有限公司 | Method, device and system for transmitting messages |
| CN102868569B (en) | 2012-06-30 | 2015-12-09 | 华为技术有限公司 | The method for testing performance of Layer3 Virtual Private Network, node and system |
| US9571364B2 (en) * | 2012-07-13 | 2017-02-14 | Telefonaktiebolaget L M Ericsson (Publ) | Connectivity fault management in a communication network |
| CN103152205B (en) * | 2013-03-22 | 2016-02-10 | 烽火通信科技股份有限公司 | Based on OAM processing method and the device of stream index |
| CN104348678B (en) * | 2013-08-05 | 2018-10-30 | 华为技术有限公司 | Ethernet performance measurement method, apparatus and system |
| CN103475588A (en) * | 2013-09-10 | 2013-12-25 | 神州数码网络(北京)有限公司 | Sending process method and device and receiving process method and device of OAM messages |
| CN104734876A (en) * | 2013-12-24 | 2015-06-24 | 中兴通讯股份有限公司 | Ethernet OAM configuration achieving method and device |
| CN105323096B (en) * | 2014-07-30 | 2018-11-23 | 中国移动通信集团公司 | A kind of the O&M method and operational system of network function |
| CN105656705A (en) * | 2014-11-12 | 2016-06-08 | 中兴通讯股份有限公司 | Method and device for detecting multicast function of access equipment |
| CN105827529B (en) | 2016-05-10 | 2019-02-26 | 华为技术有限公司 | A path establishment method and controller |
| CN108536447B (en) * | 2018-04-11 | 2021-07-16 | 上海掌门科技有限公司 | Operation and maintenance management method |
| US12301404B2 (en) | 2022-12-13 | 2025-05-13 | Cisco Technology, Inc. | In-situ operations, administration, and maintenance extension to trace multicast tree and identify failure node |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101102253A (en) * | 2007-08-13 | 2008-01-09 | 杭州华三通信技术有限公司 | Method, branch node and center node for transmitting multicast in IPsec tunnel |
| CN101212326A (en) * | 2006-12-29 | 2008-07-02 | 上海贝尔阿尔卡特股份有限公司 | Method for configuring nodes in any multicast group and auxiliary method and device |
| CN101651552A (en) * | 2009-09-09 | 2010-02-17 | 华为技术有限公司 | Node configuration method and network equipment |
-
2010
- 2010-06-22 CN CN201010213835.7A patent/CN102299815B/en not_active Expired - Fee Related
-
2011
- 2011-05-06 WO PCT/CN2011/073729 patent/WO2011160498A1/en not_active Ceased
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101212326A (en) * | 2006-12-29 | 2008-07-02 | 上海贝尔阿尔卡特股份有限公司 | Method for configuring nodes in any multicast group and auxiliary method and device |
| CN101102253A (en) * | 2007-08-13 | 2008-01-09 | 杭州华三通信技术有限公司 | Method, branch node and center node for transmitting multicast in IPsec tunnel |
| CN101651552A (en) * | 2009-09-09 | 2010-02-17 | 华为技术有限公司 | Node configuration method and network equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102299815A (en) | 2011-12-28 |
| WO2011160498A1 (en) | 2011-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102299815B (en) | Configuration method and node of OAM (operation, administration and maintenance) | |
| US10862783B2 (en) | OAM mechanisms for EVPN active-active services | |
| CN101356778B (en) | Network system and data transfer device | |
| CN102316016B (en) | Method and device for forwarding multicasting flow | |
| US8009671B2 (en) | Multicast method and multicast routing method | |
| CN106470162B (en) | A kind of method of multicasting and device of service message | |
| WO2007090346A1 (en) | Control system, data message transmission method and network device in the ethernet | |
| CN109150580B (en) | Protocol Independent Multicast Join Entropy | |
| CN101577679A (en) | Configuration management method for realizing multicast service sharing among appointed routers and appliance thereof | |
| US11716273B2 (en) | On-path telemetry for multicast traffic | |
| JPWO2006092915A1 (en) | Packet ring network system, connection method between packet rings, and inter-ring connection node | |
| WO2017036180A1 (en) | Packet processing method and device | |
| WO2010111956A1 (en) | Method and system for multicast-forwarding-path convergence | |
| WO2022121638A1 (en) | Packet processing method and device | |
| CN110115011B (en) | Multicast service processing method and access device | |
| US9537672B2 (en) | Method for managing customer edge device automatically and PE device | |
| CN100574247C (en) | Ethernet tunnel processing method, communication system and related equipment | |
| CN102739504B (en) | Method for switching multicast path and router | |
| WO2016131359A1 (en) | Multicast line switching method and device for ring-shaped network | |
| CN102244602B (en) | Method, device and system for forwarding data under protocol independent multicast dual join | |
| CN114531392B (en) | Multicast service design method, server and storage medium | |
| WO2013037319A1 (en) | Bandwidth resource management method, device and system for label switched path | |
| WO2022088931A1 (en) | Information processing method and apparatus, broadband access server, and storage medium | |
| US20250337609A1 (en) | Multicast for multifabric virtualized networks | |
| US12132643B1 (en) | Multicast datapath tracing in layer-2 networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140430 Termination date: 20190622 |