CN108933696B - OAM configuration negotiation method, device, management entity and storage medium - Google Patents
OAM configuration negotiation method, device, management entity and storage medium Download PDFInfo
- Publication number
- CN108933696B CN108933696B CN201810681363.4A CN201810681363A CN108933696B CN 108933696 B CN108933696 B CN 108933696B CN 201810681363 A CN201810681363 A CN 201810681363A CN 108933696 B CN108933696 B CN 108933696B
- Authority
- CN
- China
- Prior art keywords
- management entity
- oam
- negotiation
- message
- oam configuration
- 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.)
- Active
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
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
-
- 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/0889—Techniques to speed-up the configuration process
-
- 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/0893—Assignment of logical groups to network elements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention discloses an OAM configuration negotiation method, a device, a management entity and a storage medium. The method comprises the following steps: receiving an OAM configuration item of a current stage of a first management entity, which is sent by the first management entity; according to a predetermined operation, management and maintenance (OAM) configuration item negotiation stage, determining that the OAM configuration item of the current stage of the first management entity is matched with the OAM configuration item of the current stage of the second management entity, and returning an OAM configuration item negotiation passing message of the current stage to the first management entity; and receiving the OAM configuration item of the next stage of the first management entity sent by the first management entity until the OAM configuration item negotiation of all negotiation stages is completed. The present embodiment enables negotiation of OAM configuration items.
Description
Technical Field
The present invention relates to communications technologies, and in particular, to an OAM configuration negotiation method, apparatus, management entity, and storage medium.
Background
Operation, Administration and Maintenance (OAM) supervises network Operation and improves network service quality through many ways, and currently, there are mainly more perfect OAM mechanisms including connection-oriented packet switching network technology (MPLS-TP) OAM. MPLS-TP OAM is the hierarchical management control of MPLS-TP on the original OAM, such as segment layer, tunnel layer, pseudo wire layer, service layer and access link layer, and the MPLS-TP OAM respectively carries out hierarchical OAM aiming at the layers.
In the MPLS-TP OAM detection scheme, two Management Entities (MEs) in the OAM constitute a section to be detected by the OAM, and two MEs need to configure mutually matched OAM configuration items to perform OAM detection by receiving and sending an OAM message.
At present, the OAM configuration items are more and the configuration process is tedious, so that the OAM configuration items in two MEs are probably not matched, generally, the unmatched configuration items are checked manually in the prior art, and the operation is tedious and the labor cost is high.
Disclosure of Invention
The embodiment of the invention provides an OAM configuration negotiation method, a device, a management entity and a storage medium, which are used for realizing the negotiation of an OAM configuration item.
In a first aspect, an embodiment of the present invention provides a method for OAM configuration negotiation, including:
receiving an OAM configuration item of a current stage of a first management entity, which is sent by the first management entity;
according to a predetermined operation, management and maintenance (OAM) configuration item negotiation stage, determining that the OAM configuration item of the current stage of the first management entity is matched with the OAM configuration item of the current stage of the second management entity, and returning an OAM configuration item negotiation passing message of the current stage to the first management entity;
and receiving the OAM configuration item of the next stage of the first management entity sent by the first management entity until the OAM configuration item negotiation of all negotiation stages is completed.
In a second aspect, an embodiment of the present invention further provides an OAM configuration negotiation apparatus, including:
a receiving module, configured to receive an OAM configuration item of a current stage of a first management entity sent by the first management entity; receiving the OAM configuration items of the next stage of the first management entity sent by the first management entity until the OAM configuration items of all negotiation stages are negotiated;
and the sending module is used for determining that the OAM configuration item of the current stage of the first management entity is matched with the OAM configuration item of the current stage of the second management entity according to the predetermined negotiation stage of the operation, administration and maintenance OAM configuration item, and returning an OAM configuration item negotiation passing message of the current stage to the first management entity.
In a third aspect, an embodiment of the present invention further provides a management entity, including:
one or more processors;
a memory for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement the OAM configuration negotiation method of any of the embodiments.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the OAM configuration negotiation method according to any one of the embodiments.
In the technical scheme of this embodiment, by receiving the OAM configuration item in the current stage of the first management entity sent by the first management entity, that is, the management entity may send the OAM configuration item to the opposite end in stages, so that the opposite end performs comparison negotiation; according to a predetermined operation, management and maintenance (OAM) configuration item negotiation stage, determining that an OAM configuration item of a current stage of a first management entity is matched with an OAM configuration item of a current stage of a second management entity, and returning an OAM configuration item negotiation passing message of the current stage to the first management entity; then, receiving the OAM configuration items of the next stage of the first management entity sent by the first management entity until the OAM configuration items of all negotiation stages are negotiated, thereby determining that the OAM configuration items in the two management entities are matched with each other in a staged negotiation manner and avoiding OAM configuration errors; the OAM configuration inspection efficiency is improved without manual inspection, and the OAM can be rapidly deployed in the network.
Drawings
Fig. 1 is a flowchart of an OAM configuration negotiation method according to an embodiment of the present invention;
fig. 2 is a flowchart of an OAM configuration negotiation method according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of an OAM configuration negotiation apparatus according to a fifth embodiment of the present invention;
fig. 4 is a schematic structural diagram of a management entity according to a sixth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a flowchart of an OAM configuration negotiation method according to an embodiment of the present invention, where this embodiment is applicable to a situation where after OAM configuration is completed in two management entities, an OAM configuration item is negotiated and compared. For convenience of description, the present embodiment describes in detail a process of OAM configuration negotiation with a second management entity as an execution subject, and specifically includes the following steps:
and S110, receiving the OAM configuration item of the current stage of the first management entity, which is sent by the first management entity.
At least one OAM configuration entry may be created within either the first management entity or the second management entity. The first management entity and the second management entity need to configure matched OAM configuration items, and then OAM detection can be carried out by receiving and transmitting OAM messages. The OAM configuration item includes, but is not limited to, a management Entity Group identifier (mesh Entity Group ID), a detection object type, an End Point identifier (mesh Entity Group End Point ID) of the management Entity Group, an OAM message level, an OAM message sending period, and the like. The detection object type includes a Label Switch Path (LSP) layer, a segment layer (Section), and a pseudowire layer (Pseudo Wire).
In this embodiment, the negotiation phase of the OAM configuration item is predetermined. The negotiation stage includes a first stage, a second stage, a third stage, etc., and the negotiation of the next stage is performed after the OAM configuration item negotiation of the current stage passes. The same phase may include at least one OAM configuration entry. Preferably, in order to improve the efficiency and accuracy of negotiation, the OAM configuration item capable of uniquely identifying the OAM instance is classified into the first stage, and the other configuration items are classified into stages subsequent to the first stage.
For example, the MegID and the detection object type can uniquely identify the OAM instance, the MegID and the detection object type are classified into a first stage, and after the OAM instance is matched, the MepID, the OAM message level and the OAM message sending period are further negotiated.
S120, according to the predetermined operation, management and maintenance OAM configuration item negotiation stage, determining that the OAM configuration item of the current stage of the first management entity is matched with the OAM configuration item of the current stage of the second management entity, and returning an OAM configuration item negotiation passing message of the current stage to the first management entity. Execution continues with S130.
Optionally, the OAM configuration item sent by the second management entity may be carried in a Loopback Message (LBM), and the OAM configuration item negotiation of the current stage returned by the first management entity may be carried in a Loopback Reply (LBR) Message through a Message.
S130, judging whether the OAM configuration items of all negotiation stages are negotiated, if so, executing S150; if not, go to S140.
S140, receiving the OAM configuration item of the next stage of the first management entity sent by the first management entity, and jumping to S120.
And S150, finishing the OAM configuration negotiation. Then, OAM detection is automatically started.
It should be noted that, in the above embodiments, the first management entity is a sender of the OAM configuration item, and the second management entity is a receiver and a comparing party of the OAM configuration item, but is not limited thereto. Those skilled in the art should understand that the operations of the second management entity and the first management entity may be interchanged, i.e. the second management entity is the sender of the OAM configuration item and the first management entity is the receiver and the comparing party of the OAM configuration item.
Further, in order to improve the accuracy of the OAM configuration item negotiation, or when it is necessary to learn the OAM configuration item of the opposite end, the operations of the first management entity and the second management entity are mirror images of each other, that is, the OAM configuration items of the current stage are respectively sent to the opposite end, and whether the received OAM configuration items are matched with the OAM configuration items of the current stage of the local end is respectively judged; and if the matching is successful, returning a message that the OAM configuration item in the current stage passes the negotiation to the opposite terminal. Based on this, the present embodiment further includes: the second management entity sends the OAM configuration item of the current stage of the second management entity to the first management entity, and the first management entity returns the OAM configuration item negotiation passing message of the current stage to the second management entity if judging that the OAM configuration item of the current stage of the second management entity is matched with the OAM configuration item of the current stage of the first management entity; and after receiving the OAM configuration item negotiation passing message of the current stage and returning the OAM configuration item negotiation passing message of the current stage to the first management entity, the second management entity sends the OAM configuration item of the next stage to the first management entity.
In the technical scheme of this embodiment, by receiving the OAM configuration item in the current stage of the first management entity sent by the first management entity, that is, the management entity may send the OAM configuration item to the opposite end in stages, so that the opposite end performs comparison negotiation; according to a predetermined operation, management and maintenance (OAM) configuration item negotiation stage, determining that an OAM configuration item of a current stage of a first management entity is matched with an OAM configuration item of a current stage of a second management entity, and returning an OAM configuration item negotiation passing message of the current stage to the first management entity; then, receiving the OAM configuration items of the next stage of the first management entity sent by the first management entity until the OAM configuration items of all negotiation stages are negotiated, thereby determining that the OAM configuration items in the two management entities are matched with each other in a staged negotiation manner and avoiding OAM configuration errors; the OAM configuration inspection efficiency is improved without manual inspection, and the OAM can be rapidly deployed in the network.
In some embodiments, the negotiation phase of the predetermined OAM configuration entry includes the following two partitioning methods:
the first partitioning method: the first negotiation stage negotiates the identity of the management entity group and the type of the detection object, the second negotiation stage negotiates the endpoint identity of the management entity group, and the third negotiation stage negotiates the OAM message grade and the OAM message sending period.
The second partitioning method comprises the following steps: the first negotiation stage negotiates the identification of the management entity group, the type of the detected object, the level of the OAM message and the sending period of the OAM message, and the second negotiation stage negotiates the end point identification of the management entity group. Because the OAM message level and the OAM message sending period are consistent with the negotiation method of the MegID and the detection object type, namely the OAM configuration items are the same, the OAM message level and the OAM message sending period can be classified into the first stage.
Of course, the OAM message level and the OAM message sending period may be classified into a single phase, for example, the second phase, and the MepID into the third phase. Or classifying the MepID into the second stage, and classifying the OAM message grade and the OAM message sending period into the third stage.
It should be noted that the above combination and phase division of the OAM configuration items are only exemplary, and any possible combination and phase division of the OAM configuration items is within the scope of the present invention.
Example two
The embodiment further optimizes the above embodiment, and specifically defines that the OAM configuration item at the current stage includes the MegID and the detection object type, and a process of negotiating the MegID and the detection object type.
Fig. 2 is a flowchart of an OAM configuration negotiation method provided in the second embodiment of the present invention, which specifically includes the following steps:
s210, receiving an OAM configuration item of the current stage sent by the first management entity, wherein the OAM configuration item of the current stage comprises a MegID and a detection object type.
S220, indexing the OAM instance of the second management entity according to the label of the message sent by the first management entity.
The LBM packet sent by the first management entity includes a MegID, a detection object type, and a packet label, such as an LSP label, a PW label, or a Section label, where the packet label is a unique identifier of the OAM instance, such as a detection object type and a management entity group identifier. Based on this, the OAM instance of the second management entity is indexed according to the label of the message.
S230, determining whether an OAM instance of the second management entity is indexed, and if so, executing S240; if not, S270 is performed.
If the OAM instance is indexed, the subsequent stage judgment is continued; if the OAM instance is not indexed, it is described that the second management entity does not configure the OAM instance corresponding to the label of the message, or the OAM instance is configured incorrectly. At this time, either of the following two ways may be performed:
the first mode is as follows: and the first management entity does not return the management entity group identification and the detection object type negotiation passing message to the first management entity, the first management entity cannot receive the reply message and waits for overtime, and the first management entity notifies the network management system of negotiation failure.
The second mode is as follows: and the first management entity receives the MegID and detection object type negotiation failure message and then notifies the network management system of negotiation failure.
S240, judging whether the second management entity is in a configuration negotiation stage, and if so, jumping to S250; if not, it jumps to S260.
The configuration negotiation stage is from after OAM configuration is completed to before the negotiation is completed. After the configuration item negotiation in all stages is completed, the two management entities realize the alignment of the OAM configuration items, namely, the pairing is realized. Then, the two paired management entities automatically enter a detection stage, and network detection is carried out by receiving and sending messages.
If the second management entity is in the configuration negotiation stage, which indicates that the second management entity has not been paired with other management entities, OAM configuration negotiation with the first management entity may be continued. If the second management entity is not in the configuration negotiation stage, for example, in the detection stage (which indicates that the second management entity is already paired with other management entities), it regards that the first management entity has sent an error message, and returns a stage error message to the first management entity. After receiving the stage error message, the first management entity does not send a negotiation message to the second management entity.
S250, judging whether the MegID and the detection object type in the indexed OAM instance of the second management entity are respectively the same as the MegID and the detection object type of the first management entity, if so, executing S280; if not, that is, the MegID in the indexed OAM instance of the second management entity is not the same as the MegID of the first management entity, or the detection object type in the indexed OAM instance of the second management entity is not the same as the detection object type of the first management entity, S290 is executed.
And S260, returning a stage error message to the first management entity. And finishing the operation.
S270, not returning a MegID and detection object type negotiation passing message to the first management entity; alternatively, the MegID and detected object type negotiation back to the first management entity does not pass the message. And finishing the operation.
S280, returning MegID and detection object type negotiation passing information to the first management entity. Execution continues with S292.
And S290, returning messages of different configuration items to the first management entity. Execution continues with S291.
And if the MegID in the indexed OAM instance of the second management entity is different from the MegID of the first management entity, returning a message that the MegID is different to the first management entity. And if the detected object type in the indexed OAM instance of the second management entity is different from that of the first management entity, returning a message that the detected object type is different to the first management entity.
And S291, after the first preset duration, re-receiving the OAM configuration item of the current stage of the first management entity sent by the first management entity, and skipping to S220.
After receiving the messages of different configuration items, the first management entity waits for a first preset time period, for example, 1 minute. And sending the OAM configuration items of the current stage of the first management entity, namely the MegID and the detection object type, to the second management entity, and continuously matching with the OAM configuration items of the corresponding stage in the second management entity.
S292, receive the OAM configuration item in the next stage of the first management entity sent by the first management entity until the OAM configuration items in all negotiation stages complete negotiation.
In some embodiments, after the OAM configuration item negotiation of all negotiation stages is completed, the method further includes: the second management entity enters an OAM detection stage; and in the process of OAM detection of the second management entity, if the first management entity is detected to be failed, the configuration negotiation stage is entered again.
For example, the second management entity enters a configuration negotiation phase with the third management entity; for another example, after detecting that the first management entity restarts, the configuration negotiation phase with the first management entity is re-entered.
It should be noted that, in this embodiment, after receiving the OAM configuration item in the current stage sent by the first management entity, it is first determined whether to index the corresponding OAM instance, then it is determined whether the second management entity is in the configuration negotiation stage, and finally it is determined whether the OAM configuration items are matched, but is not limited thereto. Whether the second management entity is in the configuration negotiation stage is judged first, whether the corresponding OAM instance is indexed is judged, and whether the OAM configuration items are matched is judged finally; or, judging whether the corresponding OAM instance is indexed, judging whether the OAM configuration items are matched, and finally judging whether the second management entity is in the configuration negotiation stage.
In this embodiment, by setting several fault-tolerant mechanisms of negotiation failure, the reliability of configuration negotiation is improved, and it is convenient to find configuration errors.
EXAMPLE III
In this embodiment, the above embodiment is further optimized, and in this embodiment, the OAM configuration item at the current stage includes MepID. Correspondingly, if the OAM configuration item of the current stage of the first management entity matches with the OAM configuration item of the current stage of the second management entity, then returning the OAM configuration item negotiation passing message of the current stage to the first management entity, including: and if the MepID of the first management entity is different from the MepID of the second management entity, returning a Mep negotiation passing message to the first management entity.
The MepID of the first management entity should be different from the MepID of the second management entity before negotiation can be passed. And if the MepID of the first management entity is the same as the MepID of the second management entity, returning a Mep negotiation failure message to the first management entity.
And after receiving the Mep negotiation failure message, the first management entity continues to send the MepID to the second management entity. Based on this, the second management entity continues to receive the MepID of the first management entity sent by the first management entity, and compares whether the received MepID is the same as the MepID of the second management entity; if the Mep negotiation pass message is the same, returning the Mep negotiation pass message to the first management entity. If not, the MepID negotiation non-passing message is returned to the first management entity. And after receiving the MepID negotiation failure message, the first management entity continues to send the MepID to the second management entity.
And if the MepID of the first management entity is still different from the MepID of the second management entity after the MepID negotiation is carried out for the preset times, continuing to receive the MepID of the first management entity sent by the first management entity after waiting for the second preset time duration until the MepID of the first management entity is the same as the MepID of the second management entity.
It should be noted that, in the subsequent OAM detection process, the management entity needs to obtain the MepID of the opposite end in advance. Based on this, the second management entity determines that the MepID of the first management entity is different from the MepID of the second management entity, and learns the MepID of the first management entity. The method provided by the embodiment further comprises the following steps: and the second management entity sends the MepID to the first management entity, so that the first management entity learns the MepID of the second management entity after judging that the received MepID is different from the MepID of the local terminal, and returns a MepID negotiation passing message. After receiving the MepID negotiation passing message, the second management entity can know that the first management entity has learned the MepID of the second management entity. And after the second management entity receives the MepID negotiation passing message and returns the MepID negotiation passing message to the first management entity, receiving the OAM configuration item of the next stage.
In this embodiment, by receiving the MepID, matching the MepID with the MepID of the local terminal, and returning a message indicating whether the negotiation is passed or not, the automatic negotiation of the MepID is realized, manual inspection is not required, and the efficiency of OAM configuration inspection is improved.
Example four
In this embodiment, the OAM configuration items to be negotiated include an OAM message level and an OAM message sending period. The OAM message classes and message sending periods in the two management entities are respectively the same, and the negotiation can be passed.
The process of negotiating the OAM message level and the OAM message sending period comprises the following steps: and judging whether the OAM message grade and the OAM message sending period sent by the first management entity are respectively the same as those of the second management entity, and if so, returning an OAM message grade and an OAM message sending period negotiation passing message to the first management entity.
And if the OAM message level of the first management entity is different from that of the second management entity, or the OAM message sending period of the first management entity is different from that of the second management entity, returning messages of different configuration items to the first management entity. For example, if the levels of the OAM messages are different, a message with different levels of the OAM messages is returned to the first management entity; and if the OAM message sending periods are different, returning a message with different OAM message sending periods to the first management entity.
And after receiving the messages of different configuration items, the first management entity waits for a third preset time length and retransmits the OAM message grade and the OAM message transmission period of the first management entity to the second management entity. And after receiving the OAM message grade and the OAM message sending period of the first management entity, the second management entity judges whether the OAM message grade and the OAM message sending period of the second management entity are the same or not until the OAM message grade and the OAM message sending period of the first management entity are respectively the same as the OAM message grade and the OAM message sending period of the second management entity.
In the present invention, the first preset time period, the second preset time period, and the third preset time period may be the same or different.
In this embodiment, by receiving the OAM message level and the OAM message sending period, matching the OAM message level and the OAM message sending period with the OAM message level and the OAM message sending period of the local end, and returning a message indicating whether the negotiation is passed or not, the automatic negotiation of the OAM message level and the OAM message sending period is realized, manual inspection is not required, and the efficiency of OAM configuration inspection is improved.
In the above embodiments, the method further includes: and if the OAM configuration item fails to negotiate, displaying the reason of the negotiation failure so as to prompt the network manager of the reason of the configuration error, so that the network manager can modify the configuration item conveniently. Specifically, the second management entity is connected with a device equipped with a display apparatus, or the second management entity itself is equipped with a display apparatus. The second management entity determines that the OAM configuration item of the current stage of the first management entity is not matched with the OAM configuration item of the current stage of the second management entity, and on one hand, returns a negotiation failure reason to the first management entity, for example, "the negotiation of the MegID and the detection object type does not pass", "different configuration items", "stage error", "negotiation of the MegID does not pass", "negotiation of the OAM message level and OAM message sending period does not pass" in the above embodiment. On the other hand, the reason for the negotiation failure is displayed on the display device.
EXAMPLE five
Fig. 3 is a schematic structural diagram of an OAM configuration negotiation apparatus according to a fifth embodiment of the present invention, and includes a receiving module 51 and a sending module 52.
A receiving module 51, configured to receive an OAM configuration item of a current stage of a first management entity sent by the first management entity; receiving the OAM configuration items of the next stage of the first management entity sent by the first management entity until the OAM configuration items of all negotiation stages are negotiated;
a sending module 52, configured to determine, according to a predetermined negotiation stage of the operation, administration and maintenance OAM configuration items, that the OAM configuration item in the current stage of the first management entity is matched with the OAM configuration item in the current stage of the second management entity, and then return a negotiation passing message of the OAM configuration item in the current stage to the first management entity.
In the technical scheme of this embodiment, by receiving the OAM configuration item in the current stage of the first management entity sent by the first management entity, that is, the management entity may send the OAM configuration item to the opposite end in stages, so that the opposite end performs comparison negotiation; according to a predetermined operation, management and maintenance (OAM) configuration item negotiation stage, determining that an OAM configuration item of a current stage of a first management entity is matched with an OAM configuration item of a current stage of a second management entity, and returning an OAM configuration item negotiation passing message of the current stage to the first management entity; then, receiving the OAM configuration items of the next stage of the first management entity sent by the first management entity until the OAM configuration items of all negotiation stages are negotiated, thereby determining that the OAM configuration items in the two management entities are matched with each other in a staged negotiation manner and avoiding OAM configuration errors; the OAM configuration inspection efficiency is improved without manual inspection, and the OAM can be rapidly deployed in the network.
Optionally, the negotiation phase of the predetermined OAM configuration entry includes:
a first negotiation stage negotiates an identifier of a management entity group and a type of a detection object, a second negotiation stage negotiates an endpoint identifier of the management entity group, and a third negotiation stage negotiates an OAM message grade and an OAM message sending period; or, the first negotiation stage negotiates the identity of the management entity group, the type of the detected object, the level of the OAM message and the sending period of the OAM message, and the second negotiation stage negotiates the identity of the end point of the management entity group.
Optionally, the OAM configuration item at the current stage includes a management entity group identifier and a detection object type;
correspondingly, when determining that the OAM configuration item in the current stage of the first management entity matches the OAM configuration item in the current stage of the second management entity, the sending module 52 is specifically configured to, when returning the OAM configuration item in the current stage to the first management entity and negotiating the passing message: indexing an OAM instance of a second management entity according to a label of a message sent by a first management entity; and if the indexed management entity group identifier and the detection object type in the OAM instance of the second management entity are respectively the same as the management entity group identifier and the detection object type of the first management entity, and the second management entity is in a configuration negotiation stage, returning a management entity group identifier and detection object type negotiation passing message to the first management entity.
Optionally, after indexing the OAM instance of the second management entity according to the label of the packet sent by the first management entity, the sending module 52 is further configured to: if the OAM instance of the second management entity is not indexed, the management entity group identification and the detection object type negotiation passing message are not returned to the first management entity; or, the management entity group identification and the detection object type negotiation are returned to the first management entity without passing through the message.
Optionally, after indexing the OAM instance of the second management entity according to the label of the packet sent by the first management entity, the sending module 52 is further configured to: and if the second management entity is not in the configuration negotiation stage, returning a stage error message to the first management entity.
Optionally, after indexing the OAM instance of the second management entity according to the label of the packet sent by the first management entity, the sending module 52 is further configured to: and if the indexed OAM instance of the second management entity has a management entity group identifier different from that of the first management entity, or the detected object type in the OAM instance of the second management entity is different from that of the first management entity and the second management entity is in a configuration negotiation stage, returning a message of different configuration items to the first management entity.
Optionally, the receiving module 51 is further configured to, after returning the message of the different configuration items to the first management entity: and after the first preset duration, re-receiving the OAM configuration item of the first stage of the first management entity, which is sent by the first management entity.
Optionally, the OAM configuration item of the current stage includes an endpoint identifier of the management entity group;
correspondingly, when the sending module 52 returns the OAM configuration item negotiation passing message of the current stage to the first management entity according to the matching between the OAM configuration item of the current stage of the first management entity and the OAM configuration item of the current stage of the second management entity, it is specifically configured to: and if the endpoint identification of the management entity group of the first management entity is different from the endpoint identification of the management entity group of the second management entity, returning the endpoint identification negotiation passing message of the management entity group to the first management entity.
Optionally, if the endpoint identifier of the management entity group of the first management entity is the same as the endpoint identifier of the management entity group of the second management entity, the sending module 52 returns the endpoint identifier negotiation non-passing message of the management entity group to the first management entity; the receiving module 51 continues to receive the endpoint identifier of the management entity group of the first management entity sent by the first management entity, and compares whether the endpoint identifier of the management entity group received this time is the same as the endpoint identifier of the management entity group of the second management entity; if the endpoint identifier of the management entity group of the first management entity is still different from the endpoint identifier of the management entity group of the second management entity after the endpoint identifiers of the management entity groups are negotiated for the preset number of times, after waiting for the second preset duration, the receiving module 51 continues to receive the endpoint identifier of the management entity group of the first management entity sent by the first management entity until the endpoint identifier of the management entity group of the first management entity is the same as the endpoint identifier of the management entity group of the second management entity.
Optionally, the OAM configuration item at the current stage includes an OAM message level and an OAM message sending period;
correspondingly, when the sending module 52 returns the OAM configuration item negotiation passing message of the current stage to the first management entity according to the matching between the OAM configuration item of the current stage of the first management entity and the OAM configuration item of the current stage of the second management entity, it is specifically configured to: and if the OAM message grade and the OAM message sending period of the first management entity are respectively the same as those of the second management entity, returning the OAM message grade and the OAM message sending period negotiation passing message to the first management entity.
The sending module 52 is further configured to: and if the OAM message level of the first management entity is different from that of the second management entity, or the OAM message sending period of the first management entity is different from that of the second management entity, returning messages of different configuration items to the first management entity.
Optionally, after the sending module 52 returns the messages of different configuration items to the first management entity, and after a third preset time duration, the receiving module 51 receives the OAM message level and the OAM message sending cycle of the first management entity sent by the first management entity again until the OAM message level and the OAM message sending cycle of the first management entity are respectively the same as the OAM message level and the OAM message sending cycle of the second management entity.
Optionally, the apparatus further includes a detection module, configured to, in a process of performing OAM detection by the second management entity, if a failure of the first management entity is detected, reenter the configuration negotiation stage.
The OAM configuration negotiation device provided by the embodiment of the invention can execute the OAM configuration negotiation method provided by any embodiment of the invention, and has the corresponding functional module and beneficial effect of the execution method.
EXAMPLE six
Fig. 4 is a schematic structural diagram of a management entity according to a sixth embodiment of the present invention, as shown in fig. 4, the management entity includes a processor 60 and a memory 61; the number of the processors 60 in the management entity may be one or more, and one processor 60 is taken as an example in fig. 4; the processor 60 and the memory 61 in the management entity may be connected by a bus or other means, and fig. 4 illustrates the connection by a bus as an example.
The memory 61 may be used as a computer-readable storage medium for storing software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the OAM configuration negotiation method in the embodiment of the present invention (for example, the receiving module 51 and the sending module 52 in the OAM configuration negotiation apparatus). The processor 60 executes various functional applications and data processing of the management entity by running software programs, instructions, and modules stored in the memory 61, that is, implements the OAM configuration negotiation method described above.
The memory 61 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 61 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 61 may further include memory located remotely from the processor 60, which may be connected to a management entity over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
EXAMPLE seven
An embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, where the computer program is configured to execute a method for OAM configuration negotiation when executed by a processor, and the method includes:
receiving an OAM configuration item of a current stage of a first management entity, which is sent by the first management entity;
according to a predetermined operation, management and maintenance (OAM) configuration item negotiation stage, determining that the OAM configuration item of the current stage of the first management entity is matched with the OAM configuration item of the current stage of the second management entity, and returning an OAM configuration item negotiation passing message of the current stage to the first management entity;
and receiving the OAM configuration item of the next stage of the first management entity sent by the first management entity until the OAM configuration item negotiation of all negotiation stages is completed.
Of course, the computer program provided in the embodiments of the present invention is not limited to the method operations described above, and may also perform related operations in the OAM configuration negotiation method provided in any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the OAM configuration negotiation apparatus, each included unit and module is only divided according to function logic, but is not limited to the above division, as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (9)
1. An OAM configuration negotiation method, comprising:
receiving an OAM configuration item of a current stage of a first management entity, which is sent by the first management entity;
according to a predetermined operation, management and maintenance (OAM) configuration item negotiation stage, determining that the OAM configuration item of the current stage of the first management entity is matched with the OAM configuration item of the current stage of the second management entity, and returning an OAM configuration item negotiation passing message of the current stage to the first management entity;
receiving an OAM configuration item of a next stage of the first management entity sent by the first management entity until the OAM configuration items of all negotiation stages are negotiated;
the negotiation phase of the predetermined OAM configuration item includes: a first negotiation stage negotiates an identifier of a management entity group and a type of a detection object, a second negotiation stage negotiates an endpoint identifier of the management entity group, and a third negotiation stage negotiates an OAM message grade and an OAM message sending period; alternatively, the first and second electrodes may be,
the first negotiation stage negotiates the identification of the management entity group, the type of the detected object, the level of the OAM message and the sending period of the OAM message, and the second negotiation stage negotiates the end point identification of the management entity group.
2. The method of claim 1, wherein the OAM configuration items of the current phase include a management entity group identifier and a detection object type;
correspondingly, if it is determined that the OAM configuration item of the current stage of the first management entity matches the OAM configuration item of the current stage of the second management entity, returning the OAM configuration item of the current stage to the first management entity to negotiate a pass message, which includes:
indexing an OAM instance of a second management entity according to a label of a message sent by a first management entity;
and if the indexed management entity group identifier and the detection object type in the OAM instance of the second management entity are respectively the same as the management entity group identifier and the detection object type of the first management entity, and the second management entity is in a configuration negotiation stage, returning a management entity group identifier and detection object type negotiation passing message to the first management entity.
3. The method of claim 1, wherein the OAM configuration entry for the current stage comprises an endpoint identification for a group of management entities;
correspondingly, if it is determined that the OAM configuration item of the current stage of the first management entity matches the OAM configuration item of the current stage of the second management entity, returning the OAM configuration item of the current stage to the first management entity to negotiate a pass message, which includes:
and if the endpoint identification of the management entity group of the first management entity is different from the endpoint identification of the management entity group of the second management entity, returning the endpoint identification negotiation passing message of the management entity group to the first management entity.
4. The method of claim 3, further comprising:
if the endpoint identification of the management entity group of the first management entity is the same as the endpoint identification of the management entity group of the second management entity, returning the endpoint identification negotiation failure message of the management entity group to the first management entity;
continuously receiving the endpoint identifier of the management entity group of the first management entity sent by the first management entity, and comparing whether the endpoint identifier of the management entity group received this time is the same as the endpoint identifier of the management entity group of the second management entity;
if the endpoint identifier of the management entity group of the first management entity is still different from the endpoint identifier of the management entity group of the second management entity after the endpoint identifiers of the management entity groups are negotiated for the preset times, after waiting for a second preset time, the endpoint identifier of the management entity group of the first management entity, which is sent by the first management entity, is continuously received until the endpoint identifier of the management entity group of the first management entity is the same as the endpoint identifier of the management entity group of the second management entity.
5. The method of claim 1, wherein the OAM configuration items of the current phase include an OAM message level and an OAM message sending period;
correspondingly, if it is determined that the OAM configuration item of the current stage of the first management entity matches the OAM configuration item of the current stage of the second management entity, returning the OAM configuration item of the current stage to the first management entity to negotiate a pass message, which includes:
and if the OAM message grade and the OAM message sending period of the first management entity are respectively the same as those of the second management entity, returning the OAM message grade and the OAM message sending period negotiation passing message to the first management entity.
6. The method of claim 1, wherein determining that the current-phase OAM configuration entry of the first management entity matches the current-phase OAM configuration entry of the second management entity, then returning the current-phase OAM configuration entry negotiation pass message to the first management entity comprises:
and if the OAM message level of the first management entity is different from that of the second management entity, or the OAM message sending period of the first management entity is different from that of the second management entity, returning messages of different configuration items to the first management entity.
7. An OAM configuration negotiation apparatus, comprising:
a receiving module, configured to receive an OAM configuration item of a current stage of a first management entity sent by the first management entity; receiving the OAM configuration items of the next stage of the first management entity sent by the first management entity until the OAM configuration items of all negotiation stages are negotiated;
a sending module, configured to determine, according to a predetermined negotiation stage of an operation, administration and maintenance OAM configuration item, that an OAM configuration item at a current stage of the first management entity is matched with an OAM configuration item at a current stage of the second management entity, and then return an OAM configuration item negotiation passing message at the current stage to the first management entity;
the negotiation phase of the predetermined OAM configuration item includes: a first negotiation stage negotiates an identifier of a management entity group and a type of a detection object, a second negotiation stage negotiates an endpoint identifier of the management entity group, and a third negotiation stage negotiates an OAM message grade and an OAM message sending period; alternatively, the first and second electrodes may be,
the first negotiation stage negotiates the identification of the management entity group, the type of the detected object, the level of the OAM message and the sending period of the OAM message, and the second negotiation stage negotiates the end point identification of the management entity group.
8. A management entity, comprising:
one or more processors;
a memory for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the OAM configuration negotiation method of any of claims 1-6.
9. A computer readable storage medium having stored thereon a computer program, characterized in that the program, when executed by a processor, implements the OAM configuration negotiation method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810681363.4A CN108933696B (en) | 2018-06-27 | 2018-06-27 | OAM configuration negotiation method, device, management entity and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810681363.4A CN108933696B (en) | 2018-06-27 | 2018-06-27 | OAM configuration negotiation method, device, management entity and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108933696A CN108933696A (en) | 2018-12-04 |
| CN108933696B true CN108933696B (en) | 2021-08-20 |
Family
ID=64446453
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810681363.4A Active CN108933696B (en) | 2018-06-27 | 2018-06-27 | OAM configuration negotiation method, device, management entity and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108933696B (en) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110174307A1 (en) * | 2006-01-04 | 2011-07-21 | Lessi Stephane | Device for Supplying Oxygen to the Occupants of an Aircraft and Pressure Regulator for Such a Device |
| CN101237349A (en) * | 2008-02-26 | 2008-08-06 | 华为技术有限公司 | Report negotiation method, device and system |
| CN102480380B (en) * | 2010-11-26 | 2016-01-20 | 中兴通讯股份有限公司 | A kind of realize ethernet device set up OAM connect method and system |
| CN102868569B (en) * | 2012-06-30 | 2015-12-09 | 华为技术有限公司 | The method for testing performance of Layer3 Virtual Private Network, node and system |
| CN103780420B (en) * | 2012-10-25 | 2017-07-28 | 中国电信股份有限公司 | The method of automatic configuration and system of Ethernet detection of connectivity under VPLS environment |
-
2018
- 2018-06-27 CN CN201810681363.4A patent/CN108933696B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108933696A (en) | 2018-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109347705B (en) | Loop detection method and device | |
| US8824275B2 (en) | Route calculating after switching occurs from a primary main control board to a standby main control board | |
| CN109474495B (en) | Tunnel detection method and device | |
| CN111614505B (en) | Message processing method and gateway equipment | |
| CN106411727B (en) | Message processing method, device and autonomous system | |
| EP3806404A1 (en) | Communication method, device and system for avoiding loop | |
| CN114866365B (en) | Arbitration machine election method, device, intelligent equipment and computer readable storage medium | |
| CN107948063B (en) | Method for establishing aggregation link and access equipment | |
| CN109873719B (en) | Fault detection method and device | |
| CN109189403B (en) | Operating system OS batch installation method and device and network equipment | |
| CN109120449B (en) | Method and device for detecting link failure | |
| CN105515970B (en) | A kind of method and apparatus being used for transmission message | |
| CN112787843B (en) | Method for detecting fault node, storage medium and electronic device | |
| CN108933696B (en) | OAM configuration negotiation method, device, management entity and storage medium | |
| CN113055203B (en) | Method and device for recovering exception of SDN control plane | |
| CN108616423B (en) | Offline device monitoring method and device | |
| CN110661628B (en) | Method, device and system for realizing data multicast | |
| CN113904972B (en) | Path detection method and device, controller and PE (polyethylene) equipment | |
| CN107453995B (en) | Designated router election method, device, router and communication system | |
| CN115720193A (en) | Multicast-based software deployment method and device | |
| CN108141406B (en) | Method, device and equipment for processing service fault | |
| CN112468363B (en) | Method and device for detecting link connectivity | |
| CN110611620B (en) | Link updating method and device | |
| US7916630B2 (en) | Monitoring condition of network with distributed components | |
| CN105577427A (en) | Detection method and device for communication connection between household appliance and mobile terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |