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
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 the configuration management technology in Ethernet (Ethernet), particularly relate in a kind of open flows (OpenFlow) and realize Ethernet operation, the method that configures of management and utilization (Operations, Administration andMaintenance, OAM) and device.
Background technology
In prior art, software defined network (Software-Defined Network, SDN) is that a kind of new network proposed by clean slate seminar of Stanford Univ USA innovates framework.Particularly, the data path of this network bottom layer, if switch, router etc. are " mute, simple, minimum ", by define one opening, about stream table, public application programming interface (ApplicationProgramming Interface, API), can programme at the cofree API calling bottom of network controller simultaneously, achieve the innovation of network.
At present, the core technology OpenFlow agreement of SDN, by the chain of command of the network equipment and data surface being separated, realizes the flexible control of network traffics, for the innovation of core network and application provides good platform.In SDN, the OpenFlow switch used comprises stream table, escape way and OpenFlow agreement three part; Wherein,
Escape way connects the interface of OpenFlow switch to network controller, network controller is by this Interface Controller and management OpenFlow switch, and network controller receives the event from OpenFlow switch and sends packet to OpenFlow switch simultaneously; OpenFlow switch is communicated by escape way with network controller, and the form that all interactive information must specify according to OpenFlow agreement performs.
OpenFlow agreement is used for the standard of the mutual information used between network controller and OpenFlow switch that describes and the interface standard of network controller and OpenFlow switch; The core of OpenFlow agreement is the set for OpenFlow protocol information structure; OpenFlow agreement supports three kinds of information types: controller--switch (Controller-to-Switch), asynchronous (Asynchronous) and symmetrical (Symmetric), each type has multiple subtype.Wherein, Controller-to-Switch information is initiated by network controller and is directly used in the state detecting OpenFlow switch; Asynchronous information is initiated by OpenFlow switch and is generally used for upgrading the network event of network controller and changes the state of OpenFlow switch; Symmetric information can be initiated by network controller or OpenFlow switch when not asking.
At present, OpenFlow agreement, as network controller in SDN and the interface protocol between OpenFlow switch, can realize control and forward separating by the control of convection current table, thus realizes the service connection correlation function of OpenFlow switch.But, in conventional transmission network technology, the monitoring of fault and reporting, the triggerings of Restoration Mechanism etc. are all most important, comprise space to exchange, dense wave division multipurpose (DenseWavelength Division Multiplexing, DWDM), time division multiplexing (Time DivisionMultiplexing, TDM) and Ethernet based on operator backbone bridging technology (the Provider Backbone Bridging-Traffic Engineering of Traffic Engineering extensions, and multiprotocol label switching (Multi-Protocol Label Switching PBB-TE), MPLS) technology etc.In these techniques, OAM(Operation Administration Maintenance) can be used to monitor the performance connected, the Restoration Mechanism of trigger data plane, such as: in Ethernet PBB-TE technology, Ethernet connects fault management (Connectivity Fault Management, CFM) define and connect monitoring OAM stream, be used for detecting the survivability of ethernet network; OAM is function indispensable in transmission network.Therefore, the function of OAM needs be activated actively or passively and be consistent with linkage function, prevents the generation of false alarms, and ensures the consistency of operation.In some technology, need to be configured operation to OAM entity, the network user must according to some function of type selecting OAM connected, can OAM configuration parameter, and can activate OAM(Operation Administration Maintenance) at any time.In mpls protocol, need the automation dynamic monitoring function supporting LSP, especially when the number of LSP is very large, dynamic OAM configuration seems particularly important.In order to achieve the above object, OAM entity and correlation function thereof need to realize dynamic-configuration.
In prior art, chain of command uses RSVP (the ResourceReservation Protocol based on Traffic Engineering extensions, RSVP-TE) signaling message realizes the dynamic-configuration of OAM(Operation Administration Maintenance), and in current OpenFlow agreement, not corresponding expansion realizes the relevant function of Ethernet OAM dynamic-configuration.Therefore, the enterprising line correlation expansion on the basis of OpenFlow agreement is needed, to realize OAM configuration feature in Ethernet Transport Network Technique.
Summary of the invention
In view of this, the embodiment of the present invention, desirable to provide a kind of method and the device that realize Ethernet OAM configuration, makes OpenFlow switch can support Ethernet OAM(Operation Administration Maintenance).
For achieving the above object, technical scheme of the present invention is achieved in that
Embodiments provide a kind of method realizing Ethernet OAM and configure, the method comprises:
Carry out capability negotiation between network controller and OpenFlow switch, obtain the OAM type that OpenFlow switch is supported;
The OAM type that network controller is supported according to OpenFlow switch sends configuration messages to OpenFlow switch;
After OpenFlow switch receives configuration messages, create OAM entity and functional configuration thereof.
In such scheme, after described method also comprises OpenFlow switch establishment OAM, monitoring Ethernet label switching path LSP, and to network controller reporting fault information.
In such scheme, carry out capability negotiation between described network controller and OpenFlow switch, comprising:
Network controller sends OFPT_FEATURES_REQUEST request message to OpenFlow switch, and wherein, capable field Capabilities is OFPC_OAM_TYPE;
OpenFlow switch returns OFPT_FEATURES_REPLY response message to network controller, and wherein, rear 8 bits of reserved field Reserved carry OAM type field, shows that described OpenFlow switch is Ethernet OAM type.
In such scheme, it is that network controller sends the CONFIG message of configuration OAM entity and correlation function thereof to OpenFlow switch that described network controller sends configuration messages to OpenFlow switch;
Described CONFIG message is OFPT_SET_CONFIG message; Described OFPT_SET_CONFIG message comprises: configure configuration version number, MD rank in respective nodes type, OAM type and Sub-TLV type and Sub-TLV, whether open OAM(Operation Administration Maintenance).
In such scheme, described OpenFlow switch passes through ERROR message to network controller reporting fault information; Wherein, described fault message comprises: the error code produced in the error code produced in OAM configuration, the error code produced in FEATURE message and CONFIG message.
The embodiment of the present invention additionally provides a kind of device realizing Ethernet OAM and configure, and this device comprises: network controller, OpenFlow switch; Wherein,
Described network controller, for and OpenFlow switch between carry out capability negotiation, obtain the OAM type that OpenFlow switch is supported; Configuration messages is sent to OpenFlow switch according to the OAM type that OpenFlow switch is supported;
Described OpenFlow switch, after receiving configuration messages, creates OAM entity and functional configuration thereof.
In such scheme, described OpenFlow switch also for after creating OAM, monitoring Ethernet LSP, and to network controller reporting fault information.
In such scheme, described network controller is used for carrying out capability negotiation between OpenFlow switch, comprising:
Network controller sends OFPT_FEATURES_REQUEST request message to OpenFlow switch, and wherein, capable field Capabilities is OFPC_OAM_TYPE;
OpenFlow switch returns OFPT_FEATURES_REPLY response message to network controller, and wherein, rear 8 bits of reserved field Reserved carry OAM type field, shows that described OpenFlow switch is Ethernet OAM type.
In such scheme, it is that network controller sends the CONFIG message of configuration OAM entity and correlation function thereof to OpenFlow switch that described network controller sends configuration messages to OpenFlow switch;
Described CONFIG message is OFPT_SET_CONFIG message; Described OFPT_SET_CONFIG message comprises: configure configuration version number, MD rank in respective nodes type, OAM type and Sub-TLV type and Sub-TLV, whether open OAM(Operation Administration Maintenance).
In such scheme, described OpenFlow switch passes through ERROR message to network controller reporting fault information; Wherein, described fault message comprises: the error code produced in the error code produced in OAM configuration, the error code produced in FEATURE message and CONFIG message.
Method that Ethernet OAM configures that what the embodiment of the present invention provided realize and device, by carrying out capability negotiation between network controller and OpenFlow switch; Send configuration messages by network controller to OpenFlow switch, after OpenFlow switch receives configuration messages, create OAM entity and functional configuration thereof; Further, after establishment OAM, OpenFlow switch monitoring Ethernet label switched path (Label Switched Path, LSP), and to network controller reporting fault information.So, by improving the handling process of OAM configuration in OpenFlow agreement, increasing and expanding accordingly, under the prerequisite following existing OpenFlow agreement, realize Ethernet OAM and configure correlation function, make OpenFlow switch can support Ethernet OAM(Operation Administration Maintenance).
Accompanying drawing explanation
Fig. 1 is OAM extended format schematic diagram in RSVP-TE;
Fig. 2 is OAM Sub-TLV form schematic diagram;
Fig. 3 is Ethernet OAM Sub-TLV form schematic diagram;
Fig. 4 is MD Name Sub-TLV form schematic diagram in Ethernet OAM;
Fig. 5 is Short MA Name Sub-TLV form schematic diagram in Ethernet OAM;
Fig. 6 is MEP ID Sub-TLV form schematic diagram in Ethernet OAM;
Fig. 7 is CC Sub-TLV form schematic diagram in Ethernet OAM;
Fig. 8 is the Ethernet LSP network diagram under SDN framework;
Fig. 9 is the method handling process schematic diagram that the embodiment of the present invention realizes Ethernet OAM configuration;
Figure 10 is the concrete handling process schematic diagram of method that the embodiment of the present invention realizes Ethernet OAM configuration;
Figure 11 is that OAM capability negotiation is at FEATURES extension of message schematic diagram;
Figure 12 is that OAM is configured in CONFIG extension of message schematic diagram;
Figure 13 is the expansion schematic diagram that Ethernet OAM Sub-TLV configures;
Figure 14 is that Ethernet OAM MD Name Sub-TLV expands schematic diagram;
Figure 15 is that Ethernet OAM Short MA Name Sub-TLV expands schematic diagram;
Figure 16 is that Ethernet OAM MEP ID Sub-TLV expands schematic diagram;
Figure 17 is that Ethernet OAM CC Sub-TLV expands schematic diagram;
Figure 18 is the device composition structural representation that the embodiment of the present invention realizes Ethernet OAM configuration.
Embodiment
In actual applications, the configuration of OAM mainly comprises: create OAM entity and functional configuration, OAM parameter adjustment and delete OAM entity.
Concrete, the realization of described establishment OAM entity and functional configuration thereof comprises:
Maintenance Point (Maintenance Points, MP) comprises to be safeguarded end node (Maintenance EndPoints, MEP) and safeguards intermediate node (Maintenance Intermediate Points, MIP); Wherein, MEP is in the two ends of connection, can initiate and stop the OAM message for fault management (Fault Management, FM) and performance monitoring (Performance Monitoring, PM); MIP is in the intermediate node of connection, can only receive OAM message.
Maintenance entity (Maintenance Entity, ME), as the cooperation between MEP and MIP, is used for monitoring connection; As long as the connection establishment between MEP and MIP completes, the forwarding relation between end points and intermediate node is set up, and this contact makes OAM entity monitor LSP.
Except the relevant parameter of MP and ME definition, initiatively OAM(Operation Administration Maintenance) such as consistency detection (Continuity Check, CC) and PM need parameter configuration; These parameters can configure before connection establishment, also can obtain when connection establishment.
In prior art, RSVP-TE is utilized to realize OAM configuration flow as follows:
Fig. 1 is OAM extended format schematic diagram in RSVP-TE, and as shown in Figure 1, OAM type shows the OAM entity type creating node support; When creating OAM entity, node device does not support OAM type, then need to return error code " OAM Problem/Unsupported OAM Type ".
Fig. 2 is the form schematic diagram of OAM Sub-TLV, as shown in Figure 2, in OAM Sub-TLV, the implication that OAM Function Flag gets different value is as follows: 0 is CC function, 1 is detection of connectivity (Connectivity Verification, CV) function, 2 is fault management signal (Fault ManagementSignal, FMS) function, 3 is PM/Loss(loss) function, 4 is PM/Delay(delay) function, 5 is PM/Throughput Measurement(testing throughput) function.
When OAM creates, between node, need capability negotiation.The attribute of node represents in LSP_ATTRIBUTES flag bit, show that this node is MEP or MIP, as " OAM MEP entities desired " bit set shows that this node is MEP, " OAM MIP entities desired " bit set is shown to be MIP.ADMIN_STATUS flag bit " OAM Alarms Enabled " shows whether open OAM alarm, shows to open OAM alarm function when this flag bit set.
The realization of described OAM parameter adjustment comprises: for the OAM(Operation Administration Maintenance) creating and configure, and may need parameter adjustment in the life cycle of LSP, now, just needs to upgrade OAM parameter.Wherein, OAM parameters relationship, to the content of OAM message and duration, is also related to OAM and detects, obtain and produce the mode of alarm; Therefore, the source of OAM and tail end need synchronized update data.
First, the alarm function of OAM is prohibited, and ADMIN_STATUS flag bit " OAM AlarmsEnabled " is cleared; Next, then adjust OAM parameter.After the renewal of OAM parameter is complete, ADMIN_STATUS flag bit " OAM Alarms Enabled " is set.
The realization that described OAM entity is deleted comprises: in some cases, needs deletion or all OAM entities and function, and does not affect the connection of having set up.First, the alarm function of OAM is prohibited, ADMIN_STATUS flag bit " OAM Alarms Enabled " is cleared, and in LSP_ATTRIBUTES flag bit, " OAM MEP entities desired " bit and " OAM MIP entities desired " bit reset; Afterwards, the deletion of OAM entity is automatically triggered.
Functional configuration below for Ethernet OAM is briefly described.
In order to simplify the configuration connecting and detect, when Ethernet LSP sets up, need to create Ethernet OAM, the two ends in bi-directional point to multipoint PBB-TE connects all need to configure MEP simultaneously.When MEP monitors PBB-TE connection, need configuring maintenance territory rank (Maintenance Domain Level, MD rank) and maintenance association identifier (Maintenance Association Identifier, MAID); Each MEP has unique MEP ID; At intermediate node place, need to configure MIP, for fault location, as: link trace and loop detection function.
In Ethernet OAM, except configuring above-mentioned basic OAM parameter, also need distinctive following relevant parameter in configuration ethernet:
1) need two MEP connected for PBB-TE to distribute unique MAID, MAID comprises optional MD Name and Short MA Name;
2) each MEP needs distribution MEP ID, and MAID and MEP ID can define a unique MEP;
3) MD rank can allow the layering of monitoring entity to isolate;
4) forwarding priority;
5) MEP needs to know that oneself and far-end can arrive the parameter information of MEP.
Fig. 3 is Ethernet OAM Sub-TLV form schematic diagram, and as shown in Figure 3, in Ethernet OAM configuration parameter, the value of OAM type is 1, is defined as Ethernet OAM type; Version is CFM protocol version; MD.L is MD rank; Sub-TLV can carry the Sub-TLV type of ethernet feature.
Fig. 4 is MD Name Sub-TLV form schematic diagram in Ethernet, and as shown in Figure 4, Type is defined as 1, is indicated as MD Name Sub-TLV.
Fig. 5 is Short MA Name Sub-TLV form schematic diagram in Ethernet, and as shown in Figure 5, Type is 2, is indicated as Short MA Name Sub-TLV.
Fig. 6 is MEP ID Sub-TLV form schematic diagram in Ethernet OAM, and as shown in Figure 6, Type is 3, is indicated as MEP ID Sub-TLV; Local MEP ID is local MEP ID, 16 bit integer types, and scope is 1-8191; Remote MEP ID is the MEP ID of opposite end, 16 bit integer types, and scope is 1-8191; T bit and R bit, when MEP gives out a contract for a project, the set of T bit, when MEP packet receiving, the set of R bit.
Fig. 7 is CC Sub-TLV form schematic diagram in Ethernet OAM, and as shown in Figure 7, Type is 3, is indicated as the Sub-TLV of CC type; Prio is defined as the priority of CCM frame; CCM I is defined as the gap of CCM.
In addition, in Ethernet OAM configures, also definition has following type of error:
1) when node does not support certain CFM version, return " OAM Problem/Unsupported OAMVersion ";
2) when node does not support certain MD rank, return " OAM Problem/Unsupported MDLevel ";
3) when node receives a undefined MD Name form, return " OAM Problem/Unknown MD Name Format ";
4) when node receives a undefined MA Name form, return " OAM Problem/Unknown MA Name Format ";
5) when the total length of MD Name and MA Name is less than or equal to 44 byte, return " OAMProblem/Name Length Problem ";
6) when node does not support the CCM gap of asking, return " OAM Problem/Unsupported CCInterval ".
Based on introduction and the analysis of above-mentioned concept, in embodiments of the present invention, between network controller and OpenFlow switch, carry out capability negotiation, obtain the OAM type that OpenFlow switch is supported; The OAM type that network controller is supported according to OpenFlow switch sends configuration messages to OpenFlow switch; After OpenFlow switch receives configuration messages, create OAM entity and functional configuration thereof.
Further, after creating OAM, OpenFlow switch monitoring Ethernet LSP, and to network controller reporting fault information.
Here, in conventional transmission network, OAM configuration is completed between node by signaling method, and under SDN framework, need to set up Ethernet LSP by the OpenFlow protocol interface between network controller and OpenFlow switch to OpenFlow switch, as shown in Figure 8, Fig. 8 is the Ethernet LSP network diagram under SDN framework.
Below in conjunction with drawings and the specific embodiments, the present invention is further described in more detail.
Fig. 9 is the handling process schematic diagram that the embodiment of the present invention realizes the method that Ethernet OAM configures, and as shown in Figure 9, the method that the embodiment of the present invention realizes Ethernet OAM configuration comprises:
Step S100: carry out capability negotiation between network controller and OpenFlow switch, obtains the OAM type that OpenFlow switch is supported;
Here, between network controller and OpenFlow switch, carry out capability negotiation, completed by FEATURES message in OpenFlow agreement.
Step S101: the OAM type that network controller is supported according to OpenFlow switch sends configuration messages to OpenFlow switch;
Here, network controller sends the CONFIG message of configuration OAM entity and correlation function thereof to OpenFlow switch.
After step S102:OpenFlow switch receives configuration messages, create OAM entity and functional configuration thereof.
Under SDN framework, the Ethernet LSP business needing network controller to be issued between OpenFlow switch by OpenFlow interface sets up request, and wherein, internodal connection establishment completes by flowing the form showing to issue.
Here, OAM configuration can business set up before complete, also can set up with business and complete simultaneously, therefore, the establishment mode of OAM entity is: before stream table issues establishment, or when stream table issues together with create.
Figure 10 is the concrete handling process schematic diagram that the embodiment of the present invention realizes the method that Ethernet OAM configures, and as shown in Figure 10, the method that the embodiment of the present invention realizes Ethernet OAM configuration specifically comprises:
Step S200: network controller sends OFPT_FEATURES_REQUEST request message to OpenFlow switch;
Wherein, capable field Capabilities is OFPC_OAM_TYPE.
Here, OAM capability negotiation can expand a kind of OAM capability class OFPC_OAM_TYPE=1<<4 at the Capabilities of OFPT_FEATURES_REQUEST request message, as shown in figure 11, for OAM capability negotiation is at FEATURES extension of message schematic diagram.
Step S201:OpenFlow switch returns OFPT_FEATURES_REPLY response message to network controller;
Wherein, rear 8 bits of reserved field Reserved carry OAM type field, show that described OpenFlow switch is Ethernet OAM type.
Step S202: network controller sends the CONFIG message of configuration OAM entity and correlation function thereof to OpenFlow switch;
Here, described CONFIG message is OFPT_SET_CONFIG message; Described OFPT_SET_CONFIG message comprises: configure configuration version number, MD rank in respective nodes type, OAM type and Sub-TLV type and Sub-TLV, whether open OAM(Operation Administration Maintenance) etc.;
Wherein, configuration respective nodes type comprises MEP type and MIP type, and OAM type can be Ethernet OAM Configuration Type.
After step S203:OpenFlow switch receives configuration messages, create OAM entity and functional configuration thereof;
Figure 12 is that OAM is configured in CONFIG extension of message schematic diagram, and as shown in figure 12, OAM is configured in before business is set up according to OFPT_SET_CONFIG message arrangement OAM; The type of expansion flags field, namely in enumeration type ofp_config_flags, OFPC_FRAG_OAM=1<<2 represents OAM configuration messages; Extended field in the structure ofp_switch_config of OFPT_SET_CONFIG message, is respectively Node Type, 8 bits, for showing that this node is MEP(Node Type=1) or MIP(Node is Type=2); OAM Type, 8 bits, for showing the type of OAM, OAM Type=1 is Ethernet OAM type; OAM Alarms Enabled, 8 bits, whether be used to indicate OAM and open, set, reset and represent closedown if representing unlatching; Sub-TLV Type, 8 bits, show the type of Sub-TLV; Sub-TLV, random length, the type according to OAM is configured.
Figure 13 is the expansion schematic diagram that Ethernet OAM Sub-TLV configures, and as shown in figure 13, Version is CFM protocol version; MD.L is MD rank; Sub-TLV can carry the Sub-TLV type of ethernet feature.
Figure 14 is that Ethernet OAM MD Name Sub-TLV expands schematic diagram, and as shown in figure 14, Type is defined as 1, is indicated as MD Name Sub-TLV.
Figure 15 is that Ethernet OAM Short MA Name Sub-TLV expands schematic diagram, and as shown in figure 15, Type is 2, is indicated as Short MA Name Sub-TLV.
Figure 16 is that Ethernet OAM MEP ID Sub-TLV expands schematic diagram, and as shown in figure 16, Type is 3, is indicated as MEP ID Sub-TLV; Local MEP ID is local MEP ID, 16 bit integer types, and scope is 1-8191; Remote MEP ID is the MEP ID of opposite end, 16 bit integer types, and scope is 1-8191; T bit and R bit, when MEP gives out a contract for a project, the set of T bit, when MEP packet receiving, the set of R bit.
Figure 17 is that Ethernet OAM CC Sub-TLV expands schematic diagram, and as shown in figure 17, Type is 4, is indicated as the Sub-TLV of consistency detection CC; Prio is defined as the priority of CCM frame; CCM I is defined as the gap of CCM.
After step S204:OpenFlow switch creates OAM, monitoring Ethernet LSP, and to network controller reporting fault information.
Here, OpenFlow switch passes through ERROR message to network controller reporting fault information; Wherein, described fault message comprises: the error code produced in the error code produced in OAM configuration, the error code produced in FEATURE message and CONFIG message.
Particularly, the error code produced in OAM configuration needs to expand in ERROR, needs to increase new subtype in the corresponding type of error of ERROR, in ofp_error_type enumeration type, adds corresponding error code.
The error code type produced in FEATURE message needs to increase subtype error code in OFPET_BAD_REQUEST type of error; Wherein,
OFPBRC_UNSUPPORTED_OAM_TYPE=14, shows the request not supporting this OAM type.
The type of error produced in CONFIG message, increases subtype error code in OFPET_SWITCH_CONFIG_FAILED type of error; Wherein,
OFPSCFC_UNSUPPORTED_OAM_VERSION=3, shows the configuration not supporting this OAM version;
OFPSCFC_UNSUPPORTED_MD_LEVEL=4, shows not support this MD rank;
OFPSCFC_UNKNOWN_MD_NAME_FORMAT=5, shows unknown MD Name form.
OFPSCFC_UNKNOWN_MA_NAME_FORMAT=6, shows unknown MA Name form;
OFPSCFC_WRONG_NAME_LENGTH=7, shows the NAME length of mistake;
OFPSCFC_UNSUPPORTED_CCM_INTERVAL=8, shows not support this CCM gap.
Figure 18 is the device composition structural representation that the embodiment of the present invention realizes Ethernet OAM configuration, and as shown in figure 18, the embodiment of the present invention realizes the device that Ethernet OAM configures, and comprising: network controller 10, OpenFlow switch 11; Wherein,
Described network controller 10, for carrying out capability negotiation between OpenFlow switch 11, obtains the OAM type that OpenFlow switch is supported; OAM type according to the support of OpenFlow switch sends configuration messages to OpenFlow switch 11;
Here, carry out between described network controller 10 and OpenFlow switch 11 capability negotiation by OpenFlow agreement in FEATURES message complete.
Particularly, described network controller 10 sends OFPT_FEATURES_REQUEST request message to OpenFlow switch 11, and wherein, capable field Capabilities is OFPC_OAM_TYPE;
Here, OAM capability negotiation can expand a kind of OAM capability class OFPC_OAM_TYPE=1<<4 at the Capabilities of OFPT_FEATURES_REQUEST request message.
Correspondingly, described OpenFlow switch 11 returns OFPT_FEATURES_REPLY response message to network controller 10, wherein rear 8 bits of reserved field Reserved carry OAM type field, show that described OpenFlow switch 11 is Ethernet OAM type.
Here, described network controller 10 sends the CONFIG message of configuration OAM entity and correlation function thereof to OpenFlow switch 11.
Particularly, described CONFIG message is OFPT_SET_CONFIG message; Described OFPT_SET_CONFIG message comprises: configure configuration version number, MD rank in respective nodes type, OAM type and Sub-TLV type and Sub-TLV, whether open OAM(Operation Administration Maintenance) etc.
Wherein, configuration respective nodes type comprises MEP type and MIP type, and OAM type can be Ethernet OAM Configuration Type.
Described OpenFlow switch 11, after receiving configuration messages, creates OAM entity and functional configuration thereof.
Described OpenFlow switch 11, also for after creating OAM, monitoring Ethernet LSP, and to controller 10 reporting fault information.
Here, described OpenFlow switch 11 passes through ERROR message to network controller 10 reporting fault information; Wherein, described fault message comprises the error code produced in the error code produced in OAM configuration, the error code produced in FEATURE message and CONFIG message.
In foregoing description, all for a network controller and an OpenFlow switch, present invention is described.In the OpenFlow agreement of practical application, can be realize Ethernet OAM between a network controller and multiple OpenFlow switch to configure.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.
Claims (10)
1. realize the method that Ethernet Ethernet OAM configures, it is characterized in that, described method comprises:
Carry out capability negotiation between network controller and OpenFlow switch, obtain the OAM type that OpenFlow switch is supported;
The OAM type that network controller is supported according to OpenFlow switch sends configuration messages to OpenFlow switch;
After OpenFlow switch receives configuration messages, create OAM entity and functional configuration thereof.
2. method according to claim 1, is characterized in that, described method also comprises: after OpenFlow switch creates OAM, monitoring Ethernet label switching path LSP, and to network controller reporting fault information.
3. method according to claim 1 and 2, is characterized in that, carries out capability negotiation, comprising between described network controller and OpenFlow switch:
Network controller sends OFPT_FEATURES_REQUEST request message to OpenFlow switch, and wherein, capable field Capabilities is OFPC_OAM_TYPE;
OpenFlow switch returns OFPT_FEATURES_REPLY response message to network controller, and wherein, rear 8 bits of reserved field Reserved carry OAM type field, shows that described OpenFlow switch is Ethernet OAM type.
4. method according to claim 1 and 2, is characterized in that, it is that network controller sends the CONFIG message of configuration OAM entity and correlation function thereof to OpenFlow switch that described network controller sends configuration messages to OpenFlow switch;
Described CONFIG message is OFPT_SET_CONFIG message; Described OFPT_SET_CONFIG message comprises: configure configuration version number, MD rank in respective nodes type, OAM type and Sub-TLV type and Sub-TLV, whether open OAM(Operation Administration Maintenance).
5. method according to claim 2, is characterized in that, described OpenFlow switch passes through ERROR message to network controller reporting fault information; Wherein, described fault message comprises: the error code produced in the error code produced in OAM configuration, the error code produced in FEATURE message and CONFIG message.
6. realize the device that Ethernet Ethernet OAM configures, it is characterized in that, described device comprises: network controller, OpenFlow switch; Wherein,
Described network controller, for and OpenFlow switch between carry out capability negotiation, obtain the OAM type that OpenFlow switch is supported; Configuration messages is sent to OpenFlow switch according to the OAM type that OpenFlow switch is supported;
Described OpenFlow switch, after receiving configuration messages, creates OAM entity and functional configuration thereof.
7. device according to claim 6, is characterized in that, described OpenFlow switch, also for after creating OAM, and monitoring Ethernet LSP, and to network controller reporting fault information.
8. the device according to claim 6 or 7, is characterized in that, described network controller is used for carrying out capability negotiation between OpenFlow switch, comprising:
Network controller sends OFPT_FEATURES_REQUEST request message to OpenFlow switch, and wherein, capable field Capabilities is OFPC_OAM_TYPE;
OpenFlow switch returns OFPT_FEATURES_REPLY response message to network controller, and wherein, rear 8 bits of reserved field Reserved carry OAM type field, shows that described OpenFlow switch is Ethernet OAM type.
9. the device according to claim 6 or 7, is characterized in that, it is that network controller sends the CONFIG message of configuration OAM entity and correlation function thereof to OpenFlow switch that described network controller sends configuration messages to OpenFlow switch;
Described CONFIG message is OFPT_SET_CONFIG message; Described OFPT_SET_CONFIG message comprises: configure configuration version number, MD rank in respective nodes type, OAM type and Sub-TLV type and Sub-TLV, whether open OAM(Operation Administration Maintenance).
10. device according to claim 7, is characterized in that, described OpenFlow switch passes through ERROR message to network controller reporting fault information; Wherein, described fault message comprises: the error code produced in the error code produced in OAM configuration, the error code produced in FEATURE message and CONFIG message.
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 (1)
| 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 |
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 | |
| JP6748258B2 (en) | How to establish a relationship between a set of label switch paths and a virtual network | |
| JP5813072B2 (en) | Method and apparatus for providing full logical connectivity in an MPLS network | |
| US9769054B2 (en) | Network topology discovery method and system | |
| EP2075966B1 (en) | Method and apparatus for computing a service path | |
| EP2680510B1 (en) | Service plane triggered fast reroute protection | |
| EP1986370B1 (en) | Control system, data message transmission method and network device in the ethernet | |
| CN101505227B (en) | Method, device and system for implementing point to multi-point pseudowire | |
| CN102299815B (en) | Configuration method and node of OAM (operation, administration and maintenance) | |
| US9843502B2 (en) | Routing of point-to-multipoint services in a multi-domain network | |
| EP2441219A1 (en) | Power-saving functions in communications networks | |
| WO2015035616A1 (en) | Method and device for cross-network communications | |
| CN107645394B (en) | Switch configuration method in SDN network | |
| CN102868569A (en) | Method, node and system for detecting performance of three-layer virtual private network | |
| Choi | Design and implementation of a PCE-based software-defined provisioning framework for carrier-grade MPLS-TP networks | |
| WO2007019758A1 (en) | A method, system and apparatus for implementing traffic engineering | |
| Wang et al. | A multi-domain SDN scalability architecture implementation based on the coordinate controller | |
| WO2012142753A1 (en) | Method and device for monitoring ip bearer network performance | |
| CN104219068A (en) | Method of channel fault notification and network equipment | |
| EP3223455A1 (en) | Method for configuring and implementing operations, administration and maintenance function, and forwarding device | |
| Jing et al. | Experimental demonstration of hierarchical control over multi-domain OTN networks based on extended OpenFlow protocol | |
| CN100370748C (en) | Method of implementing synchronization of topology resource information between bearer networks | |
| Takacs et al. | GMPLS controlled Ethernet: An emerging packet-oriented transport technology | |
| WO2010020171A1 (en) | Method, system and net element device for alarm performance configuration | |
| JP6472942B2 (en) | Switching control device, switching control method, and switching control program |
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 |