CN104734876A - Ethernet OAM configuration achieving method and device - Google Patents
Ethernet OAM configuration achieving method and device Download PDFInfo
- Publication number
- CN104734876A CN104734876A CN201310724458.7A CN201310724458A CN104734876A CN 104734876 A CN104734876 A CN 104734876A CN 201310724458 A CN201310724458 A CN 201310724458A CN 104734876 A CN104734876 A CN 104734876A
- Authority
- CN
- China
- Prior art keywords
- oam
- openflow switch
- network controller
- type
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 24
- 230000004044 response Effects 0.000 claims description 6
- 210000003311 CFU-EM Anatomy 0.000 description 40
- 238000010586 diagram Methods 0.000 description 32
- 238000005516 engineering process Methods 0.000 description 8
- 238000012423 maintenance Methods 0.000 description 8
- 238000012544 monitoring process Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000001514 detection method Methods 0.000 description 3
- 101100495054 Mus musculus Ccndbp1 gene Proteins 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000004807 localization Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 239000010454 slate Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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/26—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using dedicated tools for LAN [Local Area Network] management
-
- 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses an Ethernet OAM configuration achieving method. The method comprises the steps that capability negotiation is carried out between a network controller and an OpenFlow switch, and an OAM type supported by the OpenFlow switch is obtained; the network controller sends configuration information to the OpenFlow switch according to the OAM type supported by the OpenFlow switch; after the OpenFlow switch receives the configuration information, an OAM entity and function configuration thereof are created. The invention further discloses an Ethernet OAM configuration achieving device.
Description
Technical Field
The present invention relates to a configuration management technology in Ethernet (Ethernet), and in particular, to a method and an apparatus for implementing Ethernet operation, Administration and maintenance (OAM) configuration in OpenFlow (OpenFlow).
Background
In the prior art, Software-Defined Network (SDN) is a new Network innovation architecture proposed by the clean slate research group of stanford university, usa. Specifically, the data path of the network bottom layer, such as a switch, a router and the like, is "dumb, simple and minimal", and by defining a public Application Programming Interface (API) which is open to the outside and related to the flow table, the API of the bottom layer can be freely called on the network controller for programming at the same time, thereby realizing the innovation of the network.
At present, the core technology OpenFlow protocol of the SDN separates a control plane and a data plane of a network device to realize flexible control of network traffic, and provides a good platform for innovation of a core network and application. In the SDN, the used OpenFlow switch comprises a flow table, a secure channel and an OpenFlow protocol; wherein,
the secure channel is an interface for connecting the OpenFlow switch to the network controller, the network controller controls and manages the OpenFlow switch through the interface, and meanwhile, the network controller receives events from the OpenFlow switch and sends data packets to the OpenFlow switch; the OpenFlow switch and the network controller communicate through a secure channel, and all interaction information must be executed in a format specified by the OpenFlow protocol.
The OpenFlow protocol is used for describing a standard of information used for interaction between the network controller and the OpenFlow switch and an interface standard of the network controller and the OpenFlow switch; the core part of the OpenFlow protocol is a set for an OpenFlow protocol information structure; the OpenFlow protocol supports three information types: controllers-to-Switch, Asynchronous (Asynchronous), and Symmetric (Symmetric), each type having multiple sub-types. Wherein, the Controller-to-Switch information is initiated by the network Controller and is directly used for detecting the state of the OpenFlow Switch; asynchronous information is initiated by an OpenFlow switch and is typically used to update network events of a network controller and to change the state of the OpenFlow switch; the Symmetric information may be initiated by a network controller or an OpenFlow switch without a request.
Currently, an OpenFlow protocol is used as an interface protocol between a network controller and an OpenFlow switch in an SDN, and control and forwarding separation can be realized by controlling a flow table, so that a service connection related function of the OpenFlow switch is realized. However, in the conventional transmission network technology, monitoring and reporting of a fault, triggering of a recovery mechanism, and the like are all important, and include space Switching, Dense Wavelength Division Multiplexing (DWDM), Time Division Multiplexing (TDM), and Provider Backbone Bridging technology (PBB-TE) and Multi-Protocol Label Switching (MPLS) technology, which are based on Traffic Engineering extension of ethernet. In these techniques, OAM functions may be used to monitor the performance of the connection, triggering recovery mechanisms for the data plane, such as: in ethernet PBB-TE technology, ethernet Connection Fault Management (CFM) defines a connection monitoring OAM flow for detecting the survivability of an ethernet network; OAM is an indispensable function in a transmission network. Therefore, the function of OAM needs to be actively or passively activated and kept consistent with the connection function, prevent the generation of false alarms, and guarantee the consistency of operations. In some technologies, a configuration operation needs to be performed on an OAM entity, and a network user must be able to select some functions of OAM according to the type of a connection, configure parameters of OAM, and activate the OAM functions at any time. In the MPLS protocol, it is necessary to support an automatic dynamic monitoring function of an LSP, and especially when the number of LSPs is large, dynamic OAM configuration is important. To achieve the above purpose, the OAM entities and their related functions need to implement dynamic configuration.
In the prior art, a control plane uses a resource reservation Protocol (RSVP-TE) signaling message based on traffic engineering extension to implement dynamic configuration of an OAM function, but in the current OpenFlow Protocol, there is no corresponding extension to implement a function related to Ethernet OAM dynamic configuration. Therefore, related extensions are needed on the basis of the OpenFlow protocol in order to implement OAM configuration functions in ethernet transport network technology.
Disclosure of Invention
In view of this, embodiments of the present invention are intended to provide a method and an apparatus for implementing Ethernet OAM configuration, so that an OpenFlow switch can support Ethernet OAM functions.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the embodiment of the invention provides a method for realizing Ethernet OAM configuration, which comprises the following steps:
carrying out capability negotiation between the network controller and the OpenFlow switch to obtain an OAM type supported by the OpenFlow switch;
the network controller sends a configuration message to the OpenFlow switch according to the OAM type supported by the OpenFlow switch;
and after the OpenFlow switch receives the configuration message, creating an OAM entity and function configuration thereof.
In the above scheme, the method further includes monitoring the Ethernet label switching path LSP after the OpenFlow switch creates OAM, and reporting fault information to the network controller.
In the foregoing solution, the negotiating capabilities between the network controller and the OpenFlow switch includes:
the network controller sends an OFPT _ FEATURES _ REQUEST REQUEST message to the OpenFlow switch, wherein the capability field Capabilities is OFPC _ OAM _ TYPE;
the OpenFlow switch returns an OFPT _ FEATURES _ REPLY response message to the network controller, wherein the last 8 bits of the Reserved field carry an OAM type field, which indicates that the OpenFlow switch is of an Ethernet OAM type.
In the above scheme, the network controller sends a configuration message to the OpenFlow switch, and the network controller sends a CONFIG message configuring the OAM entity and its related functions to the OpenFlow switch;
the CONFIG message is an OFPT _ SET _ CONFIG message; the OFPT _ SET _ CONFIG message includes: configuring the corresponding node type, OAM type and Sub-TLV type, and configuring version number, MD level and whether OAM function is started in the Sub-TLV.
In the above scheme, the OpenFlow switch reports the fault information to the network controller through an ERROR message; wherein the fault information includes: error codes generated in OAM configuration, error codes generated in featuremessages, and error codes generated in CONFIG messages.
The embodiment of the invention also provides a device for realizing Ethernet OAM configuration, which comprises: a network controller, an OpenFlow switch; wherein,
the network controller is used for carrying out capability negotiation with the OpenFlow switch to obtain an OAM type supported by the OpenFlow switch; sending a configuration message to the OpenFlow switch according to the OAM type supported by the OpenFlow switch;
the OpenFlow switch is used for creating an OAM entity and function configuration thereof after receiving the configuration message.
In the above scheme, the OpenFlow switch is further configured to monitor the Ethernet LSP after OAM is created, and report fault information to the network controller.
In the foregoing solution, the network controller is configured to perform capability negotiation with an OpenFlow switch, and includes:
the network controller sends an OFPT _ FEATURES _ REQUEST REQUEST message to the OpenFlow switch, wherein the capability field Capabilities is OFPC _ OAM _ TYPE;
the OpenFlow switch returns an OFPT _ FEATURES _ REPLY response message to the network controller, wherein the last 8 bits of the Reserved field carry an OAM type field, which indicates that the OpenFlow switch is of an Ethernet OAM type.
In the above scheme, the network controller sends a configuration message to the OpenFlow switch, and the network controller sends a CONFIG message configuring the OAM entity and its related functions to the OpenFlow switch;
the CONFIG message is an OFPT _ SET _ CONFIG message; the OFPT _ SET _ CONFIG message includes: configuring the corresponding node type, OAM type and Sub-TLV type, and configuring version number and MD level in the Sub-TLV, and whether to start OAM function.
In the above scheme, the OpenFlow switch reports the fault information to the network controller through an ERROR message; wherein the fault information includes: error codes generated in OAM configuration, error codes generated in featuremessages, and error codes generated in CONFIG messages.
According to the method and the device for realizing Ethernet OAM configuration, provided by the embodiment of the invention, capability negotiation is carried out between the network controller and the OpenFlow switch; the network controller sends configuration information to the OpenFlow switch, and the OpenFlow switch creates an OAM entity and function configuration thereof after receiving the configuration information; further, after the OAM is created, the OpenFlow switch monitors an Ethernet Switched Path (LSP) and reports fault information to the network controller. Therefore, corresponding expansion can be increased by perfecting the processing flow of OAM configuration in the OpenFlow protocol, and on the premise of following the existing OpenFlow protocol, the related functions of Ethernet OAM configuration are realized, so that the OpenFlow switch can support the Ethernet OAM function.
Drawings
FIG. 1 is a diagram illustrating OAM extension format in RSVP-TE;
fig. 2 is a schematic diagram of OAM Sub-TLV format;
FIG. 3 is a schematic diagram of the Ethernet OAM Sub-TLV format;
FIG. 4 is a diagram showing the MD Name Sub-TLV format in Ethernet OAM;
FIG. 5 is a schematic diagram of Short MA Name Sub-TLV format in Ethernet OAM;
FIG. 6 is a diagram showing MEP ID Sub-TLV format in Ethernet OAM;
FIG. 7 is a diagram showing the format of CC Sub-TLV in Ethernet OAM;
fig. 8 is a schematic diagram of an Ethernet LSP network under the SDN architecture;
fig. 9 is a schematic processing flow diagram of a method for implementing Ethernet OAM configuration according to an embodiment of the present invention;
fig. 10 is a schematic diagram illustrating a specific processing flow of a method for implementing Ethernet OAM configuration according to an embodiment of the present invention;
fig. 11 is a diagram illustrating an OAM capability negotiation in FEATURESs message extension;
fig. 12 is a schematic diagram illustrating an OAM configuration in a CONFIG message extension;
FIG. 13 is an expanded view of the Ethernet OAM Sub-TLV configuration;
FIG. 14 is an extended schematic diagram of Ethernet OAM MD Name Sub-TLV;
FIG. 15 is an extended schematic diagram of Ethernet OAM Short MA Name Sub-TLV;
FIG. 16 is an extended schematic diagram of Ethernet OAM MEP ID Sub-TLV;
FIG. 17 is an expanded view of Ethernet OAM CC Sub-TLV;
fig. 18 is a schematic diagram illustrating a configuration of an apparatus for implementing Ethernet OAM configuration according to an embodiment of the present invention.
Detailed Description
In practical applications, the configuration of OAM mainly includes: creating an OAM entity and its functional configuration, OAM parameter adjustment, and deleting the OAM entity.
Specifically, the creating of the OAM entity and the implementation of the functional configuration thereof include:
the Maintenance nodes (MAintenance Points, MP) comprise Maintenance end nodes (MEP) and Maintenance Intermediate nodes (MIP); the MEPs are located at two ends of the connection, and can initiate and terminate OAM messages for Fault Management (FM) and Performance Monitoring (PM); MIP is at the connected intermediate node and can only receive OAM messages.
A Maintenance Entity (ME) as a collaboration between the MEP and the MIP to monitor the connection; as long as the connection between MEP and MIP is established, the forwarding relationship between the end points and the intermediate nodes is already established, and this connection enables the OAM entity to monitor the LSP.
Besides the related parameters defined by MP and ME, active OAM functions such as Consistency Check (CC) and PM require parameter configuration; these parameters may be configured before the connection is established or may be obtained at the time of connection establishment.
In the prior art, the OAM configuration process is realized by using RSVP-TE as follows:
fig. 1 is a schematic diagram of an OAM extension format in RSVP-TE, and as shown in fig. 1, an OAM type indicates an OAM entity type supported by a creating node; when an OAM entity is created, if the node device does not support OAM types, an error code "OAM promlem/Unsupported OAM Type" needs to be returned.
Fig. 2 is a schematic format diagram of the OAM Sub-TLV, and as shown in fig. 2, in the OAM Sub-TLV, the OAM Function Flag takes different values as follows: a CC function 0, a Connectivity Verification (CV) function 1, a Fault Management Signal (FMS) function 2, a PM/Loss function 3, a PM/Delay function 4, and a PM/Throughput Measurement function 5.
When OAM is created, capability negotiation is needed between nodes. The attribute of the node is represented in the LSP _ ATTRIBUTES flag bit, which indicates whether the node is an MEP or an MIP, if the 'OAM MEP entries determined' bit is set, the node is an MEP, and if the 'OAM MIP entries determined' bit is set, the 'OAM MIP entry determined' bit is set, the node is an MIP. The ADMIN _ STATUS flag bit 'OAM Alarms Enabled' indicates whether the OAM alarm is turned on, and when the flag bit is set, indicates that the OAM alarm function is turned on.
The OAM parameter adjustment is realized by the following steps: for the OAM functions that have been created and configured, parameter adjustments may be needed during the LSP's lifecycle, at which point the OAM parameters need to be updated. The OAM parameters relate to the content and duration of the OAM message and also relate to the modes of OAM detection, acquisition and alarm generation; therefore, the source and tail ends of OAM need to synchronize update data.
Firstly, the alarm function of OAM is forbidden, and the ADMIN _ STATUS flag bit 'OAM AlarmMSEnable' is cleared; secondly, the OAM parameters are readjusted. After the OAM parameters are updated, the ADMIN _ STATUS flag bit, "OAM Alarms Enabled," is set.
The OAM entity deletion implementation comprises: in some cases, some or all OAM entities and functions need to be deleted without affecting the established connection. Firstly, the alarm function of OAM is forbidden, an ADMIN _ STATUS flag bit 'OAM Alarms Enabled' is cleared, and an 'OAM MEP entries determined' bit and an 'OAM entries determined' bit in an LSP _ ATTRIBUTES flag bit are cleared; thereafter, deletion of the OAM entity is automatically triggered.
The following is a brief description of the functional configuration of Ethernet OAM.
In order to simplify the configuration of connection detection, when an ethernet LSP is established, ethernet OAM needs to be created at the same time, and MEPs need to be configured at both ends in a bidirectional point-to-point PBB-TE connection. When the MEP monitors the PBB-TE connection, a Maintenance Domain Level (MD Level) and a Maintenance Association Identifier (MAID) need to be configured; each MEP has a unique MEP ID; at the intermediate node, MIP needs to be configured for fault localization, such as: link tracking and loop detection functions.
In ethernet OAM, in addition to configuring the basic OAM parameters, the following related parameters specific to ethernet need to be configured:
1) the method comprises the steps that unique MAIDs are required to be allocated to two MEPs connected with the PBB-TE, wherein the MAIDs comprise optional MD names and Short MA names;
2) each MEP needs to be allocated with an MEP ID, and a MAID and an MEP ID can define a unique MEP;
3) the MD level may allow for hierarchical isolation of monitoring entities;
4) a forwarding priority;
5) MEPs need to know parameter information of themselves and remotely reachable MEPs.
Fig. 3 is a schematic diagram of an Ethernet OAM Sub-TLV format, and as shown in fig. 3, in the Ethernet OAM configuration parameters, the value of OAM type is 1, which is defined as Ethernet OAM type; version is CFM protocol Version; md.l is MD grade; the Sub-TLV may carry an ethernet-capable Sub-TLV type.
FIG. 4 is a schematic diagram of the MD Name Sub-TLV format in Ethernet, and as shown in FIG. 4, Type is defined as 1, indicating MD Name Sub-TLV.
FIG. 5 is a schematic diagram showing the format of Short MA Name Sub-TLV in Ethernet, and as shown in FIG. 5, Type is 2, which indicates Short MA Name Sub-TLV.
FIG. 6 is a schematic diagram showing the MEP ID Sub-TLV format in Ethernet OAM, and as shown in FIG. 6, the Type is 3, which indicates the MEP ID Sub-TLV; the Local MEP ID is Local MEP ID, 16-bit integer type, and the range is 1-8191; the Remote MEP ID is the MEP ID of the opposite end, is a 16-bit integer type and ranges from 1 to 8191; and the T bit and the R bit are set when the MEP sends a packet, and the R bit is set when the MEP receives the packet.
FIG. 7 is a schematic diagram of CC Sub-TLV format in Ethernet OAM, as shown in FIG. 7, Type is 3, indicating CC Type Sub-TLV; prio is defined as the priority of CCM frames; CCM I is defined as the gap in CCM.
In addition, in the Ethernet OAM configuration, the following error types are also defined:
1) when the node does not support a certain CFM version, returning 'OAM Problem/Unconstructed OAMVersion';
2) when the node does not support a certain MD level, returning 'OAM Problem/Unposed MDLevel';
3) when the node receives an undefined MD Name Format, the node returns 'OAM Problem/Unknown MD Name Format';
4) when the node receives an undefined MA Name Format, the node returns 'OAM Problem/Unknown MA Name Format';
5) when the total Length of the MD Name and the MA Name is less than or equal to 44 bytes, returning to OAMProblem/Name Length Problem;
6) when the node does not support the requested CCM gap, "OAM promlem/unpopulated CCInterval" is returned.
Based on the introduction and analysis of the concept, in the embodiment of the present invention, capability negotiation is performed between a network controller and an OpenFlow switch, and an OAM type supported by the OpenFlow switch is obtained; the network controller sends a configuration message to the OpenFlow switch according to the OAM type supported by the OpenFlow switch; and after the OpenFlow switch receives the configuration message, creating an OAM entity and function configuration thereof.
Further, after the OAM is created, the OpenFlow switch monitors the Ethernet LSP and reports the fault information to the network controller.
Here, in the conventional transport network, OAM configuration is completed between nodes through signaling, and in the SDN architecture, an Ethernet LSP needs to be established to an OpenFlow switch through an OpenFlow protocol interface between a network controller and the OpenFlow switch, as shown in fig. 8, fig. 8 is a schematic diagram of an Ethernet LSP network in the SDN architecture.
The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
Fig. 9 is a schematic processing flow diagram of a method for implementing Ethernet OAM configuration according to an embodiment of the present invention, and as shown in fig. 9, the method for implementing Ethernet OAM configuration according to an embodiment of the present invention includes:
step S100: carrying out capability negotiation between the network controller and the OpenFlow switch to obtain an OAM type supported by the OpenFlow switch;
here, capability negotiation is performed between the network controller and the OpenFlow switch, and is completed through FEATURES messages in the OpenFlow protocol.
Step S101: the network controller sends a configuration message to the OpenFlow switch according to the OAM type supported by the OpenFlow switch;
here, the network controller sends a CONFIG message configuring the OAM entity and its related functions to the OpenFlow switch.
Step S102: and after the OpenFlow switch receives the configuration message, creating an OAM entity and function configuration thereof.
Under the SDN architecture, a network controller is required to issue an Ethernet LSP service establishment request between OpenFlow switches through an OpenFlow interface, where connection establishment between nodes is completed in a form of flow table issue.
Here, OAM configuration may be completed before service establishment or simultaneously with service establishment, and therefore, the OAM entity is created in the following manner: the flow table is created before or together with the flow table issuing time.
Fig. 10 is a schematic processing flow diagram of a method for implementing Ethernet OAM configuration according to an embodiment of the present invention, and as shown in fig. 10, the method for implementing Ethernet OAM configuration according to an embodiment of the present invention specifically includes:
step S200: the network controller sends an OFPT _ FEATURES _ REQUEST REQUEST message to the OpenFlow switch;
wherein, the capability field Capabilities is OFPC _ OAM _ TYPE.
Here, the OAM capability negotiation may extend an OAM capability TYPE OFPC _ OAM _ TYPE =1< <4 in Capabilities of the OFPT _ featuresjrequest message, as shown in fig. 11, which is a schematic diagram of the OAM capability negotiation extending in featuresmessage.
Step S201: the OpenFlow switch returns an OFPT _ FEATURES _ REPLY response message to the network controller;
wherein, the last 8 bits of the Reserved field Reserved carry an OAM type field, which indicates that the OpenFlow switch is of Ethernet OAM type.
Step S202: the network controller sends a CONFIG message for configuring the OAM entity and related functions thereof to the OpenFlow switch;
here, the CONFIG message is an OFPT _ SET _ CONFIG message; the OFPT _ SET _ CONFIG message includes: configuring corresponding node type, OAM type and Sub-TLV type, and configuring version number, MD level, whether OAM function is started or not in Sub-TLV, and the like;
the configured corresponding node type includes an MEP type and an MIP type, and the OAM type may be an Ethernet OAM configuration type.
Step S203: after the OpenFlow switch receives the configuration message, an OAM entity and the function configuration thereof are established;
fig. 12 is a schematic diagram illustrating an OAM configuration in a CONFIG message extension, and as shown in fig. 12, the OAM configuration configures OAM according to an OFPT _ SET _ CONFIG message before service is established; the type of the extended flags field, that is, the OAM configuration message is denoted by OFPC _ FRAG _ OAM =1< <2 in the enumeration type ofp _ config _ flags; an extension field, which is Node Type and 8 bits respectively, is extended in the structure ofp _ switch _ CONFIG of the OFPT _ SET _ CONFIG message to indicate whether the Node is MEP (Node Type = 1) or MIP (Node Type = 2); the OAM Type is 8 bits and is used for indicating the Type of the OAM, and the OAM Type =1 is the Ethernet OAM Type; OAM Alarms Enabled, 8 bits, used to indicate whether OAM is on, set indicating on, clear indicating off; Sub-TLV Type, 8 bits, indicating the Type of Sub-TLV; Sub-TLV, indefinite length, is configured according to the type of OAM.
FIG. 13 is an expanded view of the configuration of Ethernet OAM Sub-TLV, as shown in FIG. 13, Version is CFM protocol Version; md.l is MD grade; the Sub-TLV may carry an ethernet-capable Sub-TLV type.
FIG. 14 is an extended schematic diagram of Ethernet OAM MD Name Sub-TLV, and as shown in FIG. 14, Type is defined as 1, indicating MD Name Sub-TLV.
FIG. 15 is an extended schematic diagram of Ethernet OAM Short MA Name Sub-TLV, and as shown in FIG. 15, Type is 2, indicating Short MA Name Sub-TLV.
FIG. 16 is an extended schematic diagram of Ethernet OAM MEP ID Sub-TLV, as shown in FIG. 16, Type is 3, indicating MEP ID Sub-TLV; the Local MEP ID is Local MEP ID, 16-bit integer type, and the range is 1-8191; the Remote MEP ID is the MEP ID of the opposite end, is a 16-bit integer type and ranges from 1 to 8191; and the T bit and the R bit are set when the MEP sends a packet, and the R bit is set when the MEP receives the packet.
FIG. 17 is an expanded view of Ethernet OAM CC Sub-TLV, as shown in FIG. 17, Type is 4, indicating Sub-TLV of the consistency check CC; prio is defined as the priority of CCM frames; CCM I is defined as the gap in CCM.
Step S204: after the OpenFlow switch creates OAM, the Ethernet LSP is monitored, and fault information is reported to the network controller.
Here, the OpenFlow switch reports fault information to the network controller through an ERROR message; wherein the fault information includes: error codes generated in OAM configuration, error codes generated in featuremessages, and error codes generated in CONFIG messages.
Specifically, the ERROR code generated in the OAM configuration needs to be extended in ERROR, a new subtype needs to be added to the ERROR type corresponding to ERROR, and a corresponding ERROR code needs to be added to the ofp _ ERROR _ type enumeration type.
The type of error code generated in the FEATURE message requires addition of a subtype error code in the OFPET _ BAD _ REQUEST error type; wherein,
OFPBRC _ UNSUPPORTED _ OAM _ TYPE =14, indicating that this OAM TYPE request is not supported.
Adding subtype error codes to the OFPET _ SWITCH _ CONFIG _ FAILED error types generated in the CONFIG message; wherein,
OFPSCFC _ unsurported _ OAM _ VERSION =3, indicating that configuration of this OAM VERSION is not supported;
OFPSCFC _ UNSUPPORTED _ MD _ LEVEL =4, indicating that this MD LEVEL is not supported;
OFPSCFC _ UNKNOWN _ MD _ NAME _ FORMAT =5, indicating an UNKNOWN MD NAME FORMAT.
OFPSCFC _ UNKNOWN _ MA _ NAME _ FORMAT =6, indicating an UNKNOWN MA NAME FORMAT;
ofpsccfwrong _ NAME _ LENGTH =7, indicating the LENGTH of the NAME in error;
ofpsccfcfrcunpupported CCM _ INTERVAL =8, indicating that the CCM gap is not supported.
Fig. 18 is a schematic structural diagram of an apparatus for implementing Ethernet OAM configuration according to an embodiment of the present invention, and as shown in fig. 18, the apparatus for implementing Ethernet OAM configuration according to an embodiment of the present invention includes: a network controller 10, an OpenFlow switch 11; wherein,
the network controller 10 is configured to perform capability negotiation with the OpenFlow switch 11 to obtain an OAM type supported by the OpenFlow switch; sending a configuration message to the OpenFlow switch 11 according to the OAM type supported by the OpenFlow switch;
here, the capability negotiation between the network controller 10 and the OpenFlow switch 11 is performed by featuremessages in the OpenFlow protocol.
Specifically, the network controller 10 sends an OFPT _ FEATURES _ REQUEST message to the OpenFlow switch 11, where the capability field Capabilities is OFPC _ OAM _ TYPE;
here, the OAM capability negotiation may extend one OAM capability TYPE OFPC _ OAM _ TYPE =1< <4 in Capabilities of the OFPT _ featurs _ REQUEST message.
Correspondingly, the OpenFlow switch 11 returns an OFPT _ FEATURES _ REPLY response message to the network controller 10, where the last 8 bits of the Reserved field Reserved carry an OAM type field, indicating that the OpenFlow switch 11 is an Ethernet OAM type.
Here, the network controller 10 sends a CONFIG message configuring an OAM entity and its related functions to the OpenFlow switch 11.
Specifically, the CONFIG message is an OFPT _ SET _ CONFIG message; the OFPT _ SET _ CONFIG message includes: configuring corresponding node type, OAM type and Sub-TLV type, and configuring version number, MD level, whether OAM function is started or not in Sub-TLV, etc.
The configured corresponding node type includes an MEP type and an MIP type, and the OAM type may be an Ethernet OAM configuration type.
The OpenFlow switch 11 is configured to create an OAM entity and its functional configuration after receiving the configuration message.
The OpenFlow switch 11 is further configured to monitor the Ethernet LSP after OAM is created, and report fault information to the controller 10.
Here, the OpenFlow switch 11 reports the fault information to the network controller 10 through an ERROR message; wherein the fault information includes an error code generated in the OAM configuration, an error code generated in the FEATURE message, and an error code generated in the CONFIG message.
In the above description, the present invention is described by taking a network controller and an OpenFlow switch as examples. In an OpenFlow protocol in practical application, Ethernet OAM configuration can be implemented between one network controller and multiple OpenFlow switches.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (10)
1. A method for implementing Ethernet OAM configuration, the method comprising:
carrying out capability negotiation between the network controller and the OpenFlow switch to obtain an OAM type supported by the OpenFlow switch;
the network controller sends a configuration message to the OpenFlow switch according to the OAM type supported by the OpenFlow switch;
and after the OpenFlow switch receives the configuration message, creating an OAM entity and function configuration thereof.
2. The method of claim 1, further comprising: after the OpenFlow switch creates OAM, the OpenFlow switch monitors an Ethernet Label Switching Path (LSP) and reports fault information to a network controller.
3. The method according to claim 1 or 2, wherein capability negotiation between the network controller and the OpenFlow switch is performed, and includes:
the network controller sends an OFPT _ FEATURES _ REQUEST REQUEST message to the OpenFlow switch, wherein the capability field Capabilities is OFPC _ OAM _ TYPE;
the OpenFlow switch returns an OFPT _ FEATURES _ REPLY response message to the network controller, wherein the last 8 bits of the Reserved field carry an OAM type field, which indicates that the OpenFlow switch is of an Ethernet OAM type.
4. The method according to claim 1 or 2, wherein the network controller sends the configuration message to the OpenFlow switch, and the network controller sends a CONFIG message configuring the OAM entity and its related functions to the OpenFlow switch;
the CONFIG message is an OFPT _ SET _ CONFIG message; the OFPT _ SET _ CONFIG message includes: configuring the corresponding node type, OAM type and Sub-TLV type, and configuring version number, MD level and whether OAM function is started in the Sub-TLV.
5. The method according to claim 2, wherein the OpenFlow switch reports fault information to a network controller via an ERROR message; wherein the fault information includes: error codes generated in OAM configuration, error codes generated in featuremessages, and error codes generated in CONFIG messages.
6. An apparatus for implementing Ethernet OAM configuration, the apparatus comprising: a network controller, an OpenFlow switch; wherein,
the network controller is used for carrying out capability negotiation with the OpenFlow switch to obtain an OAM type supported by the OpenFlow switch; sending a configuration message to the OpenFlow switch according to the OAM type supported by the OpenFlow switch;
the OpenFlow switch is used for creating an OAM entity and function configuration thereof after receiving the configuration message.
7. The apparatus of claim 6, wherein the OpenFlow switch is further configured to monitor an Ethernet LSP after OAM is created, and report a fault information to a network controller.
8. The apparatus according to claim 6 or 7, wherein the network controller is configured to perform capability negotiation with an OpenFlow switch, and comprises:
the network controller sends an OFPT _ FEATURES _ REQUEST REQUEST message to the OpenFlow switch, wherein the capability field Capabilities is OFPC _ OAM _ TYPE;
the OpenFlow switch returns an OFPT _ FEATURES _ REPLY response message to the network controller, wherein the last 8 bits of the Reserved field carry an OAM type field, which indicates that the OpenFlow switch is of an Ethernet OAM type.
9. The apparatus according to claim 6 or 7, wherein the network controller sends the configuration message to the OpenFlow switch, and sends a CONFIG message configuring the OAM entity and its related functions to the OpenFlow switch;
the CONFIG message is an OFPT _ SET _ CONFIG message; the OFPT _ SET _ CONFIG message includes: configuring the corresponding node type, OAM type and Sub-TLV type, and configuring version number and MD level in the Sub-TLV, and whether to start OAM function.
10. The apparatus of claim 7, wherein the OpenFlow switch reports fault information to a network controller via an ERROR message; wherein the fault information includes: error codes generated in OAM configuration, error codes generated in featuremessages, and error codes generated in CONFIG messages.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310724458.7A CN104734876A (en) | 2013-12-24 | 2013-12-24 | Ethernet OAM configuration achieving method and device |
| PCT/CN2014/080603 WO2015096426A1 (en) | 2013-12-24 | 2014-06-24 | Ethernet oam configuration method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310724458.7A CN104734876A (en) | 2013-12-24 | 2013-12-24 | Ethernet OAM configuration achieving method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104734876A true CN104734876A (en) | 2015-06-24 |
Family
ID=53458333
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310724458.7A Withdrawn CN104734876A (en) | 2013-12-24 | 2013-12-24 | Ethernet OAM configuration achieving method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN104734876A (en) |
| WO (1) | WO2015096426A1 (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016101582A1 (en) * | 2014-12-23 | 2016-06-30 | 中兴通讯股份有限公司 | Method for configuring and implementing operations, administration and maintenance function, and forwarding device |
| WO2017142862A1 (en) * | 2016-02-18 | 2017-08-24 | Idac Holdings, Inc. | Open flow functionality in a software-defined network |
| CN107634895A (en) * | 2016-07-19 | 2018-01-26 | 上海诺基亚贝尔股份有限公司 | For batch operation processing method and equipment based on file or single message |
| CN108259212A (en) * | 2017-05-25 | 2018-07-06 | 新华三技术有限公司 | Message processing method and device |
| CN109981450A (en) * | 2017-12-28 | 2019-07-05 | 中国电信股份有限公司 | Path is connected to maintaining method, device and system |
| CN110166320A (en) * | 2019-05-27 | 2019-08-23 | 盛科网络（苏州）有限公司 | MPLS-TP OAM realization method and system based on OpenFlow interchanger |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111835538B (en) * | 2019-04-17 | 2022-09-02 | 烽火通信科技股份有限公司 | Management method and system for optical communication service and OAM dependency relationship |
| CN113709049A (en) * | 2020-05-20 | 2021-11-26 | 中兴通讯股份有限公司 | Method for creating intermediate point of maintenance entity group, node and readable storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1848757A (en) * | 2005-04-15 | 2006-10-18 | 华为技术有限公司 | Three-layer VPN operation maintenance system and method in communication network |
| CN1897497A (en) * | 2006-05-16 | 2007-01-17 | 中国电信股份有限公司 | Expand operation managing maintenance-ability discovery in Ethernet non-light source network |
| CN101179433A (en) * | 2007-10-24 | 2008-05-14 | 中兴通讯股份有限公司 | Method and system for performing remote management to passive optical network terminal |
| CN102299815A (en) * | 2010-06-22 | 2011-12-28 | 华为技术有限公司 | Configuration method and node of OAM (operation, administration and maintenance) |
| CN102332987A (en) * | 2010-07-12 | 2012-01-25 | 中兴通讯股份有限公司 | Method and system for configuration of OAM attribute of pseudowire |
| US20130010605A1 (en) * | 2011-07-04 | 2013-01-10 | Telefonaktiebolaget L M Ericsson (Publ) | Generic Monitoring Packet Handling Mechanism for OpenFlow 1.1 |
| CN103001887A (en) * | 2012-11-22 | 2013-03-27 | 中兴通讯股份有限公司 | Link keeping alive method, controller and switchboard |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101414925B (en) * | 2007-10-17 | 2011-04-06 | 华为技术有限公司 | Method, system and apparatus for configuring optical network terminal |
| CN102291493B (en) * | 2011-08-25 | 2012-10-03 | 华为终端有限公司 | Method, relevant device and system for configuring application parameter of mobile terminal |
-
2013
- 2013-12-24 CN CN201310724458.7A patent/CN104734876A/en not_active Withdrawn
-
2014
- 2014-06-24 WO PCT/CN2014/080603 patent/WO2015096426A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1848757A (en) * | 2005-04-15 | 2006-10-18 | 华为技术有限公司 | Three-layer VPN operation maintenance system and method in communication network |
| CN1897497A (en) * | 2006-05-16 | 2007-01-17 | 中国电信股份有限公司 | Expand operation managing maintenance-ability discovery in Ethernet non-light source network |
| CN101179433A (en) * | 2007-10-24 | 2008-05-14 | 中兴通讯股份有限公司 | Method and system for performing remote management to passive optical network terminal |
| CN102299815A (en) * | 2010-06-22 | 2011-12-28 | 华为技术有限公司 | Configuration method and node of OAM (operation, administration and maintenance) |
| CN102332987A (en) * | 2010-07-12 | 2012-01-25 | 中兴通讯股份有限公司 | Method and system for configuration of OAM attribute of pseudowire |
| US20130010605A1 (en) * | 2011-07-04 | 2013-01-10 | Telefonaktiebolaget L M Ericsson (Publ) | Generic Monitoring Packet Handling Mechanism for OpenFlow 1.1 |
| CN103001887A (en) * | 2012-11-22 | 2013-03-27 | 中兴通讯股份有限公司 | Link keeping alive method, controller and switchboard |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016101582A1 (en) * | 2014-12-23 | 2016-06-30 | 中兴通讯股份有限公司 | Method for configuring and implementing operations, administration and maintenance function, and forwarding device |
| WO2017142862A1 (en) * | 2016-02-18 | 2017-08-24 | Idac Holdings, Inc. | Open flow functionality in a software-defined network |
| CN107634895A (en) * | 2016-07-19 | 2018-01-26 | 上海诺基亚贝尔股份有限公司 | For batch operation processing method and equipment based on file or single message |
| US10798204B2 (en) | 2016-07-19 | 2020-10-06 | Alcatel Lucent | File based or single message based bulk operation processing method and device |
| CN108259212A (en) * | 2017-05-25 | 2018-07-06 | 新华三技术有限公司 | Message processing method and device |
| CN108259212B (en) * | 2017-05-25 | 2019-09-17 | 新华三技术有限公司 | Message processing method and device |
| CN109981450A (en) * | 2017-12-28 | 2019-07-05 | 中国电信股份有限公司 | Path is connected to maintaining method, device and system |
| CN109981450B (en) * | 2017-12-28 | 2021-06-15 | 中国电信股份有限公司 | Path communication maintenance method, device and system |
| CN110166320A (en) * | 2019-05-27 | 2019-08-23 | 盛科网络（苏州）有限公司 | MPLS-TP OAM realization method and system based on OpenFlow interchanger |
| CN110166320B (en) * | 2019-05-27 | 2022-06-21 | 苏州盛科通信股份有限公司 | MPLS-TP OAM implementation method and system based on OpenFlow switch |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2015096426A1 (en) | 2015-07-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104734876A (en) | Ethernet OAM configuration achieving method and device | |
| EP2595350B1 (en) | GMPLS based OAM provisioning | |
| EP1986370B1 (en) | Control system, data message transmission method and network device in the ethernet | |
| EP2441219B1 (en) | Power-saving functions in communications networks | |
| EP1895721B1 (en) | Method and apparatus for end-to-end link detection and policy routing switching | |
| EP2075966B1 (en) | Method and apparatus for computing a service path | |
| WO2016165463A1 (en) | Software defined network-based link failure reporting method and forwarding device | |
| US9270564B2 (en) | System and method for congestion notification in an ethernet OAM network | |
| JP2013502779A (en) | Bandwidth information notification method, service processing method, network node, and communication system | |
| WO2013185567A1 (en) | Apparatus and method for protecting and switching packet transport network | |
| EP2555469B1 (en) | Fault protection method and device | |
| CN110351141B (en) | Flexe interface management method, device and network element | |
| CN102238067B (en) | Switching method and device on Rapid Ring Protection Protocol (RRPP) ring | |
| EP3461080A1 (en) | Topology determination method, message response method, controller and switch | |
| US7860090B2 (en) | Method for processing LMP packets, LMP packet processing unit and LMP packet processing node | |
| RU2678713C2 (en) | Method of configuring and implementing function of operation, administration and maintenance, and also transfer device | |
| Takacs et al. | GMPLS RSVP-TE extensions for operations, administration, and maintenance (OAM) configuration | |
| CN106341320A (en) | Business backtracking method and device | |
| EP2654241B1 (en) | Method and system for realizing loopback control through control plane | |
| WO2010020171A1 (en) | Method, system and net element device for alarm performance configuration | |
| JP2010136008A (en) | Network configuration apparatus, management apparatus and communication network | |
| Huang et al. | Key requirements of packet transport network based on MPLS-TP | |
| CN102546361A (en) | Method and device for notifying invalidation of transport plane | |
| WO2007071114A1 (en) | A method for soft rerouting in optical network | |
| Takacs et al. | GMPLS RSVP-TE Extensions for Ethernet Operations, Administration, and Maintenance (OAM) Configuration |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20150624 |
|
| WW01 | Invention patent application withdrawn after publication |