WO2017219957A1 - 故障类型的确定方法和装置、存储介质 - Google Patents

故障类型的确定方法和装置、存储介质 Download PDF

Info

Publication number
WO2017219957A1
WO2017219957A1 PCT/CN2017/089146 CN2017089146W WO2017219957A1 WO 2017219957 A1 WO2017219957 A1 WO 2017219957A1 CN 2017089146 W CN2017089146 W CN 2017089146W WO 2017219957 A1 WO2017219957 A1 WO 2017219957A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
identifier
flow table
group
determining
Prior art date
Application number
PCT/CN2017/089146
Other languages
English (en)
French (fr)
Inventor
张平平
孙军欢
陈志伟
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017219957A1 publication Critical patent/WO2017219957A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J3/00—Circuit arrangements for ac mains or ac distribution networks

Definitions

  • the present invention relates to the field of the Internet, and in particular to a method and apparatus for determining a fault type, and a storage medium.
  • SDN Software Defined Network
  • Emulex network is a new network innovation architecture of Emulex network. It is an implementation method of network virtualization. Its core technology OpenFlow separates the control plane of the network device from the data plane. Flexible control of network traffic makes the network more intelligent as a pipeline.
  • OpenFlow is currently the most popular SDN implementation. OpenFlow-based SDN switches rely on internal indexing of multiple flow tables and group tables to implement packet forwarding.
  • the service deployment of the SDN network is automatically delivered by the data packet triggering controller.
  • the widespread application of SDN networks brings revolutionary benefits to service deployment, but it also brings inconvenience to the location of network faults. When a fault occurs, the fault type and fault location cannot be accurately determined, and fault handling cannot be performed in a timely and effective manner.
  • the embodiment of the invention provides a method and a device for determining a fault type and a storage medium, so as to at least solve the technical problem that the fault type cannot be determined in time in the SDN network.
  • a method for determining a fault type comprising: extracting control data recorded on a control board of an SDN switch and maintenance data recorded on a service board of an SDN switch; The data and maintenance data determine abnormal data in the control data; and determine the fault type of the SDN switch based on the abnormal data.
  • extracting the control data recorded on the control board of the SDN switch and the maintenance data recorded on the service board of the SDN switch includes: extracting the first set of table sets and the first flow table set delivered by the control board, and/or, An identifier of a hardware resource associated with the group table in the first set of table sets and an identifier of the hardware resource associated with the flow table in the first flow table set; extracting the second set of table sets and the second flow table received by the service board A set, and/or an identification of a hardware resource associated with a group table in the second set of table sets and an identification of a hardware resource associated with the flow table in the second flow table set.
  • determining the abnormal data in the control data by comparing the control data and the maintenance data includes: obtaining an identifier of any one of the first set of table sets; determining whether the second set of the table set exists with any one of the set of tables A group table having the same identifier; if there is no group table having the same identifier as any of the group tables in the second group of table sets, it is determined that any of the group tables is abnormal data.
  • determining, by comparing the control data and the maintenance data, the abnormal data in the control data includes: obtaining an identifier of any flow table in the first flow table set; determining whether the second flow table set has the same identifier as any flow table The flow table; if there is no flow table with the same identifier as any flow table in the second flow table set, it is determined that any flow table is abnormal data.
  • determining, according to the abnormal data, the fault type of the SDN switch includes: a group table having the same identifier as the abnormal data does not exist in the second group table, or having the same identifier as the abnormal data in the second flow table set In the case of the flow table, it is determined that the fault type of the SDN switch is that the traffic between the control board and the service board is unreachable.
  • determining the abnormal data in the control data by comparing the control data and the maintenance data includes: obtaining an identifier of any one of the first group of the table sets; determining the identifier and the association of the hardware resources associated with any of the group of tables Whether the identifiers of the hardware resources in the target group table are the same, wherein the target group table is a group table in the second group of table sets having the same identifier as any group of tables; if the identifiers and associations of hardware resources associated with any group table are associated If the identifiers of the hardware resources of the target group table are different, it is determined that any of the group tables is abnormal data.
  • determining the abnormal data in the control data by comparing the control data and the maintenance data includes: obtaining an identifier of any flow table in the first flow table set; determining an identifier of the hardware resource associated with any flow table and being associated with the target flow Whether the identifier of the hardware resource of the table is the same, where the target flow table is a flow table in the second flow table that has the same identifier as any of the flow tables; if the identifier of the hardware resource associated with any flow table and the hardware associated with the target flow table If the identifiers of the resources are different, then any flow table is determined to be abnormal data.
  • determining, according to the abnormal data, the fault type of the SDN switch includes: determining, when the identifier of the hardware resource associated with the abnormal data is different from the identifier of the hardware resource associated with the target group table or the target flow table, determining the SDN switch The fault type is incorrect for the traffic encapsulation information.
  • the method further includes: obtaining a log record table of the SDN switch; taking the identifier of the abnormal data as an index, and acquiring the fault information of the SDN switch from the log record table.
  • the method further includes: displaying the abnormal data and the fault information; and/or instructing the control panel to re-issue the corresponding group table and the flow table to repair the SDN switch. malfunction.
  • a fault type determining apparatus comprising: an extracting unit configured to extract a control recorded on a control board of an SDN switch Data and maintenance data recorded on the service board of the SDN switch; the first determining unit is configured to determine abnormal data in the control data by comparing the control data and the maintenance data; and the second determining unit is configured to determine the SDN switch according to the abnormal data The type of failure.
  • the extracting unit includes: a first extracting module, configured to extract a first set of table sets and a first flow table set delivered by the control board, and/or hardware associated with the group table in the first set of table sets An identifier of the resource and an identifier of the hardware resource associated with the flow table in the first flow table set;
  • the second extraction module is configured to extract the second set of the table set and the second flow table set received by the service board, and/or, An identification of a hardware resource associated with a group table in the second set of table sets and an identification of a hardware resource associated with the flow table in the second flow table set.
  • the device further includes: a display unit configured to display the abnormal data and the fault information; and/or a repairing unit, configured to instruct the control panel to re-issue the corresponding group table and the flow table to repair the fault of the SDN switch.
  • a display unit configured to display the abnormal data and the fault information
  • a repairing unit configured to instruct the control panel to re-issue the corresponding group table and the flow table to repair the fault of the SDN switch.
  • a storage medium configurable to store program code for performing the steps of: extracting control data recorded on a control board of an SDN switch and a service board of an SDN switch The recorded maintenance data; the abnormal data in the control data is determined by comparing the control data and the maintenance data; and the fault type of the SDN switch is determined according to the abnormal data.
  • control data recorded on the control board of the SDN switch and the maintenance data recorded on the service board of the SDN switch are extracted; the abnormal data in the control data is determined by comparing the control data and the maintenance data; The data determines the type of failure of the SDN switch. Therefore, the technical problem that the fault type cannot be determined in time in the SDN network is solved, and the technical effect of quickly locating the fault type of the SDN switch is realized.
  • FIG. 1 is a schematic diagram of a computer terminal in accordance with an embodiment of the present invention.
  • FIG. 2 is a flow chart of a method of determining a fault type according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a system architecture in accordance with an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a network device according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method of determining an optional failure type according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a device for determining a failure type according to an embodiment of the present invention.
  • the method embodiment provided in Embodiment 1 of the present application can be executed in a mobile terminal, a computer terminal (such as an SDN switch) or the like.
  • the computer terminal may include one or more (only one shown) processor 101 (the processor 101 may include, but is not limited to, a microprocessor MCU or programmable A processing device such as a logic device FPGA, a memory 103 provided to store data, and a transmission device 105 provided as a communication function.
  • the structure shown in FIG. 1 is merely illustrative and does not limit the structure of the above electronic device.
  • the memory 103 can be configured as a software program and a module for storing application software, such as program instructions/modules corresponding to the control method of the device in the embodiment of the present invention, and the processor 101 executes by executing a software program and a module stored in the memory 103.
  • application software such as program instructions/modules corresponding to the control method of the device in the embodiment of the present invention
  • the processor 101 executes by executing a software program and a module stored in the memory 103.
  • the memory can include high speed random access memory and can also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • the memory can further include memory remotely located relative to the processor, which can be connected to the computer terminal over a network.
  • An example of the above network include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission device is arranged to receive or transmit data via a network.
  • the above-described network specific examples may include a wireless network provided by a communication provider of a computer terminal.
  • the transmission device includes a Network Interface Controller (NIC) that can be connected to other network devices through the base station to communicate with the Internet.
  • the transmission device can be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.
  • NIC Network Interface Controller
  • RF Radio Frequency
  • the technical problems to be solved by the present application include: automatically analyzing faults for fault types such as distributed resource ID conflicts, service traffic forwarding failures, and packet encapsulation errors caused by high CPU utilization in the SDN network environment.
  • Type and implementation of fast recovery services The service deployment on the SDN switch is implemented by directly sending a large number of flow tables and group tables through the controller, which is not conducive to fault location.
  • the time for analyzing the fault type can be greatly saved, and the fault is quickly located.
  • the problem can also achieve rapid recovery of services and reduce user losses caused by equipment failure.
  • the so-called flow table can be regarded as an abstraction of OpenFlow's data forwarding function for network devices.
  • the data forwarding of the switch and the router depends on the Layer 2 MAC address forwarding table or the Layer 3 IP address routing table saved in the device, and the flow table used in the OpenFlow switch adopts a similar manner in its table.
  • the item integrates network configuration information at various levels in the network, so that more rules can be used when forwarding data.
  • a group is an efficient method for OpenFlow to specify the same set of operations in multiple streams for a packet.
  • the corresponding group table includes: group identifier, group type, counter, and action bucket.
  • group table each data stream can be divided into corresponding groups, and the execution of the action instructions can be performed for all data packets belonging to the same group identifier, suitable for implementing broadcast or multicast, or specifying that only certain specifics are performed. Operation set. Among them, the type of the group specifies whether all the instructions in the action bucket will be executed.
  • a method embodiment of a method for determining a fault type is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions. And, although the logical order is shown in the flowchart, In some cases, the steps shown or described may be performed in an order different than that described herein.
  • FIG. 2 is a flowchart of a method for determining a fault type according to an embodiment of the present invention. As shown in FIG. 2, the method includes the following steps:
  • step S201 the control data recorded on the control board of the SDN switch and the maintenance data recorded on the service board of the SDN switch are extracted.
  • Step S202 determining abnormal data in the control data by comparing the control data and the maintenance data.
  • each data in the control data will have a corresponding data in the maintenance data
  • the abnormal data refers to the data existing in the control data
  • the abnormal data can be determined in the following two cases: In one data, there is no data corresponding to any data in the maintenance data, or data corresponding to any data exists in the maintenance data, but the information described in the data does not match the data recorded in any of the data.
  • Step S203 determining a fault type of the SDN switch according to the abnormal data.
  • the control data recorded on the control board of the SDN switch and the maintenance data recorded on the service board of the SDN switch are extracted; the abnormal data in the control data is determined by comparing the control data and the maintenance data; and the SDN is determined according to the abnormal data.
  • the fault type of the switch solves the technical problem that the fault type cannot be determined in time in the SDN network, and realizes the technical effect of quickly determining the fault type of the SDN switch.
  • the execution body of the foregoing step may be a device such as an SDN switch, but is not limited thereto.
  • the flow table and group table content data and related hardware resource ID data that is, determine the cause of the fault, and then obtain the fault type.
  • the data analysis of the flow table and the group table is performed by extracting and comparing the SDN distribution.
  • the control board of the switch and the group table of the service board and the content data of the flow table and the hardware resource ID data record are implemented.
  • extracting the control data recorded on the control board of the SDN switch and the maintenance data recorded on the service board of the SDN switch includes: extracting the first set of table sets and the first flow table set delivered by the control board, and/or Identification and associated with the hardware resources associated with the group table in a set of table collections An identifier of a hardware resource associated with the flow table in the first flow table set; extracting a second set of table sets and a second flow table set received by the service board, and/or associating with the group table in the second set of table sets The identifier of the hardware resource and the identifier of the hardware resource associated with the flow table in the second flow table set.
  • the above process of extracting data occurs on the control board and the service board of the SDN switch, respectively, and the analysis and comparison occur on the control board of the SDN switch.
  • the extracted control board record is the content information of the flow table and the group table sent by the SDN controller to the SDN switch control board through the OpenFlow protocol, and the related hardware resources (ie, and flow) allocated and maintained on the control board by the flow table and the group table.
  • the data of the switch service card is extracted from the group table and the flow table of the switch service board and the content data of the flow table and
  • the resource ID data applied by the service board is sent to the control board of the switch according to the flow table and the group table ID (that is, the identifier of the group table) after the content data of the SDN switch service board is extracted.
  • the switch control board according to the flow table and the group table ID. The analysis is performed.
  • the hardware resource IDs of the flow table and the group table are uniformly allocated, delivered, and recycled by the control board of the switch, and the application and release are triggered by the SDN switch service board.
  • the ID of the group table or the flow table may be used as an index to search for corresponding data; or the time period may be used as a condition to extract all data in the time period.
  • the time period may be used as a condition to extract all data in the time period.
  • MAC+VLAN ie MAC address and virtual local area network
  • HOSTIP+VRF HOSTIP table
  • HOSTIP and VPN routing forwarding tables look up the index.
  • the abnormal data in the control data may be determined by comparing the control data and the maintenance data, as follows: acquiring the first set of table sets An identifier of a group of tables; determining whether there is a group table having the same identifier as any one of the group tables in the second group of table sets; if there is no group table having the same identifier as any group of tables in the second group of table sets, determining Any group of tables is abnormal data.
  • determining, by comparing the control data and the maintenance data, the abnormal data in the control data includes: obtaining an identifier of any flow table in the first flow table set; determining whether the second flow table set has the same identifier as any flow table The flow table; if there is no flow table with the same identifier as any flow table in the second flow table set, it is determined that any flow table is abnormal data.
  • determining the abnormal data in the control data by comparing the control data and the maintenance data includes: obtaining an identifier of any one of the first group of the table sets; determining the identifier and the association of the hardware resources associated with any of the group of tables Whether the identifiers of the hardware resources in the target group table are the same, wherein the target group table is a group table in the second group of table sets having the same identifier as any group of tables; if the identifiers and associations of hardware resources associated with any group table are associated If the identifiers of the hardware resources of the target group table are different, it is determined that any of the group tables is abnormal data.
  • determining the abnormal data in the control data by comparing the control data and the maintenance data includes: obtaining an identifier of any flow table in the first flow table set; determining an identifier of the hardware resource associated with any flow table and being associated with the target flow Whether the identifier of the hardware resource of the table is the same, where the target flow table is a flow table in the second flow table that has the same identifier as any of the flow tables; if the identifier of the hardware resource associated with any flow table and the hardware associated with the target flow table If the identifiers of the resources are different, then any flow table is determined to be abnormal data.
  • the fault type of the SDN switch can be determined according to the abnormal data (the abnormal situation of the abnormal data, that is, the cause of the fault), as follows: if the fault cause is The second group of tables does not have a group table with the same identifier as the abnormal data, or the flow table with the same identifier as the abnormal data does not exist in the second flow table set, and the fault type of the SDN switch is determined to be the control board and the service. The flow between the boards is unreachable. The reason is that because the abnormal data is found, the abnormal data may be abnormal in the data of the group table or abnormal in the contents of the stream data.
  • determining the fault type of the SDN switch according to the abnormal data may also be implemented by: if the identifier of the hardware resource associated with the abnormal data is different from the identifier of the hardware resource associated with the target group table or the target flow table. Then, it is determined that the fault type of the SDN switch is that the traffic encapsulation information is incorrect. The reason is that the hardware resource ID in the abnormal data of the group table or the abnormal data in the flow table conflicts, that is, the resource ID maintained on the main control board does not match the resource ID on the service board.
  • the method of the present application further includes: obtaining a log record table of the SDN switch; using the identifier of the abnormal data as an index, obtaining the fault information of the SDN switch from the log record table. .
  • the flow table and the group table are delivered in real time.
  • the relevant data when the program is in error including the business module ID, the number of code lines, the related incoming parameters, the return value, etc., where the error occurs, the record has the flow table ID or the group table ID as the unique index.
  • the flow table ID or the group table ID of the error may be first determined, and then the relevant data at the time of the program error may be determined according to the ID to achieve the purpose of locating the error.
  • the method of the present application further includes: displaying the abnormal data and the fault information; and/or instructing the control panel to re-issue the corresponding group table and the flow table to repair the SDN. The failure of the switch.
  • the related flow table or group table received by the service board side of the switch is mainly based on the record of the control board (that is, an abnormality occurs).
  • the group table or the flow table is deleted, and the hardware resource ID corresponding to the table is released on the control board, and then the related flow table and the group table content data are re-issued to the service board of the switch according to the software record of the control board, and the service of the switch is performed.
  • the board re-applies the relevant hardware resource ID according to the content data of the flow table and the group table.
  • the present application provides an implementation method for restoring services based on service traffic, and the service may be classified into "MAC+ based on the Layer 2 service. "VLAN” and “VRF+IP” for Layer 3 services. Whether it is based on “MAC+VLAN” or “VRF+IP”, you can find a series of cascading unidirectionally referenced flow tables and group tables, and then determine whether there are abnormal records in each flow table and group table. If any, restore the business as described above.
  • the method of the present application can be applied to the system architecture shown in FIG. 3, and the controller uniformly sends control information such as a group table and a flow table to implement control of the network device (including the network device 1 and the network device 2).
  • Devices can be connected through an internal network, and network devices can also be connected to an external network.
  • Network devices can interact with servers (including Server 1 and Server 2) through a bus.
  • the foregoing network device (such as an SDN switch) can be used to perform the method of the present application.
  • the network device can include: a data configuration unit 401, a data recording unit 402, a data display unit 403, a data analysis unit 404, and data. Recovery unit 405.
  • the data configuration unit 401 provides an instruction configuration and a resolution configuration of the failure analysis, and provides a mode configuration for data recovery.
  • the configured failback mode can be configured to either automatic mode or manual mode.
  • the data recording unit 402 is responsible for the error LOG (ie, the log record table), and is responsible for recording related data when the program is in error during the flow table and group table issuance, and the recorded data is stored in the log record by using the flow table ID or the group table ID as an index. In the table.
  • error LOG ie, the log record table
  • LOG records can be added for group tables or flow tables with incorrect return values (providing material for subsequent error reasons).
  • the LOG is recorded in the memory, and records a series of prompt information such as the business module ID where the error occurred, the incoming parameter, the return value, and the number of error code lines.
  • the data analysis unit 404 extracts the content data of the flow table and the group table of the SDN switch control board and the service board and the record of the related hardware resource ID, and then performs comparative analysis on the control panel of the switch.
  • the extracted control board record is the content information of the flow table and the group table sent by the controller to the control board through the OpenFlow protocol, and the hardware resource ID data of the flow table or the group table application; the extracted service board record is the bottom record of the service board.
  • the group table and flow table content data and the hardware resource ID data of the service board application is the content information of the flow table and the group table sent by the controller to the control board through the OpenFlow protocol, and the hardware resource ID data of the flow table or the group table application; the extracted service board record is the bottom record of the service board.
  • the data display unit 403 displays the group table and the flow table contents and the related resource ID information on the control board and the service board, and simultaneously calls the LOG record module to display the cause of the error.
  • the data recovery unit 405 restores the error entry data manually or automatically according to the configured recovery mode information.
  • the implementation steps of detecting and recovering the traffic failure caused by the group table and the flow table information of the SDN switch control board not being delivered by the SDN switch service board due to the high CPU utilization are as follows: :
  • step S11 the "IP+VRF" or "MAC+VLAN” for forwarding the unannounced text is input, if the second layer is forwarded, the former is input, and if it is the third layer, the latter is input.
  • Step S12 Acquire a reference chain of the group table and the flow table according to "MAC+VLAN” or “IP+VRF”, and then perform the following steps on each flow table and group table unit in the reference chain.
  • Step S13 according to the group table ID and the flow table ID on the control board and the service board of the SDN switch
  • the data content of the related entry is extracted, and the SDN switch service board sends the extracted data information to the control board.
  • step S14 the switch control board invokes the data analysis unit to perform comparative analysis on the extracted data according to the flow table ID and the group table ID.
  • step S15 the data display unit is called to display the analysis result, and the data of the group table flow table on the control panel side is different from the service board.
  • step S16 the data recovery unit is manually called to perform real-time data recovery on the table of the group table and the flow table data abnormality.
  • step S21 the original "IP+VRF" or "MAC+VLAN” of the packet with the forwarding traffic encapsulated incorrectly is input, and if the layer 2 is forwarded, the former is input, and if it is the third layer, the latter is input.
  • Step S22 Obtain a reference chain of the group table and the flow table according to "MAC+VLAN” or “IP+VRF”, and then perform the following steps on each flow table and group table unit in the reference chain:
  • step S23 the data content of the related entry (that is, the group table or the flow table in which the error occurs) is extracted according to the group table ID and the flow table ID on the control board and the service board of the SDN switch, and the switch service board sends the extracted data information to the switch service board.
  • Switch control board the data content of the related entry
  • Step S24 the SDN switch control board invokes the data analysis unit to perform comparative analysis on the extracted data according to the flow table ID and the group table ID.
  • step S25 the data display unit is called to display the analysis result, and it is found that the hardware resource ID information of the group table flow table on the control panel side is different from that on the service board side of the switch.
  • step S26 the data recovery unit is manually called to perform real-time data recovery on the table of the group table and the flow table data abnormality.
  • step S501 a timer is started first, and the time interval is configurable by the user, and the fault check and the fault recovery are performed every fixed time.
  • step S502 it is determined whether the automatic recovery mode is enabled in the processing flow of the timer. If not, step S503 is performed; if the automatic recovery function is turned on, step S504 is performed.
  • step S503 returning may be performed, or step S502 may be performed again after the next interval time.
  • Step S504 extracting the flow table, the content data of the group table, the resource application data, and the like on the control board and the service board according to the group table or the flow table ID.
  • Step S505 the error analysis module is called to compare the service board data and the control panel data.
  • step S506 it is determined whether there is an error. If there is no error, the process returns to step S504. If there is an error, step S507 is performed.
  • Step S507 the fault recovery module is called to resume the service in real time.
  • the above method can greatly save the analysis of the fault time, and analyze and resolve the resource ID conflict, the residual data on the service board, the control board and the service board data are inconsistent. Problems such as unreachable services and incorrect encapsulation information are very effective. They can quickly locate problems and solve them quickly. At the same time, they can quickly recover services, thus avoiding long-term traffic interruptions and causing losses to customers.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • a device for determining the type of failure is also provided in the embodiment of the present invention.
  • the device is used to implement The above embodiments and preferred embodiments have not been described again.
  • the term "module" may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 6 is a schematic diagram of a device for determining a failure type according to an embodiment of the present invention.
  • the apparatus may include an extracting unit 61, a first determining unit 62, and a second determining unit 63.
  • the extracting unit 61 is configured to extract the control data recorded on the control board of the SDN switch and the maintenance data recorded on the service board of the SDN switch.
  • the first determining unit 62 is configured to determine abnormal data in the control data by comparing the control data and the maintenance data.
  • the second determining unit 63 is configured to determine the fault type of the SDN switch according to the abnormality data.
  • the extracting unit extracts the control data recorded on the control board of the SDN switch and the maintenance data recorded on the service board of the SDN switch; the first determining unit determines the abnormal data in the control data by comparing the control data and the maintenance data.
  • the second determining unit determines the fault type of the SDN switch according to the abnormal data, thereby solving the technical problem that the fault type cannot be determined in time in the SDN network, and realizing the technical effect of quickly determining the fault type of the SDN switch.
  • the above device may be applied to devices such as an SDN switch, but is not limited thereto.
  • the flow table and the group table content data and the related hardware resource ID data need to be analyzed.
  • the data analysis of the flow table and the group table is performed by extracting and comparing the group table of the control board and the service board of the SDN distributed switch. And the content data of the flow table and the hardware resource ID data record are implemented.
  • the extracting unit includes: a first extracting module, configured to extract a first set of table sets and a first flow table set delivered by the control board, and/or hardware resources associated with the group table in the first set of table sets. And an identifier of the hardware resource associated with the flow table in the first flow table set; the second extraction module is configured to extract the second set of the table set and the second flow table set received by the service board, and/or, The identification of the hardware resources associated with the group table in the second set of table sets and the second flow table set The identifier of the hardware resource associated with the flow table in .
  • the first determining unit may be configured to: obtain an identifier of any one of the first group of table sets; and determine whether there is a group table that has the same identifier as the any group of the second set of the table; If there is no group table with the same identifier as any group table in the two sets of table sets, then any group table is determined to be abnormal data.
  • the first determining unit is further configured to: obtain an identifier of any flow table in the first flow table set; determine whether a flow table having the same identifier as any flow table exists in the second flow table set; if the second flow table If there is no flow table with the same identifier as any flow table in the collection, then any flow table is determined to be abnormal data.
  • the second determining unit may be configured to perform: a group table having the same identifier as the abnormal data does not exist in the second group table, or a stream having the same identifier as the abnormal data does not exist in the second flow table set.
  • the fault type of the SDN switch is determined to be unreachable between the control board and the service board.
  • the first determining unit is further configured to: obtain an identifier of any one of the first group of table sets; determine an identifier of the hardware resource associated with the any group of tables and an identifier of the hardware resource associated with the target group table Is the same, wherein the target group table is a group table of the second group of table sets having the same identity as any group of tables; if the identifier of the hardware resource associated with any group table and the identifier of the hardware resource associated with the target group table If they are different, then any set of tables is determined to be abnormal data.
  • the first determining unit is further configured to: obtain an identifier of any flow table in the first flow table set; determine whether the identifier of the hardware resource associated with any flow table is the same as the identifier of the hardware resource associated with the target flow table,
  • the target flow table is a flow table having the same identifier as any flow table in the second flow table; if the identifier of the hardware resource associated with any flow table is different from the identifier of the hardware resource associated with the target flow table,
  • the first-class table is abnormal data.
  • the second determining unit may be further configured to: if the identifier of the hardware resource associated with the abnormal data is different from the identifier of the hardware resource associated with the target group table or the target flow table, determine the SDN switch The fault type is incorrect for the traffic encapsulation information.
  • the foregoing apparatus of the present application further includes: a display unit configured to display abnormal data and fault information; and/or a repair unit configured to instruct the control panel to re-issue the corresponding group table and flow Table to fix the failure of the SDN switch.
  • the above method can greatly save the analysis of the fault type time, analyze and resolve the resource ID conflict, the residual data on the service board, the control board and the service board data.
  • the problems such as inconsistency, unreasonable service forwarding, and incorrect encapsulation information are very effective. They can quickly locate problems and solve them quickly, and can quickly restore services, thus avoiding long-term traffic interruptions and causing losses to customers.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the storage medium is further arranged to store program code for performing the following steps:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs: extracting control data recorded on a control board of the SDN switch and maintenance data recorded on a service board of the SDN switch according to the stored program code in the storage medium; The data and maintenance data determine abnormal data in the control data; and determine the fault type of the SDN switch based on the abnormal data.
  • the processor performs: extracting, according to the stored program code in the storage medium, the first set of table sets and the first flow table set delivered by the control board, and/or, and the first set of table sets. An identifier of the hardware resource associated with the group table and an identifier of the hardware resource associated with the flow table in the first flow table set; extracting the second set of table sets and the second flow table set received by the service board, and/or An identification of a hardware resource associated with the group table in the second set of table sets and an identification of the hardware resource associated with the flow table in the second flow table set.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • control data recorded on the control board of the SDN switch and the maintenance data recorded on the service board of the SDN switch are extracted; by comparing the control data and maintaining The data determines abnormal data in the control data; and determines the fault type of the SDN switch based on the abnormal data. Therefore, the technical problem that the fault type cannot be determined in time in the SDN network is solved, and the technical effect of quickly locating the fault type of the SDN switch is realized.

Landscapes

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

Abstract

本发明提供了一种故障类型的确定方法和装置、存储介质。其中，该方法包括：提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据；通过比对控制数据和维护数据确定出控制数据中的异常数据；根据异常数据确定SDN交换机的故障类型。本发明解决了SDN网络中无法及时地确定故障类型的技术问题，进而达到了快速确定SDN交换机的故障类型的效果。

Description

故障类型的确定方法和装置、存储介质 技术领域
本发明涉及互联网领域，具体而言，涉及一种故障类型的确定方法和装置、存储介质。
背景技术
软件定义网络(Software Defined Network，SDN)，是Emulex网络一种新型网络创新架构，是网络虚拟化的一种实现方式，其核心技术OpenFlow通过将网络设备控制面与数据面分离开来，从而实现了网络流量的灵活控制，使网络作为管道变得更加智能。
传统IT架构中的网络，根据业务需求部署上线以后，在业务需求发生变动时，重新修改相应网络设备(如路由器、交换机、防火墙等)上的配置是一件非常繁琐的事情。在互联网或移动互联网瞬息万变的业务环境下，网络的高稳定与高性能还不足以满足业务需求，灵活性和敏捷性反而更为关键。SDN所做的事是将网络设备上的控制权分离出来，由集中的控制器管理，无须依赖底层网络设备(如路由器、交换机、防火墙等)，屏蔽了来自底层网络设备的差异。而控制权是完全开放的，用户可以自定义想实现的网络路由和传输规则策略，从而更加灵活和智能。
近年来，为了满足数据中心的网络虚拟化要求，SDN技术迅速崛起，SDN为网络设计带来了极大便利，SDN时代的网络，不再是以设备为中心，而是以应用为中心，应用驱动网络变革。这就需要很多深度定制的工作，云计算网络尤其如此。
OpenFlow是当前最为流行的SDN实现方式，基于OpenFlow的SDN的交换机是靠内部多个流表与组表的索引级联来实现报文转发。
相对于传统交换机业务的人工部署，SDN网络的业务部署是通过数据报文触发控制器自动下发的。SDN网络的普遍应用给业务部署带来了革命性的好处，但也给网络故障的定位带来了不便。当故障发生时，无法准确确定故障类型和故障位置，不能及时有效地进行故障处理。
针对SDN网络中无法及时地确定故障类型的技术问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种故障类型的确定方法和装置、存储介质，以至少解决SDN网络中无法及时地确定故障类型的技术问题。
根据本发明实施例的一个方面，提供了一种故障类型的确定方法，该方法包括：提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据；通过比对控制数据和维护数据确定出控制数据中的异常数据；根据异常数据确定SDN交换机的故障类型。
可选地，提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据包括：提取控制板下发的第一组表集合和第一流表集合，和/或，与第一组表集合中的组表相关联的硬件资源的标识和与第一流表集合中的流表相关联的硬件资源的标识；提取业务板接收到的第二组表集合和第二流表集合，和/或，与第二组表集合中的组表相关联的硬件资源的标识和与第二流表集合中的流表相关联的硬件资源的标识。
可选地，通过比对控制数据和维护数据确定出控制数据中的异常数据包括：获取第一组表集合中任一组表的标识；判断第二组表集合中是否存在与任一组表具有相同标识的组表；若第二组表集合中不存在与任一组表具有相同标识的组表，则确定任一组表为异常数据。
可选地，通过比对控制数据和维护数据确定出控制数据中的异常数据包括：获取第一流表集合中任一流表的标识；判断第二流表集合中是否存在与任一流表具有相同标识的流表；若第二流表集合中不存在与任一流表具有相同标识的流表，则确定任一流表为异常数据。
可选地，根据异常数据确定SDN交换机的故障类型包括：在第二组表中不存在与异常数据具有相同标识的组表，或，在第二流表集合中不存在与异常数据具有相同标识的流表的情况下，确定SDN交换机的故障类型为控制板与业务板之间流量不通。
可选地，通过比对控制数据和维护数据确定出控制数据中的异常数据包括：获取第一组表集合中任一组表的标识；判断关联于任一组表的硬件资源的标识与关联于目标组表的硬件资源的标识是否相同，其中，目标组表为第二组表集合中与任一组表具有相同标识的组表；若关联于任一组表的硬件资源的标识与关联于目标组表的硬件资源的标识不相同，则确定任一组表为异常数据。
可选地，通过比对控制数据和维护数据确定出控制数据中的异常数据包括：获取第一流表集合中任一流表的标识；判断关联于任一流表的硬件资源的标识与关联于目标流表的硬件资源的标识是否相同，其中，目标流表为第二流表中与任一流表具有相同标识的流表；若关联于任一流表的硬件资源的标识与关联于目标流表的硬件资源的标识不相同，则确定任一流表为异常数据。
可选地，根据异常数据确定SDN交换机的故障类型包括：在关联于异常数据的硬件资源的标识与关联于目标组表或目标流表的硬件资源的标识不相同的情况下，则确定SDN交换机的故障类型为流量封装信息不正确。
可选地，在根据异常数据确定SDN交换机的故障类型之后，该方法还包括：获取SDN交换机的日志记录表；以异常数据的标识为索引，从日志记录表中获取SDN交换机的故障信息。
可选地，在根据异常数据确定SDN交换机的故障类型之后，该方法还包括：显示异常数据和故障信息；和/或指示控制板重新下发对应的组表和流表，以修复SDN交换机的故障。
根据本发明实施例的另一个方面，提供了一种故障类型的确定装置，该装置包括：提取单元，设置为提取SDN交换机的控制板上记录的控制 数据和SDN交换机的业务板上记录的维护数据；第一确定单元，设置为通过比对控制数据和维护数据确定出控制数据中的异常数据；第二确定单元，设置为根据异常数据确定SDN交换机的故障类型。
可选地，提取单元包括：第一提取模块，设置为提取控制板下发的第一组表集合和第一流表集合，和/或，与第一组表集合中的组表相关联的硬件资源的标识和与第一流表集合中的流表相关联的硬件资源的标识；第二提取模块，设置为提取业务板接收到的第二组表集合和第二流表集合，和/或，与第二组表集合中的组表相关联的硬件资源的标识和与第二流表集合中的流表相关联的硬件资源的标识。
可选地，该装置还包括：显示单元，设置为显示异常数据和故障信息；和/或修复单元，设置为指示控制板重新下发对应的组表和流表，以修复SDN交换机的故障。
根据本发明的另一个实施例，提供了一种存储介质，存储介质可以被设置为存储用于执行以下步骤的程序代码：提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据；通过比对控制数据和维护数据确定出控制数据中的异常数据；根据异常数据确定SDN交换机的故障类型。
在本发明实施例中，通过提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据；通过比对控制数据和维护数据确定出控制数据中的异常数据；根据异常数据确定SDN交换机的故障类型。从而解决了SDN网络中无法及时地确定故障类型的技术问题，实现了快速定位SDN交换机的故障类型的技术效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的一种计算机终端的示意图；
图2是根据本发明实施例的故障类型的确定方法的流程图；
图3是根据本发明实施例的一种系统架构的示意图；
图4是根据本发明实施例的一种网络设备的示意图；
图5是根据本发明实施例的可选的故障类型的确定方法的流程图；
图6是根据本发明实施例的故障类型的确定装置的示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例一所提供的方法实施例可以在移动终端、计算机终端(如SDN交换机)或者类似的运算装置中执行。以运行在计算机终端上为例，如图1所示，计算机终端可以包括一个或多个(图中仅示出一个)处理器101(处理器101可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)、设置为存储数据的存储器103、以及设置为通信功能的传输装置105。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述电子装置的结构造成限定。
存储器103可设置为存储应用软件的软件程序以及模块，如本发明实施例中的设备的控制方法对应的程序指令/模块，处理器101通过运行存储在存储器103内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器可进一步包括相对于处理器远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端。上述网络的实例 包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置设置为经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端的通信供应商提供的无线网络。在一个实例中，传输装置包括一个网络适配器(Network Interface Controller，NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置可以为射频(Radio Frequency，RF)模块，其设置为通过无线方式与互联网进行通讯。
本申请所要解决的技术问题包括：对于SDN网络环境中交换机由于CPU利用率过高等原因造成的分布式资源ID冲突、业务流量转发不通、报文封装错误等故障类型，提供了一种自动分析故障类型和快速恢复业务的实现方式。由于SDN交换机上的业务部署都是通过控制器直接下发大量的流表和组表来实现的，不利于故障定位，通过实施本申请的方法能够极大的节省分析故障类型的时间，快速定位问题，同时还可以实现业务的快速恢复，降低由于设备故障导致的用户损失。
所谓流表，可被视作是OpenFlow对网络设备的数据转发功能的一种抽象。在传统网络设备中，交换机和路由器的数据转发需要依赖设备中保存的二层MAC地址转发表或者三层IP地址路由表，而OpenFlow交换机中使用的流表也采用类似的方式，在它的表项中整合了网络中各个层次的网络配置信息，从而在进行数据转发时可以使用更丰富的规则。
组是OpenFlow为数据包指定在多个流中执行相同操作集的高效方法，其对应的组表包括：组标志符、组类型、计数器和动作桶。利用组表，每个数据流可以被划分到相应的组中，动作指令的执行可以针对属于同一个组标识符的所有数据包，适合用于实现广播或多播，或者规定只执行某些特定的操作集。其中，组的类型规定了是否所有的动作桶中的指令都会被执行。
根据本发明实施例，提供了一种故障类型的确定方法的方法实施例，需要说明的是，在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是 在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
图2是根据本发明实施例的故障类型的确定方法的流程图，如图2所示，该方法包括如下步骤：
步骤S201，提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据。
步骤S202，通过比对控制数据和维护数据确定出控制数据中的异常数据。
正常情况下，控制数据中的每一个数据会在维护数据中存在一个对应的数据，而异常数据是指控制数据中存在的数据，可通过以下两种情况确定异常数据：对于控制数据中的任一数据，在维护数据中不存在与任一数据对应的数据，或者，在维护数据中存在与任一数据对应的数据，但是该数据中记载的信息与任一数据记载的数据不一致。
步骤S203，根据异常数据确定SDN交换机的故障类型。
通过上述实施例，提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据；通过比对控制数据和维护数据确定出控制数据中的异常数据；根据异常数据确定SDN交换机的故障类型，从而解决了SDN网络中无法及时地确定故障类型的技术问题，实现了快速确定SDN交换机的故障类型的技术效果。
可选地，上述步骤的执行主体可以为SDN交换机等设备，但不限于此。
为了确定异常数据和故障类型，需要对流表和组表内容数据和相关硬件资源ID数据分析，即确定故障的原因，进而得到故障类型，对流表和组表的数据分析是通过提取和比较SDN分布式交换机的控制板和业务板的组表和流表的内容数据和硬件资源ID数据记录来实现的。
具体地，提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据包括：提取控制板下发的第一组表集合和第一流表集合，和/或，与第一组表集合中的组表相关联的硬件资源的标识和与 第一流表集合中的流表相关联的硬件资源的标识；提取业务板接收到的第二组表集合和第二流表集合，和/或，与第二组表集合中的组表相关联的硬件资源的标识和与第二流表集合中的流表相关联的硬件资源的标识。
上述的提取数据的过程分别发生在SDN交换机的控制板和业务板上，分析和比较发生地点在SDN交换机的控制板上。提取的控制板记录是SDN控制器通过OpenFlow协议向SDN交换机控制板下发的流表和组表的内容信息以及这个流表和组表在控制板上分配和维护的相关硬件资源(即与流表或组表相关联的硬件资源)的ID数据(即上述的组表的标识或者流表的标识)；交换机业务卡数据提取的是交换机业务板底层记录的组表和流表的内容数据以及本业务板申请的资源ID数据，SDN交换机业务板内容数据提取完成后根据流表和组表ID(即组表的标识)发送给交换机的控制板，由交换机控制板根据流表和组表ID进行分析，另外，流表和组表相关的硬件资源ID由交换机的控制板统一分配、下发、回收，由SDN交换机业务板触发申请和释放。
需要说明的是，在上述的提取数据的过程中，可以组表或者流表的ID(即流表标识)作为索引查找对应的数据；也可以时间段为条件，提取该时间段内的所有数据；还可以BRIGDE表(即二层MAC地址转发表)中的“MAC+VLAN”(即MAC地址和虚拟局域网)，或以HOSTIP表(即三层IP地址路由表)中的“HOSTIP+VRF”(主机IP和VPN路由转发表)为索引进行查找。
在上述实施例中，在交换机控制板根据流表和组表ID进行分析时，可通过比对控制数据和维护数据确定出控制数据中的异常数据，具体如下：获取第一组表集合中任一组表的标识；判断第二组表集合中是否存在与任一组表具有相同标识的组表；若第二组表集合中不存在与任一组表具有相同标识的组表，则确定任一组表为异常数据。
可选地，通过比对控制数据和维护数据确定出控制数据中的异常数据包括：获取第一流表集合中任一流表的标识；判断第二流表集合中是否存在与任一流表具有相同标识的流表；若第二流表集合中不存在与任一流表具有相同标识的流表，则确定任一流表为异常数据。
可选地，通过比对控制数据和维护数据确定出控制数据中的异常数据包括：获取第一组表集合中任一组表的标识；判断关联于任一组表的硬件资源的标识与关联于目标组表的硬件资源的标识是否相同，其中，目标组表为第二组表集合中与任一组表具有相同标识的组表；若关联于任一组表的硬件资源的标识与关联于目标组表的硬件资源的标识不相同，则确定任一组表为异常数据。
可选地，通过比对控制数据和维护数据确定出控制数据中的异常数据包括：获取第一流表集合中任一流表的标识；判断关联于任一流表的硬件资源的标识与关联于目标流表的硬件资源的标识是否相同，其中，目标流表为第二流表中与任一流表具有相同标识的流表；若关联于任一流表的硬件资源的标识与关联于目标流表的硬件资源的标识不相同，则确定任一流表为异常数据。
在通过比对控制数据和维护数据确定出控制数据中的异常数据之后，即可根据异常数据(异常数据的异常情形即故障的原因)确定SDN交换机的故障类型，具体如下：如果故障原因为在第二组表中不存在与异常数据具有相同标识的组表，或，在第二流表集合中不存在与异常数据具有相同标识的流表，则确定SDN交换机的故障类型为控制板与业务板之间流量不通。原因就是因为发现了异常数据，这个异常数据可能是组表数据内容异常或者是流标数据内容异常。
可选地，根据异常数据确定SDN交换机的故障类型还可以通过如下方式实现：在关联于异常数据的硬件资源的标识与关联于目标组表或目标流表的硬件资源的标识不相同的情况下，则确定SDN交换机的故障类型为流量封装信息不正确。原因就是组表异常数据或者流表异常数据中的硬件资源ID冲突，即主控板上维护的资源ID与业务板上的资源ID不匹配。
可选的，在根据异常数据确定SDN交换机的故障类型之后，本申请的方法还包括：获取SDN交换机的日志记录表；以异常数据的标识为索引，从日志记录表中获取SDN交换机的故障信息。
需要说明的是，在日志记录表中，会实时保存流表和组表下发过程中 程序出错时的相关数据，包括出错发生的业务模块ID、代码行数、相关传入参数、返回值等，该记录以流表ID或者组表ID作为唯一索引。
因此，可以首先确定出错的流表ID或组表ID，然后根据这个ID即可确定程序出错时的相关数据，以达到对错误进行定位的目的。
可选地，在根据异常数据确定SDN交换机的故障类型之后，本申请的方法还包括：显示异常数据和故障信息；和/或指示控制板重新下发对应的组表和流表，以修复SDN交换机的故障。
当出现流表、组表中显示的信息与软硬件数据不一致、资源ID冲突时，以控制板的记录为主，将交换机的业务板侧接收到的相关流表或者组表(即发生异常的组表或者流表)删除，并且在控制板上释放该表对应的硬件资源ID，然后按照控制板的软件记录向交换机的业务板重新下发相关流表和组表内容数据，由交换机的业务板根据流表和组表的内容数据重新申请相关的硬件资源ID。
在上述实施例中，当出现业务转发不通、封装信息不正确的情况时，本申请给出了一种基于业务流量来恢复业务的实现方法，基于业务可以分为基于二层业务的“MAC+VLAN”以及三层业务的“VRF+IP”两种。无论是基于“MAC+VLAN”还是基于“VRF+IP”，都可以查找出一系列级联的单向引用的流表和组表，然后判断每个流表和组表中是否有异常记录，如果有的就按照上述的方法恢复业务。
下面结合图3至图5详述本申请的实施例。
本申请的方法可以应用于如图3所示的系统架构中，由控制器统一发送组表和流表等控制信息，以实现对网络设备(包括网络设备1和网络设备2)的控制，网络设备之间可以通过内部网络连接，网络设备也可以与外部网络连接，网络设备可以通过总线与服务器(包括服务器1和服务器2)进行交互。
上述的网络设备(如SDN交换机)可用于执行本申请的方法，如图4所示，该网络设备可以包括：数据配置单元401、数据记录单元402、数据显示单元403、数据分析单元404以及数据恢复单元405。
数据配置单元401，提供故障分析的指令配置和解析配置、提供数据恢复的模式配置。
配置的故障恢复的模式可以配置成为自动模式或者手动模式。
数据记录单元402，负责错误LOG(即日志记录表)，负责记录流表和组表下发过程中程序出错时的相关数据，记录的数据以流表ID或者组表ID作为索引保存在日志记录表中。
可针对有错误返回值的组表或者流表增加LOG记录(为后续显示错误原因提供素材)。该LOG记录在内存中，记录发生错误的业务模块ID，传入参数、返回值、错误代码行数等一系列提示信息。
数据分析单元404，分别提取SDN交换机控制板和业务板的流表和组表的内容数据以及相关硬件资源ID的记录，然后在交换机的控制板上做比较分析。提取的控制板记录是控制器通过OpenFlow协议向控制板下发的流表和组表的内容信息以及这个流表或者组表申请的硬件资源ID数据；提取的业务板记录是本业务板底层记录的组表和流表内容数据以及本业务板申请的硬件资源ID数据。
数据显示单元403，显示控制板和业务板上组表和流表内容以及相关资源ID信息，同时调用LOG记录模块显示错误原因。
数据恢复单元405，根据配置的恢复模式信息，手动或者自动恢复错误表项数据。
在上述实施例中，如果选用手动恢复模式，对于由于CPU利用率过高导致SDN交换机控制板的组表和流表信息没有下发SDN交换机业务板而导致流量不通的检测和恢复的实施步骤如下：
步骤S11，输入转发不通报文的“IP+VRF”或者“MAC+VLAN”，如果是二层转发则输入前者，如果是三层转发则输入后者。
步骤S12，根据“MAC+VLAN”或者“IP+VRF”获取组表和流表的引用链，然后对引用链中的每个流表和组表单元执行下述步骤。
步骤S13，在SDN交换机的控制板和业务板上根据组表ID和流表ID 提取相关表项的数据内容，SDN交换机业务板将提取的数据信息发给控制板。
步骤S14，交换机控制板根据流表ID和组表ID调用数据分析单元对提取的数据进行比较分析。
步骤S15，调用数据显示单元显示分析结果，发现控制板侧的组表流表数据与业务板不同。
步骤S16，手动调用数据恢复单元对组表和流表数据异常的表项进行数据的实时恢复。
如果选用手动恢复模式，对于在CPU利用率过高时，SDN交换机控制板上维护的硬件资源ID与业务板卡申请维护的资源ID不同导致的资源ID冲突，从而使得流量封装信息不正确时，执行实时检测和恢复的步骤。
步骤S21，输入转发流量封装不正确报文的原始的“IP+VRF”或者“MAC+VLAN”，如果是二层转发则输入前者，如果是三层转发则输入后者。
步骤S22，根据“MAC+VLAN”或者“IP+VRF”获取组表和流表的引用链，然后对引用链中的每个流表和组表单元执行下述步骤：
步骤S23，在SDN交换机的控制板和业务板上根据组表ID和流表ID提取相关表项的数据内容(即发生错误的组表或流表)，交换机业务板将提取的数据信息发给交换机控制板。
步骤S24，SDN交换机控制板根据流表ID和组表ID调用数据分析单元对提取的数据进行比较分析。
步骤S25，调用数据显示单元显示分析结果，发现控制板侧的组表流表硬件资源ID信息与交换机业务板侧的不同。
步骤S26，手动调用数据恢复单元对组表和流表数据异常的表项进行数据的实时恢复。
如果选择自动恢复模式，实施步骤如附图5所示：
步骤S501，首先启动一个的定时器，时间间隔用户可配置，每隔固定时间进行故障检查和故障恢复。
步骤S502，在定时器的处理流程中判断是否开启了自动恢复模式，如果没有开启，则执行步骤S503；如果开启了自动恢复功能执行步骤S504。
步骤S503，返回，可以是停止执行，也可以是下一次间隔时间到后再次执行步骤S502。
步骤S504，根据组表或流表ID在控制板和业务板上分别提取流表、组表的内容数据、资源申请数据等。
步骤S505，调用错误分析模块，比较业务板数据和控制板数据。
步骤S506，判断是否有错，如果没有错误则返回步骤S504，有错误则执行步骤S507。
步骤S507，调用故障恢复模块实时恢复业务。
在SDN网络环境中，在分布式网络设备出现故障时，通过上述方法，能够极大节省分析故障的时间，对分析和解决资源ID冲突、业务板上的残留数据、控制板和业务板数据不一致、业务转发不通、封装信息不正确等问题十分有效，能够快速定位问题并快速解决，同时可以快速恢复业务，从而避免长时间流量中断给客户造成损失。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例2
本发明实施例中还提供了一种故障类型的确定装置。该装置用于实现 上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本发明实施例的故障类型的确定装置的示意图。如图6所示，该装置可以包括：提取单元61、第一确定单元62以及第二确定单元63。
提取单元61，设置为提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据。
第一确定单元62，设置为通过比对控制数据和维护数据确定出控制数据中的异常数据。
第二确定单元63，设置为根据异常数据确定SDN交换机的故障类型。
通过上述实施例，提取单元提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据；第一确定单元通过比对控制数据和维护数据确定出控制数据中的异常数据；第二确定单元根据异常数据确定SDN交换机的故障类型，从而解决了SDN网络中无法及时地确定故障类型的技术问题，实现了快速确定SDN交换机的故障类型的技术效果。
可选地，上述装置可应用于SDN交换机等设备，但不限于此。
为了确定异常数据和故障类型，需要对流表和组表内容数据和相关硬件资源ID数据分析，对流表和组表的数据分析是通过提取和比较SDN分布式交换机的控制板和业务板的组表和流表的内容数据和硬件资源ID数据记录来实现的。
具体地，提取单元包括：第一提取模块，设置为提取控制板下发的第一组表集合和第一流表集合，和/或，与第一组表集合中的组表相关联的硬件资源的标识和与第一流表集合中的流表相关联的硬件资源的标识；第二提取模块，设置为提取业务板接收到的第二组表集合和第二流表集合，和/或，与第二组表集合中的组表相关联的硬件资源的标识和与第二流表集合 中的流表相关联的硬件资源的标识。
可选地，第一确定单元可设置为执行：获取第一组表集合中任一组表的标识；判断第二组表集合中是否存在与任一组表具有相同标识的组表；若第二组表集合中不存在与任一组表具有相同标识的组表，则确定任一组表为异常数据。
可选地，第一确定单元还设置为执行：获取第一流表集合中任一流表的标识；判断第二流表集合中是否存在与任一流表具有相同标识的流表；若第二流表集合中不存在与任一流表具有相同标识的流表，则确定任一流表为异常数据。
可选地，第二确定单元可设置为执行：在第二组表中不存在与异常数据具有相同标识的组表，或，在第二流表集合中不存在与异常数据具有相同标识的流表的情况下，确定SDN交换机的故障类型为控制板与业务板之间流量不通。
可选地，第一确定单元还设置为执行：获取第一组表集合中任一组表的标识；判断关联于任一组表的硬件资源的标识与关联于目标组表的硬件资源的标识是否相同，其中，目标组表为第二组表集合中与任一组表具有相同标识的组表；若关联于任一组表的硬件资源的标识与关联于目标组表的硬件资源的标识不相同，则确定任一组表为异常数据。
可选地，第一确定单元还设置为执行：获取第一流表集合中任一流表的标识；判断关联于任一流表的硬件资源的标识与关联于目标流表的硬件资源的标识是否相同，其中，目标流表为第二流表中与任一流表具有相同标识的流表；若关联于任一流表的硬件资源的标识与关联于目标流表的硬件资源的标识不相同，则确定任一流表为异常数据。
可选地，第二确定单元还可设置为执行：在关联于异常数据的硬件资源的标识与关联于目标组表或目标流表的硬件资源的标识不相同的情况下，则确定SDN交换机的故障类型为流量封装信息不正确。
可选地，本申请的上述装置还包括：显示单元，设置为显示异常数据和故障信息；和/或修复单元，设置为指示控制板重新下发对应的组表和流 表，以修复SDN交换机的故障。
在SDN网络环境中，在分布式网络设备出现故障时，通过上述方法，能够极大节省分析故障类型的时间，对分析和解决资源ID冲突、业务板上的残留数据、控制板和业务板数据不一致、业务转发不通、封装信息不正确等问题十分有效，能够快速定位问题并快速解决，同时可以快速恢复业务，从而避免长时间流量中断给客户造成损失。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据；
S2，通过比对控制数据和维护数据确定出控制数据中的异常数据；
S3，根据异常数据确定SDN交换机的故障类型。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S4，提取控制板下发的第一组表集合和第一流表集合，和/或，与第一组表集合中的组表相关联的硬件资源的标识和与第一流表集合中的流表相关联的硬件资源的标识；
S5，提取业务板接收到的第二组表集合和第二流表集合，和/或，与第二组表集合中的组表相关联的硬件资源的标识和与第二流表集合中的流表相关联的硬件资源的标识。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据；通过比对控制数据和维护数据确定出控制数据中的异常数据；根据异常数据确定SDN交换机的故障类型。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行：提取控制板下发的第一组表集合和第一流表集合，和/或，与第一组表集合中的组表相关联的硬件资源的标识和与第一流表集合中的流表相关联的硬件资源的标识；提取业务板接收到的第二组表集合和第二流表集合，和/或，与第二组表集合中的组表相关联的硬件资源的标识和与第二流表集合中的流表相关联的硬件资源的标识。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
在本发明实施例中，通过提取SDN交换机的控制板上记录的控制数据和SDN交换机的业务板上记录的维护数据；通过比对控制数据和维护 数据确定出控制数据中的异常数据；根据异常数据确定SDN交换机的故障类型。从而解决了SDN网络中无法及时地确定故障类型的技术问题，实现了快速定位SDN交换机的故障类型的技术效果。

Claims (14)

  1. 一种故障类型的确定方法，包括：
    提取SDN交换机的控制板上记录的控制数据和所述SDN交换机的业务板上记录的维护数据；
    通过比对所述控制数据和所述维护数据确定出所述控制数据中的异常数据；
    根据所述异常数据确定所述SDN交换机的故障类型。
  2. 根据权利要求1所述的方法，其中，提取SDN交换机的控制板上记录的控制数据和所述SDN交换机的业务板上记录的维护数据包括：
    提取所述控制板下发的第一组表集合和第一流表集合，和/或，与所述第一组表集合中的组表相关联的硬件资源的标识和与所述第一流表集合中的流表相关联的硬件资源的标识；
    提取所述业务板接收到的第二组表集合和第二流表集合，和/或，与所述第二组表集合中的组表相关联的硬件资源的标识和与所述第二流表集合中的流表相关联的硬件资源的标识。
  3. 根据权利要求2所述的方法，其中，通过比对所述控制数据和所述维护数据确定出所述控制数据中的异常数据包括：
    获取所述第一组表集合中任一组表的标识；
    判断所述第二组表集合中是否存在与所述任一组表具有相同标识的组表；
    若所述第二组表集合中不存在与所述任一组表具有相同标识的组表，则确定所述任一组表为异常数据。
  4. 根据权利要求2所述的方法，其中，通过比对所述控制数据 和所述维护数据确定出所述控制数据中的异常数据包括：
    获取所述第一流表集合中任一流表的标识；
    判断所述第二流表集合中是否存在与所述任一流表具有相同标识的流表；
    若所述第二流表集合中不存在与所述任一流表具有相同标识的流表，则确定所述任一流表为异常数据。
  5. 根据权利要求3或4所述的方法，其中，根据所述异常数据确定所述SDN交换机的故障类型包括：
    在所述第二组表中不存在与所述异常数据具有相同标识的组表，或，在所述第二流表集合中不存在与所述异常数据具有相同标识的流表的情况下，确定所述SDN交换机的故障类型为所述控制板与所述业务板之间流量不通。
  6. 根据权利要求2所述的方法，其中，通过比对所述控制数据和所述维护数据确定出所述控制数据中的异常数据包括：
    获取所述第一组表集合中任一组表的标识；
    判断关联于所述任一组表的硬件资源的标识与关联于目标组表的硬件资源的标识是否相同，其中，所述目标组表为所述第二组表集合中与所述任一组表具有相同标识的组表；
    若关联于所述任一组表的硬件资源的标识与关联于所述目标组表的硬件资源的标识不相同，则确定所述任一组表为异常数据。
  7. 根据权利要求2所述的方法，其中，通过比对所述控制数据和所述维护数据确定出所述控制数据中的异常数据包括：
    获取所述第一流表集合中任一流表的标识；
    判断关联于所述任一流表的硬件资源的标识与关联于目标流表的硬件资源的标识是否相同，其中，所述目标流表为所述第二流表中与 所述任一流表具有相同标识的流表；
    若关联于所述任一流表的硬件资源的标识与关联于所述目标流表的硬件资源的标识不相同，则确定所述任一流表为异常数据。
  8. 根据权利要求6或7所述的方法，其中，根据所述异常数据确定所述SDN交换机的故障类型包括：
    在关联于所述异常数据的硬件资源的标识与关联于目标组表或目标流表的硬件资源的标识不相同的情况下，则确定所述SDN交换机的故障类型为流量封装信息不正确。
  9. 根据权利要求1或2所述的方法，其中，在根据所述异常数据确定所述SDN交换机的故障类型之后，所述方法还包括：
    获取所述SDN交换机的日志记录表；
    以所述异常数据的标识为索引，从所述日志记录表中获取所述SDN交换机的故障信息。
  10. 根据权利要求9所述的方法，其中，在根据所述异常数据确定所述SDN交换机的故障类型之后，所述方法还包括：
    显示所述异常数据和所述故障信息；和/或
    指示所述控制板重新下发对应的组表和流表，以修复所述SDN交换机的故障。
  11. 一种故障类型的确定装置，包括：
    提取单元，设置为提取SDN交换机的控制板上记录的控制数据和所述SDN交换机的业务板上记录的维护数据；
    第一确定单元，设置为通过比对所述控制数据和所述维护数据确定出所述控制数据中的异常数据；
    第二确定单元，设置为根据所述异常数据确定所述SDN交换机的故障类型。
  12. 根据权利要求11所述的装置，其中，所述提取单元包括：
    第一提取模块，设置为提取所述控制板下发的第一组表集合和第一流表集合，和/或，与所述第一组表集合中的组表相关联的硬件资源的标识和与所述第一流表集合中的流表相关联的硬件资源的标识；
    第二提取模块，设置为提取所述业务板接收到的第二组表集合和第二流表集合，和/或，与所述第二组表集合中的组表相关联的硬件资源的标识和与所述第二流表集合中的流表相关联的硬件资源的标识。
  13. 根据权利要求11或12所述的装置，其中，所述装置还包括：
    显示单元，设置为显示所述异常数据和故障信息；和/或
    修复单元，设置为指示所述控制板重新下发对应的组表和流表，以修复所述SDN交换机的故障。
  14. 一种存储介质，其特征在于，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求1至10中任一项所述的方法。
PCT/CN2017/089146 2016-06-22 2017-06-20 故障类型的确定方法和装置、存储介质 WO2017219957A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610460553.4A CN107528715A (zh) 2016-06-22 2016-06-22 故障类型的确定方法和装置
CN201610460553.4 2016-06-22

Publications (1)

Publication Number Publication Date
WO2017219957A1 true WO2017219957A1 (zh) 2017-12-28

Family

ID=60734180

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/089146 WO2017219957A1 (zh) 2016-06-22 2017-06-20 故障类型的确定方法和装置、存储介质

Country Status (2)

Country Link
CN (1) CN107528715A (zh)
WO (1) WO2017219957A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10652084B2 (en) 2018-05-01 2020-05-12 At&T Intellectual Property I, L.P. Service recovery in a software defined network
CN113037539A (zh) * 2021-02-05 2021-06-25 新华三信息安全技术有限公司 一种故障定位方法及装置
CN114221853A (zh) * 2021-12-13 2022-03-22 国网浙江省电力有限公司营销服务中心 一种用电信息采集设备的运行分析系统及其工作方法

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108629865A (zh) * 2018-04-28 2018-10-09 百度在线网络技术（北京）有限公司 故障日志的生成方法、装置、设备及存储介质
CN109327344B (zh) * 2018-11-29 2021-10-26 郑州云海信息技术有限公司 一种白盒交换机故障诊断方法及装置
CN112910731B (zh) * 2021-01-28 2022-11-11 三维通信股份有限公司 计数器的确定方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104579810A (zh) * 2013-10-23 2015-04-29 中兴通讯股份有限公司 软件定义网络流量采样方法和系统
US20150350156A1 (en) * 2012-12-26 2015-12-03 Zte Corporation NAT implementation system, method, and Openflow switch
CN105406988A (zh) * 2015-10-26 2016-03-16 中国电子科技集团公司第二十八研究所 一种软件定义抗毁网络构建方法
CN105406473A (zh) * 2015-12-29 2016-03-16 国网辽宁省电力有限公司 一种基于软件定义网络的配电网故障统一处理方法和系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103428031B (zh) * 2013-08-05 2016-04-13 浙江大学 一种基于软件定义网络的域间链路快速故障恢复方法
US9350632B2 (en) * 2013-09-23 2016-05-24 Intel Corporation Detection and handling of virtual network appliance failures
US9253026B2 (en) * 2013-12-18 2016-02-02 International Business Machines Corporation Software-defined networking disaster recovery
CN103929333A (zh) * 2014-05-08 2014-07-16 陈桂芳 一种sdn控制器资源池的实现方法
CN104243205B (zh) * 2014-09-03 2019-01-25 新华三技术有限公司 一种虚拟交换机故障时的报文处理方法和设备
KR20160069415A (ko) * 2014-12-08 2016-06-16 주식회사 케이티 Sdn 환경에서 플로우 엔트리 복구를 위한 sdn 스위치 플로우 저장 방법
CN104717098B (zh) * 2015-04-09 2017-12-29 北京邮电大学 一种数据处理方法及装置
CN105634817A (zh) * 2016-01-08 2016-06-01 广州西麦科技股份有限公司 一种基于sdn的网络故障自动检测的系统及方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150350156A1 (en) * 2012-12-26 2015-12-03 Zte Corporation NAT implementation system, method, and Openflow switch
CN104579810A (zh) * 2013-10-23 2015-04-29 中兴通讯股份有限公司 软件定义网络流量采样方法和系统
CN105406988A (zh) * 2015-10-26 2016-03-16 中国电子科技集团公司第二十八研究所 一种软件定义抗毁网络构建方法
CN105406473A (zh) * 2015-12-29 2016-03-16 国网辽宁省电力有限公司 一种基于软件定义网络的配电网故障统一处理方法和系统

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10652084B2 (en) 2018-05-01 2020-05-12 At&T Intellectual Property I, L.P. Service recovery in a software defined network
US11463304B2 (en) 2018-05-01 2022-10-04 At&T Intellectual Property I, L.P. Service recovery in a software defined network
CN113037539A (zh) * 2021-02-05 2021-06-25 新华三信息安全技术有限公司 一种故障定位方法及装置
CN114221853A (zh) * 2021-12-13 2022-03-22 国网浙江省电力有限公司营销服务中心 一种用电信息采集设备的运行分析系统及其工作方法
CN114221853B (zh) * 2021-12-13 2023-07-28 国网浙江省电力有限公司营销服务中心 一种用电信息采集设备的运行分析系统及其工作方法

Also Published As

Publication number Publication date
CN107528715A (zh) 2017-12-29

Similar Documents

Publication Publication Date Title
WO2017219957A1 (zh) 故障类型的确定方法和装置、存储介质
US10452422B2 (en) Method and apparatus for deploying virtual machine instance, and device
US20210152443A1 (en) Technologies for annotating process and user information for network flows
US11082282B2 (en) Method and system for sharing state between network elements
EP3664372A1 (en) Network management method and related device
WO2022083540A1 (zh) 故障恢复预案确定方法、装置及系统、计算机存储介质
WO2017008578A1 (zh) 网络功能虚拟化架构中数据检查的方法和装置
WO2015188579A1 (zh) 分布式虚拟防火墙装置、方法及防火墙控制器
US10417014B2 (en) System service reloading method and apparatus
WO2016206386A1 (zh) 一种故障关联方法和装置
US9548922B2 (en) Enabling scalable virtual machine tracking in a data center fabric
CN109981403A (zh) 虚拟机网络数据流量监控方法及装置
US10846120B2 (en) Configuration tracking in virtualized computing environments
US10671421B2 (en) Virtual machine start method and apparatus
CN103260190B (zh) 基于lte长期演进系统网络的安全审计方法
CN109639488B (zh) 一种多外网分流加速方法及系统
US9985862B2 (en) MEP configuration method and network device
WO2016177180A1 (zh) 一种OpenFlow交换机能力上报的方法及装置
CN106464541B (zh) 基于网络功能虚拟化的故障处理方法及设备
EP3474501B1 (en) Network device stacking
WO2016188081A1 (zh) 扩展端口的处理方法、装置及系统
US11916739B2 (en) Mitigation of physical network misconfigurations for clustered nodes
US9762661B1 (en) Managing networks in a virtualization system
WO2024098938A1 (zh) 网络存储功能故障检测及容灾方法及相关设备
EP4149062A1 (en) Deployment method and apparatus for virtualized network service

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17814695

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17814695

Country of ref document: EP

Kind code of ref document: A1