WO2016110248A1 - 一种转发设备故障处理的方法、设备和控制器 - Google Patents

一种转发设备故障处理的方法、设备和控制器 Download PDF

Info

Publication number
WO2016110248A1
WO2016110248A1 PCT/CN2016/070159 CN2016070159W WO2016110248A1 WO 2016110248 A1 WO2016110248 A1 WO 2016110248A1 CN 2016070159 W CN2016070159 W CN 2016070159W WO 2016110248 A1 WO2016110248 A1 WO 2016110248A1
Authority
WO
WIPO (PCT)
Prior art keywords
forwarding
port
forwarding device
path
snc
Prior art date
Application number
PCT/CN2016/070159
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 华为技术有限公司
Priority to EP16734908.3A priority Critical patent/EP3232616B1/en
Publication of WO2016110248A1 publication Critical patent/WO2016110248A1/zh
Priority to US15/641,027 priority patent/US10756958B2/en
Priority to US16/931,708 priority patent/US11496355B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • 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
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • 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
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • 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
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, device, and controller for fault handling of a forwarding device.
  • a forwarding device when a forwarding device generates a fault due to hardware or software, such as a forwarding device port error, a port error, and a single fiber fault, the fault information needs to be transmitted to other devices.
  • the delivery is dependent on the protocol message, so that multiple forwarding devices jointly optimize the packet forwarding path related to the failure.
  • the commonly used protocol packet is the bidirectional forwarding detection (BFD) protocol, which can achieve fast convergence of the link and ensure the resiliency of the service.
  • BFD bidirectional forwarding detection
  • the CRC error detection is performed on the port of the forwarding device. After the port detects the CRC error, the port sends the error information to the ingress node of the forwarding path through the BFD packet.
  • the multiple forwarding devices in the forwarding path respectively calculate the CRC error, and the ingress node calculates the error rate of the forward forwarding path to calculate the error rate, and determines whether the error rate exceeds the preset threshold to determine whether to trigger the forwarding path and service switching.
  • the BFD packets can reach the ingress node through multiple forwarding devices, so the elapsed time is long, which may interrupt the service and occupy the hardware resources of the BFD system.
  • the embodiments of the present invention provide a method, a device, and a controller for processing a fault of a forwarding device, which can solve the problem that the fault information is transmitted in a time-consuming manner, so that the efficiency of the forwarding path is recalculated.
  • the first aspect provides a method for troubleshooting a forwarding device, including:
  • the software-defined networking (SDN) controller receives a notification message sent by the first forwarding device, where the notification message includes a fault parameter of the first forwarding device, and the first forwarding
  • the fault parameter of the device includes the device identifier of the first forwarding device, the port identifier of the port of the first forwarding device that is degraded, and the degradation value of the port identified by the port identifier.
  • the SDN controller (English: SDN controller, SNC) determines at least one forwarding path of the port identified by the port identifier according to the device identifier and the port identifier;
  • the SNC acquires a fault parameter of the forwarding device other than the first forwarding device on one of the at least one forwarding path, where the fault parameter of the other forwarding device includes the device identifier of the other forwarding device, a port identifier of the port of the other forwarding device on the one forwarding path and a degradation value of the port on the one forwarding path;
  • the SNC determines whether the one forwarding path needs to be updated according to the fault parameter of the first forwarding device and the fault parameter of the other forwarding device except the first forwarding device on the one forwarding path.
  • the SNC is configured according to a fault parameter of the first forwarding device and a fault parameter of the other forwarding device except the first forwarding device on the one forwarding path. Determining whether to update the one forwarding path includes:
  • the SNC updates the first forwarding path.
  • the SNC updating the first forwarding path includes:
  • the SNC calculates the updated first forwarding path, removes the first forwarding path, and establishes the updated first forwarding path according to the updated first forwarding path;
  • the SNC replaces the first forwarding path with a backup path of the first forwarding path.
  • the notification message is an asynchronous message of an OpenFlow OpenFlow protocol
  • the notification message A type-length-value TLV having a type value of 35 is included, and the TLV includes a failure parameter of the first forwarding device.
  • an SNC including:
  • a receiving unit configured to receive a notification message sent by the first forwarding device, where the notification message includes a fault parameter of the first forwarding device, and the fault parameter of the first forwarding device includes a device identifier of the first forwarding device, a port identifier of the port on which the first forwarding device is degraded and a degradation value of the port identified by the port;
  • a processing unit configured to determine, according to the device identifier and the port identifier, at least one forwarding path of the port identified by the port identifier;
  • An acquiring unit configured to acquire a fault parameter of another forwarding device except the first forwarding device on one of the at least one forwarding path, where the fault parameter of the other forwarding device includes the device of the other forwarding device Identifying a port identifier of a port of the other forwarding device on the one forwarding path and a degradation value of a port on the one forwarding path;
  • the processing unit is further configured to determine, according to the fault parameter of the first forwarding device, and the fault parameter of the other forwarding device except the first forwarding device on the one forwarding path, whether to update the one forwarding path .
  • the processing unit is configured to:
  • the processing unit is configured to:
  • the notification message is an asynchronous message of an OpenFlow OpenFlow protocol
  • the notification message A type-length-value TLV having a type value of 35 is included, and the TLV includes a failure parameter of the first forwarding device.
  • a third aspect provides a method for troubleshooting a forwarding device, including:
  • the forwarding device sends a notification message to the SNC, where the notification message includes a fault parameter of the forwarding device, the fault parameter of the forwarding device includes a device identifier of the forwarding device, and a port identifier of the port of the forwarding device that is degraded and Determining a value of the port identified by the port identifier;
  • the forwarding device receives a path setup message sent by the SNC, where the path setup message includes path information of the updated forwarding path.
  • the notification message is an asynchronous message of an OpenFlow OpenFlow protocol, and the notification message includes a type-length-value TLV of type value 35, where the TLV includes The fault parameter of the forwarding device.
  • a forwarding device including:
  • a sending unit configured to send a notification message to the software-defined network SDN controller SNC, where the notification message includes a fault parameter of the forwarding device, the fault parameter of the forwarding device includes a device identifier of the forwarding device, and the forwarding device a port identifier of the degraded port and a degraded value of the port identified by the port identifier;
  • a receiving unit configured to receive a path setup message sent by the SNC, where the path setup message includes path information of the updated forwarding path.
  • the notification message is an asynchronous message of an OpenFlow OpenFlow protocol, and the notification message includes a type-length-value TLV having a type value of 35, where the TLV includes The fault parameter of the forwarding device.
  • a communication system comprising the controller SNC of the second aspect and the forwarding device of the fourth aspect.
  • An embodiment of the present invention provides a method, a device, and a controller for processing a fault of a forwarding device.
  • the SNC receives a notification message sent by the first forwarding device, where the notification message includes a fault parameter of the first forwarding device, and the fault parameter of the first forwarding device includes The device identifier of the first forwarding device, the port identifier of the port on which the first forwarding device is degraded, and the degraded value of the port identified by the port identifier, and determining, according to the device identifier and the port identifier, at least one forwarding of the port identified by the port identifier
  • the path obtains the fault parameter of the forwarding device other than the first forwarding device on the forwarding path of the at least one forwarding path, and the fault parameter of the other forwarding device includes the device identifier of the other forwarding device, and the other forwarding device is on a forwarding path.
  • the controller determines whether the update is needed according to the fault parameter of the first forwarding device and the fault parameter of the forwarding device other than the first forwarding device on a forwarding path. This one forwarding path, so no The traditional transmission of the fault information between the forwarding devices is performed, and the fault information of the forwarding device is notified to the controller, so that the controller calculates the updated forwarding path, which can solve the problem that the fault information transmission time is caused by the transmission of the fault by the forwarding device, so that the Calculate the problem of low efficiency of the forwarding path.
  • Figure 1 is a diagram of an SDN network architecture
  • FIG. 2 is a schematic flowchart of a method for transmitting fault information according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of interface definition in an SDN network architecture
  • FIG. 4 is a schematic diagram of a packet forwarding path in an SDN network
  • FIG. 5 is a schematic flowchart of another method for transmitting fault information according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a signal flow direction of a method for transmitting fault information according to an embodiment of the present invention
  • FIG. 7 is a schematic flowchart of still another method for transmitting fault information according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a controller according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a forwarding device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a controller according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a forwarding device according to an embodiment of the present invention.
  • a device can be divided into an SNC and a forwarding device, and the forwarding device can be, for example, a network switch.
  • An SNC can control multiple forwarding devices.
  • the controller communicates with the forwarding device through the southbound interface.
  • the southbound interface can be an OpenFlow (English: OpenFlow) protocol.
  • the SNC is the control device for the SDN network.
  • the forwarding device is responsible for forwarding packets based on control information sent by the SNC through the southbound interface.
  • the embodiment of the present invention provides a method for processing a fault of a forwarding device, as shown in FIG. 2, including:
  • the SNC receives the notification message sent by the first forwarding device, where the notification message includes a fault parameter of the first forwarding device, where the fault parameter of the first forwarding device includes the device identifier of the first forwarding device, and the port of the first forwarding device that is degraded.
  • the port ID and the port ID identify the degradation value of the port.
  • the SNC determines, according to the device identifier and the port identifier, at least one forwarding path of the port identified by the port identifier.
  • the SNC obtains a fault parameter of the forwarding device other than the first forwarding device in the forwarding path of the at least one forwarding path, where the fault parameter of the other forwarding device includes the device identifier of the other forwarding device, and the other forwarding device is on a forwarding path. Port ID of the port and the degradation value of the port on a forwarding path.
  • the SNC determines whether the one forwarding path needs to be updated according to the fault parameter of the first forwarding device and the fault parameter of the forwarding device other than the first forwarding device on one forwarding path.
  • the SNC can be a network switch.
  • the notification message may be sent to the controller SNC, where the notification message includes the fault parameter of the first forwarding device.
  • the first fault parameter includes a device identifier of the first forwarding device, a port identifier of the port on which the degradation occurs, and a degradation value of the port identified by the port identifier.
  • the degradation value here may be used to represent the fault type and the quantized value of the fault generated by the first forwarding device.
  • the first forwarding device generates a port error
  • the degradation value may be: a bit error rate of 20%.
  • the network switch 1 detects the port error through the CRC check, and may send a notification message to the SNC, where the notification message includes the failure of the network switch 1.
  • Location, fault status, and fault parameters may be a device identifier and a port identifier used to identify the network switch 1
  • the fault state may be a fault
  • the fault parameter may include a degradation value of the fault generated by the network switch 1 port, for example, a port error rate of the port.
  • the port error may be due to the fact that the signal changes, the decay changes the voltage of the signal, causing the signal to be damaged during transmission, causing errors, and the pulse caused by alternating current or lightning, transmission equipment failure and other factors may cause Error code.
  • the network switch may also generate a port frame loss fault, and the frame erasure rate (FER) may reflect the performance of the network switch when overloaded.
  • the fault parameter of the forwarding device is The frame loss rate, which is the percentage of frames that the network switch cannot forward due to lack of resources under continuous load conditions.
  • the network switch may also generate a single fiber fault, that is, the fiber of a port of the network switch generates a physical fault, for example, the fiber is disconnected from the port, and the fault parameter may be a single fiber fault, and the fault degradation value is zero.
  • the control plane and the data plane are separated, and the southbound interface and the east-west interface are also defined at the same time.
  • the interface here is not an interface in a physical sense, and can be understood as a protocol.
  • the southbound interface is used for communication between the controller and the forwarding device, that is, the control plane and the forwarding plane.
  • the east-west interface is used for communication between the controller and the controller, that is, the cooperative work between the control planes.
  • the fault parameter sent by the SNC receiving and forwarding device may be a fault parameter of a type-length-value (TLV) format sent by the forwarding device through the OpenFlow protocol.
  • TLV type-length-value
  • the format of the TLV can be as shown in Table 1 below:
  • the TLV header (English: header) may include a version number (English: version), a TLV type, a TLV string length (information string length), and a xid.
  • the embodiment of the present invention provides a TLV.
  • the type may be 35 to indicate that the TLV information string carries fault information of the device.
  • the version number indicates the version number of the OpenFlow protocol, for example, OpenFlow1.4.0; xid indicates the serial number of the data packet where the TLV is located; and the TLV information string length indicates the length of the TLV, which may be 16 bits.
  • the TLV information string includes a switch identifier (English: switch ID) and a port identifier of the degraded port (English: port ID), so that the SNC removes or replaces the forwarding path related to the failed port according to the switch identifier and the port identifier. .
  • the TLV information string may further include a fault parameter (fault_para), where the fault parameter may be a bit error rate, a frame loss rate, or a single fiber fault, etc., where the fault parameter is a bit error rate and a frame loss rate, It can be expressed as a percentage or as a percentage ratio.
  • a single fiber fault can be represented by 0 or other values.
  • the TLV information string can also be in a fault state (fault_state). The fault state can be 0 or 1, and 1 indicates that the fault has occurred. , 0 means fault recovery.
  • the SNC may determine, according to the device identifier of the forwarding device and the port identifier of the degraded port, the port identified by the port identifier that is degraded by the forwarding device. At least one forwarding path.
  • the forwarding path refers to: the path of the data packet transmitted/forwarded in the network by one stream, the first network switch that the data packet enters the network, the Nth switch of the data packet and the data packet, and the data packet from the first network switch. Transferring to the second, third to N-1th switches passing through the Nth network switch, and the link between adjacent switches.
  • the SNC has the device, port, and link information of the network switch, where the port is the network interface that transmits the data packet between the OpenFlow process and the network, and the network switches are logically connected to each other through the OpenFlow port, and the SNC is Each network switch dimension Protect the corresponding flow table, the flow table is composed of a plurality of flow entries, each flow entry is a forwarding rule, and the data packet entering the network switch obtains the forwarded destination port by querying the flow table, so when the SNC is in When the device identifier of the network switch and the port identifier of the degraded port are known, at least one forwarding path of the port identified by the port identifier degraded by the network switch may be determined according to the device identifier and the port identifier, that is, the port is determined. Associated at least one logical flow entry through multiple network switches.
  • the SNC may acquire, according to the at least one forwarding path determined in step 202, one of the at least one forwarding path.
  • the fault parameter of the other forwarding device outside the first forwarding device, the fault parameter of the other forwarding device includes the device identifier of the other forwarding device, and the port of the port of the other forwarding device on a forwarding path identifies the port on the one forwarding path. Degraded value.
  • step 203 it is determined whether the one forwarding path needs to be updated in combination with the fault parameter of the first forwarding device and the fault parameter sent by another forwarding device on one forwarding path.
  • the SNC may calculate the total degradation value of the port on a forwarding path according to the degradation value of the port identified by the port identifier of the first forwarding device and the degradation value of the port of the other forwarding device on a forwarding path, if a forwarding path is used.
  • the SNC updates the first forwarding path when the total degradation value of the port is greater than a preset threshold.
  • the first implementation of the SNC updating the first forwarding path is: the SNC calculates the updated first forwarding path, removes the first forwarding path, and establishes the updated first forwarding path according to the updated first forwarding path; The SNC replaces the first forwarding path with the backup path of the first forwarding path, so as to quickly optimize all the forwarding paths related to the fault in the network, and quickly switch to other normal paths, and of course, may also include other implementations. This is not limited.
  • the fault parameter of the first forwarding device is the port error rate of the first port of the first forwarding device
  • the fault parameters of the other forwarding device include the same forwarding path as the first port.
  • the port error rate of the second port sent by the second forwarding device the SNC can superimpose the port error rate on the same path. If the erroneous bit rate is greater than the preset threshold, the SNC needs to remove the same forwarding.
  • the path deletes the forwarding rule related to the same forwarding path in the SNC, that is, deletes the flow entry related to the same forwarding path, and then re-defines the forwarding rule, that is, re-determines the forwarding path to quickly switch to other normal paths. Then, the SNC sends a new forwarding rule to the forwarding device on the newly established path, so that the packet to be forwarded is not forwarded through the forwarding path where the degraded port is located.
  • the SNC corresponds to four network switches, namely S1, S2, S3, and S4, and S1 is sequentially connected to S2, S3 to S4, and S1 detects that there is a bit error in port 1, and the bit error rate of port 1 is greater than Preset threshold set by the network switch
  • the value of S1 reports the port error rate of port 1 to the SNC.
  • S2 Before S1 reports the fault parameter, S2 also reports the fault parameter to the SNC because the port error rate of the port 2 exceeds the preset threshold.
  • the error rate of port 2 of S2 does not reach the fault parameter before the fault parameter of port 1 is reported by S1.
  • the default rate set by the SNC exceeds 10%.
  • the forwarding path associated with port 1 of S1 is also related to port 2 of S2.
  • the SNC finds that the port error rate of port 1 of S1 and the port 2 of S2 after S1 report the fault parameter. If the sum of the port error rates is greater than the preset condition by 10%, the SNC determines that the path of S1-S2-S3-S4 where port 1 and port 2 are located needs to be removed, and rebuilds the path, for example, port 3 of S1. At the same time, it is connected to the port 4 of the S4, and the SNC can create the paths S1-S4 for the ports 4 to S4 of the S1.
  • the path can be other paths as long as the packets to be forwarded do not pass through the ports 1 to S2 of the S1.
  • the control information of the flow entry may be sent to the S1, S2, S3, and S4.
  • the flow entry of the reconstructed path may be sent to the S1 and S4.
  • the forwarding path may have a primary path and a backup path.
  • the SNC may send a handover message to the forwarding device.
  • the message carries a switching flag to indicate that the port of the forwarding device is switched from the primary path to the backup path, where the backup path may be pre-computed and stored in the forwarding device, or the SNC may determine that the preset condition is met.
  • the path information of the backup path is calculated, and the switch message includes not only the switch mark but also the path information of the backup path.
  • the controller may receive another notification message sent by the forwarding device through the southbound interface with the forwarding device, and the other notification message includes a fault parameter used by the forwarding device to indicate fault recovery.
  • the fault parameter includes a fault location for recovering the fault, the fault location includes a device identifier and a port identifier for recovering the fault, and may also include a fault state, where the fault state is fault recovery, and then the fault that is saved in the controller is deleted according to the fault parameter indicating the fault recovery.
  • the fault parameter of the port That is, after the network switch detects the fault and notifies the SNC, if the fault is recovered, it also needs to report to the SNC, so that the SNC deletes the previously saved fault parameters.
  • the network switch 1 needs to notify the SNC of the fault recovery, so that the SNC is in establishing the path.
  • port 1 of the network switch 1 is taken into consideration. For example, if the port 2 of the network switch 1 has a port error and the bit error rate is high, and the fault parameter is notified to the SNC, the switch may need to recover the fault because the switch recovers the fault by means of error detection and correction.
  • the SNC is notified to the SNC, and after obtaining the notification message of the failure recovery, the SNC deletes the fault parameter indicated by the notification message.
  • each SNC corresponds to multiple forwarding devices for forwarding, and when forwarding packets to the destination device, there may be more than one SNC.
  • Controlled forwarding The device is forwarded through the forwarding device of at least two controllers. Therefore, the fault parameter of the failed forwarding device needs to be notified to all other SNCs through the SNC to which it belongs, that is, the SNC receives the forwarding. After the fault parameter is sent by the device, the fault parameter needs to be notified to other SNCs. After receiving the fault parameter, any SNC in the other SNCs will pass the forwarding device under the two SNCs.
  • the fault parameter notified to other SNCs may also be a parameter for restoring the fault, so that the fault parameters that are now restored again are saved before other SNCs are deleted.
  • the embodiment of the present invention further includes:
  • the SNC sends a fault parameter of the first forwarding device to the other SNC through an east-west interface with another SNC.
  • the SNC needs to send the fault parameter to the other SNC through the east-west interface when transmitting the fault parameter to another SNC.
  • the forwarding device 1 under the control of two SNCs: SNC1, SNC2, and SNC1 and the forwarding device 2 under the control of the SNC2 are used as an example, and the forwarding device 1 and the forwarding device 2 may be multiple, and it is known from steps 201 to 204.
  • the signal flow diagram between SNC1, SNC2, forwarding device 1 and forwarding device 2 can be as shown in FIG. 6.
  • An embodiment of the present invention provides a method for processing a fault of a forwarding device, where the SNC receives a notification message sent by the first forwarding device, where the notification message includes a fault parameter of the first forwarding device, and the fault parameter of the first forwarding device includes the first forwarding device.
  • the fault parameters of the other forwarding device include the device identifier of the other forwarding device, and the port identifier of the port of the other forwarding device on a forwarding path. And determining, by the controller according to the fault parameter of the first forwarding device and the fault parameter of the forwarding device other than the first forwarding device, on the forwarding path of the first forwarding device, determining whether the forwarding path needs to be updated. In this way, without passing the traditional pass The fault information is transmitted between the transmitting devices, and the fault information of the forwarding device is notified to the controller, so that the controller calculates the updated forwarding path, which can solve the problem that the fault information transmission time is caused by the transmission of the fault by the forwarding device, so that the forwarding path efficiency is recalculated. Low problem.
  • the embodiment of the present invention further uses a method for troubleshooting a forwarding device, as shown in FIG. 7, including:
  • the forwarding device sends a notification message to the SNC, where the notification message includes a fault parameter of the forwarding device, and the fault parameter of the forwarding device includes the device identifier of the forwarding device, the port identifier of the port on which the forwarding device is degraded, and the port identifier identified by the port identifier. value.
  • the forwarding device receives a path setup message sent by the SNC, where the path setup message includes path information of the updated forwarding path.
  • the forwarding device when the forwarding device detects the local fault, the forwarding device sends a notification message to the SNC through the southbound interface with the SNC, where the notification message includes a fault parameter of the forwarding device, and the notification message may be an OpenFlow OpenFlow protocol.
  • the notification message includes a TLV of type 35, and the TLV includes a failure parameter of the forwarding device.
  • the forwarding device when the failback of the forwarding device is detected, the forwarding device sends another notification message to the SNC, and the other notification message is used to cause the controller to delete the previously saved fault parameter.
  • the embodiment of the present invention provides a method for processing a fault of a forwarding device.
  • the forwarding device sends a notification message to the SNC.
  • the notification message includes a fault parameter of the forwarding device.
  • the fault parameter of the forwarding device includes the device identifier of the forwarding device, and the port of the forwarding device is degraded.
  • the port identifier and the port identifier identify the degraded value of the port.
  • the forwarding device receives the path setup message sent by the SNC, and the path setup message includes the path information of the updated forwarding path, so that the device does not need to be forwarded through the conventional technology.
  • the fault parameter is transmitted, and the fault parameter of the forwarding device is notified to the SNC, so that the controller calculates a new forwarding path, which can solve the problem that the fault information transmission time is caused by the transmission of the fault by the forwarding device, so that the recalculation of the forwarding path is inefficient.
  • the embodiment of the present invention further provides a controller 80, as shown in FIG. 8, comprising:
  • the receiving unit 801 is configured to receive a notification message that is sent by the first forwarding device, where the notification message includes a fault parameter of the first forwarding device, where the fault parameter of the first forwarding device includes the device identifier of the first forwarding device, and the first forwarding device is degraded.
  • the processing unit 802 is configured to determine, according to the device identifier and the port identifier, at least one forwarding path of the port identified by the port identifier;
  • the obtaining unit 803 is configured to acquire a fault parameter of the forwarding device other than the first forwarding device in the forwarding path of the at least one forwarding path, where the fault parameter of the other forwarding device includes the device identifier of the other forwarding device, and the other forwarding device is in the The port identifier of the port on the forwarding path and the degradation value of the port on one forwarding path;
  • the processing unit 802 is further configured to determine, according to a fault parameter of the first forwarding device, and a fault parameter of another forwarding device other than the first forwarding device on a forwarding path, whether to need to update a forwarding path.
  • the receiving unit 801 can be used to:
  • the notification message sent by the forwarding device is received through the southbound interface with the forwarding device.
  • Processing unit 802 can be used to:
  • the first forwarding path is updated.
  • processing unit 802 can be configured to:
  • the sending unit 804 is configured to send, by using the east-west interface between the other SNCs, fault parameters to other SNCs.
  • the notification message is an asynchronous message of the OpenFlow OpenFlow protocol, and the notification message includes a type-length-value TLV of type 35, and the TLV includes a fault parameter of the first forwarding device.
  • An embodiment of the present invention provides a controller SNC, which receives, by using an SNC, a notification message sent by a first forwarding device, where the notification message includes a fault parameter of the first forwarding device, and the fault parameter of the first forwarding device includes a device identifier of the first forwarding device.
  • the controller determines whether the forwarding path needs to be updated according to the fault parameter of the first forwarding device and the fault parameter of the forwarding device other than the first forwarding device on a forwarding path, so that the controller does not need to update the forwarding path.
  • the embodiment of the present invention further provides a forwarding device 90, as shown in FIG. 9, comprising:
  • the sending unit 901 is configured to send a notification message to the software-defined network SDN controller SNC, where the notification message includes a fault parameter of the forwarding device, the fault parameter of the forwarding device includes a device identifier of the forwarding device, and a port identifier of the port of the forwarding device that is degraded and The deterioration value of the port identified by the port identifier;
  • the receiving unit 902 is configured to receive a path setup message sent by the SNC, where the path setup message includes path information of the updated forwarding path.
  • the sending unit 901 can be configured to:
  • the sending unit 901 is further configured to:
  • the forwarding device detects the failure recovery, sending another notification message to the SNC, the another notification message is used to cause the SNC to delete the fault parameter;
  • the notification message is an asynchronous message of the OpenFlow OpenFlow protocol, and the notification message includes a type-length-value TLV with a type value of 35, and the TLV includes a fault parameter of the forwarding device.
  • the embodiment of the present invention provides a forwarding device, where the forwarding device sends a notification message to the SNC, where the notification message includes a fault parameter of the forwarding device, the fault parameter of the forwarding device includes the device identifier of the forwarding device, and the port identifier of the port on which the forwarding device is degraded and The port identifier identifies the degraded value of the port, and the forwarding device receives the path setup message sent by the SNC.
  • the path setup message includes the path information of the updated forwarding path, so that the fault parameter is not transmitted between the forwarding devices by using the traditional technology.
  • the faulty parameter of the forwarding device is notified to the SNC, so that the controller calculates a new forwarding path, which can solve the problem that the fault information transmission time is caused by the transmission of the fault by the forwarding device, so that the recalculation of the forwarding path is inefficient.
  • the embodiment of the present invention further provides a controller SNC10, as shown in FIG. 10 is a schematic structural diagram of the SNC.
  • the specific embodiment of the present invention does not limit the specific implementation of the SNC, and the SNC may include:
  • the processor 101, the communication interface 102, and the memory 103 are connected by a bus 104.
  • the communication interface 102 is configured to communicate with the forwarding device, such as with a network switch.
  • the processor 101 is configured to execute program code to perform the related steps in the method embodiments shown in FIG. 2 and FIG. 5 above.
  • the processor 101 may be a central processing unit (CPU).
  • the memory 103 is used to store the program 105.
  • the memory 103 may include a volatile memory (English: volatile memory), such as random-access memory (RAM); Can include non-volatile memory (English: non-volatile memory), such as read-only memory (English: read-only memory, ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, HDD Or a solid state drive (SSD); the memory 103 may also include a combination of the above types of memory.
  • the program 105 may specifically include:
  • the fault parameter of the first forwarding device includes the device identifier of the first forwarding device, and the port identifier and port of the port on which the first forwarding device is degraded The degraded value of the identified port;
  • the program 105 performs, according to the fault parameter of the first forwarding device, and the fault parameter of the other forwarding device except the first forwarding device on a forwarding path, determining whether a forwarding path needs to be updated may include :
  • the first forwarding path is updated.
  • the updating, by the program 105, the first forwarding path may include:
  • the notification message is an asynchronous message of the OpenFlow OpenFlow protocol, and the notification message includes a type-length-value TLV of type 35, and the TLV includes a fault parameter of the first forwarding device.
  • An embodiment of the present invention provides an SNC, which receives a notification message sent by a first forwarding device, where the notification message includes a fault parameter of the first forwarding device, and the fault parameter of the first forwarding device includes a device identifier of the first forwarding device, and the first forwarding device Determining the port identifier of the degraded port and the degraded value of the port identified by the port identifier, determining at least one forwarding path of the port identified by the port identifier according to the device identifier and the port identifier, and acquiring one of the at least one forwarding path Fault parameters of other forwarding devices except the first forwarding device on the path, other forwarding
  • the fault parameter of the device includes the device identifier of the other forwarding device, the port identifier of the port of the other forwarding device on a forwarding path, and the degradation value of the port on a forwarding path.
  • the controller performs the forwarding parameter according to the failure parameter of the first forwarding device.
  • a failure parameter of the forwarding device other than the first forwarding device is determined to determine whether the forwarding path needs to be updated, so that the failure information is not transmitted through the traditional forwarding device, but the failure information of the forwarding device is notified to the control.
  • the controller can calculate the updated forwarding path, and can solve the problem that the fault information transmission time is caused by the transmission of the fault by the forwarding device, so that the recalculation of the forwarding path is inefficient.
  • the embodiment of the present invention provides a software-defined network SDN forwarding device 11, which may be a network switch, and FIG. 11 is a schematic structural diagram of a forwarding device. Illustrated by a network switch, the network switch can be comprised of a processor 111, a memory 112, an interface circuit 113, and a bus 114 that connects the processor, memory, and interface circuitry.
  • the processor 111 may be (central processing unit, CPU); the memory is used to store the running configuration, the flow table, etc.; the interface circuit is an internal circuit of each port of the network switch.
  • the CPU may apply the OpenFlow protocol and send a notification message to the SNC through the port connected to the SNC, where the notification message includes a fault parameter of the forwarding device, and the fault parameter of the forwarding device includes The device identifier of the forwarding device, the port identifier of the port on which the device is degraded, and the degraded value of the port identified by the port identifier, and then receives the path setup message sent by the SNC, where the path setup message includes the path information of the updated forwarding path.
  • the notification message is an asynchronous message of the OpenFlow OpenFlow protocol, and the notification message includes a type-length-value TLV of type 35, and the TLV includes a fault parameter of the forwarding device.
  • the embodiment of the present invention provides a forwarding device, where the forwarding device sends a notification message to the SNC, where the notification message includes a fault parameter of the forwarding device, the fault parameter of the forwarding device includes the device identifier of the forwarding device, and the port identifier of the port on which the forwarding device is degraded and The port identifier identifies the degraded value of the port, and the forwarding device receives the path setup message sent by the SNC.
  • the path setup message includes the path information of the updated forwarding path, so that the fault parameter is not transmitted between the forwarding devices by using the traditional technology.
  • the SNC is notified of the fault parameter of the forwarding device, so that the SNC calculates a new forwarding path, which can solve the problem that the fault information transmission time is caused by the transmission of the fault by the forwarding device, so that the recalculation of the forwarding path is inefficient.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit.
  • All or part of the steps of implementing the above method embodiments may be implemented by hardware related to the program instructions.
  • the foregoing program may be stored in a computer readable storage medium.
  • the processor executes the embodiment including the method embodiment.
  • the foregoing storage medium includes: a USB flash drive (English: USB flash drive), a hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, and the like, which can store program codes.

Landscapes

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

Abstract

一种转发设备故障处理的方法、设备和控制器，涉及通信领域，能够解决通过转发设备传递故障造成故障信息传递耗时，使得重新计算转发路径效率低的问题。其方法为：通过SNC接收第一转发设备发送的通知消息，通知消息包括第一转发设备的故障参数，故障参数包括第一转发设备的设备标识，发生劣化的端口的端口标识及端口标识所标识的端口的劣化值，根据设备标识及端口标识，确定经过端口标识所标识的端口的至少一个转发路径，再根据第一转发设备的故障参数和一个转发路径上的其他转发设备的故障参数，确定是否需要更新这一个转发路径。本发明实施例用于转发设备故障处理。

Description

一种转发设备故障处理的方法、设备和控制器
本申请要求于2015年1月5日提交中国专利局、申请号为201510003991.3、发明名称为“一种转发设备故障处理的方法、设备和控制器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信领域，尤其涉及一种转发设备故障处理的方法、设备和控制器。
背景技术
在传统的网络架构中，由于硬件或软件原因导致某台转发设备产生了故障，例如转发设备端口误码故障、端口误帧故障和单纤故障等，需要将故障信息传递给其它设备时，往往依赖于协议报文来进行传递，以使得多个转发设备共同优化与此故障相关的报文转发路径。常用的协议报文为双向转发检测(英文：Bidirectional Forwarding Detection，BFD)协议，可以实现链路的快速收敛，确保业务的永续性。
以应用BFD协议传递端口循环冗余校验(英文：cyclic redundancy check，CRC)误码的方案为例。转发设备的端口上进行CRC误码检测，当端口检测到CRC误码后，通过BFD报文将误码信息发送给转发路径的入口节点。转发路径中的多个转发设备分别计算CRC误码，而后入口节点将正向转发路径的误码汇总计算误码率，进而确定误码率是否超过预设阈值决定是否触发转发路径和业务倒换。在此过程中，BFD报文通过多个转发设备才能到达入口节点，所以耗费的时间长，从而可能会使得业务中断，并且占用BFD系统硬件资源。
发明内容
本发明的实施例提供一种转发设备故障处理的方法、设备和控制器，能够解决故障信息传递耗时，使得重新计算转发路径效率低的问题。
为达到上述目的，本发明的实施例采用如下技术方案：
第一方面，提供一种转发设备故障处理的方法，包括：
软件定义网络(英文：software-defined networking，SDN)控制器接收第一转发设备发送的通知消息，所述通知消息包括所述第一转发设备的故障参数，所述第一转发 设备的故障参数包括所述第一转发设备的设备标识，所述第一转发设备的发生劣化的端口的端口标识及所述端口标识所标识的端口的劣化值；
所述SDN控制器(英文：SDN controller，SNC)根据所述设备标识及所述端口标识，确定经过所述端口标识所标识的端口的至少一个转发路径；
所述SNC获取所述至少一个转发路径中的一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，所述其他转发设备的故障参数包括所述其他转发设备的设备标识，所述其他转发设备在所述一个转发路径上的端口的端口标识及在所述一个转发路径上的端口的劣化值；
所述SNC根据所述第一转发设备的故障参数和所述一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，确定是否需要更新所述一个转发路径。
结合第一方面，在第一方面的第一种实现中，所述SNC根据第一转发设备的故障参数和所述一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，确定是否需要更新所述一个转发路径包括：
所述SNC根据所述第一转发设备的所述端口标识所标识的端口的劣化值和所述其他转发设备在所述一个转发路径上的端口的劣化值计算所述一个转发路径上端口的总劣化值；
若所述一个转发路径上端口的总劣化值大于预设阈值，则所述SNC更新所述第一转发路径。
结合第一方面或第一方面的第一种实现，在第一方面的第二种实现中，所述SNC更新第一转发路径包括：
所述SNC计算更新后的第一转发路径，拆除所述第一转发路径，并按照所述更新后的第一转发路径建立所述更新后的第一转发路径；
或，所述SNC用所述第一转发路径的备份路径替换所述第一转发路径。
结合第一方面，第一方面的第一种和第二种实现中的任意一个，在第一方面的第三种实现中，所述通知消息为开放流OpenFlow协议的异步消息，所述通知消息包括类型值为35的类型-长度-值TLV，所述TLV包括所述第一转发设备的故障参数。
第二方面，提供一种SNC，包括：
接收单元，用于接收第一转发设备发送的通知消息，所述通知消息包括所述第一转发设备的故障参数，所述第一转发设备的故障参数包括所述第一转发设备的设备标识，所述第一转发设备发生劣化的端口的端口标识及所述端口标识的端口的劣化值；
处理单元，用于根据所述设备标识及所述端口标识，确定经过所述端口标识所标识的端口的至少一个转发路径；
获取单元，用于获取所述至少一个转发路径中的一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，所述其他转发设备的故障参数包括所述其他转发设备的设备标识，所述其他转发设备在所述一个转发路径上的端口的端口标识及在所述一个转发路径上的端口的劣化值；
所述处理单元，还用于根据所述第一转发设备的故障参数和所述一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，确定是否需要更新所述一个转发路径。
结合第二方面，在第二方面的第一种实现中，所述处理单元用于：
根据所述第一转发设备的所述端口标识所标识的端口的劣化值和所述其他转发设备在所述一个转发路径上的端口的劣化值计算所述一个转发路径上端口的总劣化值；
若所述一个转发路径上端口的总劣化值大于预设阈值，则更新所述第一转发路径。
结合第二方面或第二方面的第一种实现，在第二方面的第二种实现中，所述处理单元用于：
计算更新后的第一转发路径，拆除所述第一转发路径，并按照所述更新后的第一转发路径建立所述更新后的第一转发路径；
或，用所述第一转发路径的备份路径替换所述第一转发路径。
结合第二方面，第二方面的第一种和第二种实现中的任意一个，在第二方面的第三种实现中，所述通知消息为开放流OpenFlow协议的异步消息，所述通知消息包括类型值为35的类型-长度-值TLV，所述TLV包括所述第一转发设备的故障参数。
第三方面，提供一种转发设备故障处理的方法，包括：
转发设备向SNC发送通知消息，所述通知消息包括所述转发设备的故障参数，所述转发设备的故障参数包括所述转发设备的设备标识，所述转发设备的发生劣化的端口的端口标识及所述端口标识所标识的端口的劣化值；
所述转发设备接收所述SNC发送的路径建立消息，所述路径建立消息包括更新后的转发路径的路径信息。
结合第三方面，在第三方面的一种实现中，所述通知消息为开放流OpenFlow协议的异步消息，所述通知消息包括类型值为35的类型-长度-值TLV，所述TLV包括所述转发设备的故障参数。
第四方面，提供一种转发设备，包括：
发送单元，用于向软件定义网络SDN控制器SNC发送通知消息，所述通知消息包括所述转发设备的故障参数，所述转发设备的故障参数包括所述转发设备的设备标识，所述转发设备的发生劣化的端口的端口标识及所述端口标识所标识的端口的劣化值；
接收单元，用于接收所述SNC发送的路径建立消息，所述路径建立消息包括更新后的转发路径的路径信息。
结合第四方面，在第四方面的一种实现中，所述通知消息为开放流OpenFlow协议的异步消息，所述通知消息包括类型值为35的类型-长度-值TLV，所述TLV包括所述转发设备的故障参数。
第五方面，提供一种通信系统，包括如第二方面所述的控制器SNC和第四方面所述的转发设备。
本发明实施例提供一种转发设备故障处理的方法、设备和控制器，通过SNC接收第一转发设备发送的通知消息，通知消息包括第一转发设备的故障参数，第一转发设备的故障参数包括第一转发设备的设备标识，第一转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值，根据设备标识及端口标识，确定经过端口标识所标识的端口的至少一个转发路径，再获取至少一个转发路径中的一个转发路径上除第一转发设备外的其他转发设备的故障参数，其他转发设备的故障参数包括其他转发设备的设备标识，其他转发设备在一个转发路径上的端口的端口标识及在一个转发路径上的端口的劣化值，控制器根据第一转发设备的故障参数和一个转发路径上除第一转发设备外的其他转发设备的故障参数，确定是否需要更新这一个转发路径，这样，不用通过传统的通过转发设备间传递故障信息，而是将转发设备的故障信息通知给控制器，使控制器计算更新后的转发路径，能够解决通过转发设备传递故障造成故障信息传递耗时，使得重新计算转发路径效率低的问题。
附图说明
图1为一种SDN网络架构图；
图2为本发明实施例提供的一种故障信息的传递方法流程示意图；
图3为一种SDN网络架构中的接口定义示意图；
图4为一种SDN网络中报文转发路径示意图；
图5为本发明实施例提供的另一种故障信息的传递方法流程示意图；
图6为本发明实施例提供的一种故障信息的传递方法信号流向示意图；
图7为本发明实施例提供的又一种故障信息的传递方法流程示意图；
图8为本发明实施例提供的一种控制器结构示意图；
图9为本发明实施例提供的一种转发设备结构示意图；
图10为本发明实施例提供的一种控制器结构示意图；
图11为本发明实施例提供的一种转发设备结构示意图。
具体实施方式
软件定义网络(英文：software-defined networking,SDN)是通过将控制平面和数据平面分离开来，分别由SDN控制器(英文：SDN controller，SNC)和转发设备实现，实现了网络流量的灵活控制。
在SDN网络中，设备可以分为SNC和转发设备，该转发设备例如可以为网络交换机(英文：network switch)。一个SNC可以控制多个转发设备。如图1所示，控制器和转发设备间通过南向接口通信。南向接口可以是开放流(英文：OpenFlow)协议。SNC为SDN网络的控制设备。转发设备主要负责根据SNC通过南向接口发送的控制信息转发报文。
应用上述网络结构，本发明实施例提供一种转发设备故障处理的方法，如图2所示，包括：
201、SNC接收第一转发设备发送的通知消息，通知消息包括第一转发设备的故障参数，第一转发设备的故障参数中包括第一转发设备的设备标识，第一转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值。
202、SNC根据设备标识及端口标识，确定经过端口标识所标识的端口的至少一个转发路径。
203、SNC获取至少一个转发路径中的一个转发路径上除第一转发设备外的其他转发设备的故障参数，其他转发设备的故障参数包括其他转发设备的设备标识，其他转发设备在一个转发路径上的端口的端口标识及在一个转发路径上的端口的劣化值。
204、SNC根据第一转发设备的故障参数和一个转发路径上除第一转发设备外的其他转发设备的故障参数，确定是否需要更新该一个转发路径。
其中，SNC可以为网络交换机。当第一转发设备检测到该转发设备故障时，可以向控制器SNC发送通知消息，该通知消息中就包括第一转发设备的故障参数。
第一故障参数包括第一转发设备的设备标识，发生劣化的端口的端口标识，以及端口标识所标识的端口的劣化值。这里的劣化值可以用于表征第一转发设备所产生的故障类型和故障的量化值，例如，第一转发设备产生端口误码，劣化值可以为：误码率20％。
对于步骤201，示例性的，在图1所示的网络结构中，假设网络交换机1通过CRC校验检测到端口误码，便可以向SNC发送通知消息，该通知消息中包括网络交换机1的故障位置、故障状态和故障参数。其中，故障位置可以为用于标识网络交换机1的设备标识和端口标识，故障状态可以为故障产生，故障参数可以包括该网络交换机1端口产生故障的劣化值，例如端口的端口误码率。其中，端口误码是可以是由于信号传输中，衰变改变了信号的电压，致使信号在传输中遭到破坏，产生误码，且交流电或闪电造成的脉冲、传输设备故障及其他因素都可能导致误码。误码率也即比特错误率(英文：bit error rate，BER)是衡量数据在规定时间内数据传输精确性的指标，即比特错误率＝传输错误的比特/传输的比特总数。
再举例来说，网络交换机还有可能产生端口帧丢失的故障，而帧丢失率(英文：frame erasure rate，FER)可以反映网络交换机在过载时的性能状况，这时，转发设备的故障参数就可以为帧丢失率，表示网络交换机在持续负载状态下由于缺乏资源而无法转发的帧的百分比。此外，网络交换机还有可能产生单纤故障，即网络交换机某一端口的光纤产生物理故障，例如光纤与端口断开连接，故障参数可以为单纤故障，其故障的劣化值为0。
其中，在SDN网络结构中，在控制平面和数据平面分离的同时，也同时规定了南向接口和东西向接口，这里的接口并不是物理意义上的接口，可以理解为协议。如图3所示，其中，南向接口用于控制器与转发设备即控制平面与转发平面之间通信。东西向接口用于控制器与控制器之间通信，也就是控制平面之间的协同工作。这样，结合本发明实施例，转发设备在向SNC上报故障参数时，SNC可以通过南向接口接收转发设备发送的故障参数。
上述SNC接收转发设备发送的故障参数可以是转发设备通过OpenFlow协议发送的类型-长度-值(英文：type-length-value，TLV)格式的故障参数。
具体而言，该TLV的格式可以如下表1所示：
表1
Figure PCTCN2016070159-appb-000001
根据OpenFlow协议规定的TLV格式，其TLV头(英文：header)可以包括版本号(英文：version)、TLV type、TLV信息串长度(英文：information string length)以及xid。本发明实施例提出一种TLV，举例来说，type可以为35，以指示该TLV information string携带的是设备的故障信息。其中的版本号表示OpenFlow协议的版本号，例如可以为OpenFlow1.4.0；xid表示该TLV所在数据包的序列号；TLV information string length指示TLV长度，可以为16bits。
其中，TLV information string包括交换机标识(英文：switch ID)和发生劣化的端口的端口标识(英文：port ID)，以便于SNC根据交换机标识和端口标识拆除或替换与发生故障的端口相关的转发路径。
可选的，TLV information string还可以包括故障参数(fault_para)，该故障参数可以为误码率、或帧丢失率、或单纤故障等，其中，故障参数为误码率和帧丢失率时，可以以百分比表示，也可以以万分比表示，单纤故障可以以0或者其它值表示；可选的，TLV information string还可以故障状态(fault_state)，故障状态可以为0或1，1表示故障发生，0表示故障恢复。
进一步的，在步骤202中，当转发设备将故障参数发送给了SNC后，SNC可以根据转发设备的设备标识及发生劣化的端口的端口标识，确定经过转发设备发生劣化的端口标识所标识的端口的至少一个转发路径。其中转发路径指的是：一个流的数据包在网络中传输/转发的路径，路径由数据包进入网络的第一网络交换机、数据包转出网络的第N交换机及数据包从第一网络交换机转出至转入第N网络交换机过程中经过的第二、第三至第N-1个交换机、以及相邻交换机之间的链路。由于在OpenFlow网络中，SNC拥有网络交换机的设备、端口和链路信息，其中端口是OpenFlow进程和网络之间传递数据包的网络接口，网络交换机之间通过OpenFlow端口在逻辑上互相连接，SNC为每个网络交换机维 护其相应的流表，该流表由很多个流表项组成，每个流表项就是一个转发规则，进入网络交换机的数据包通过查询流表来获得转发的目的端口，因此，当SNC在获知网络交换机的设备标识和发生劣化的端口的端口标识时，可以根据该设备标识和端口标识确定经过该网络交换机发生劣化的端口标识所标识的端口的至少一个转发路径，也即确定与该端口相关的经过多个网络交换机的至少一个逻辑流表项。
再进一步的，SNC在确定了发生劣化的端口所在的至少一个转发路径后，在步骤203中，SNC可以根据步骤202中确定的至少一个转发路径获取该至少一个转发路径中的一个转发路径上除第一转发设备外的其它转发设备的故障参数，该其它转发设备的故障参数包括其他转发设备的设备标识，其他转发设备在一个转发路径上的端口的端口标识在该一个转发路径上的端口的劣化值。
再进一步的，在步骤203中，结合第一转发设备的故障参数和一个转发路径上的其它转发设备发送的故障参数，确定是否需要更新该一个转发路径。具体的，SNC可以根据第一转发设备的端口标识所标识的端口的劣化值和其它转发设备在一个转发路径上的端口的劣化值计算一个转发路径上端口的总劣化值，若一个转发路径上端口的总劣化值大于预设阈值，则SNC就更新第一转发路径。
SNC更新第一转发路径的第一种实现为：SNC计算更新后的第一转发路径，拆除第一转发路径，并按照更新后的第一转发路径建立更新后的第一转发路径；第二种实现为：SNC用第一转发路径的备份路径替换第一转发路径，以便于快速优化网络中与故障相关的所有转发路径，迅速切换至其它正常路径上，当然还可以包括其它实现，本发明对此不做限定。
针对第一种实现，举例来说，当第一转发设备的故障参数为第一转发设备第一端口的端口误码率时，假设其它转发设备的故障参数包括与第一端口在同一转发路径上的第二转发设备发送的第二端口的端口误码率，SNC可以将同一条路径上的端口误码率进行叠加，如果叠加后的误码率大于预设阈值，则SNC需要拆除该同一转发路径，删除SNC中与该同一转发路径相关的转发规则，也即删除与该同一转发路径相关的流表项，进而重新制定转发规则，即重新确定转发路径，以迅速切换至其它正常路径上。进而SNC向新建立路径上的转发设备发送新的转发规则，以使待转发的报文不经过发生劣化的端口所在的转发路径进行转发。
举例来说，SNC与4个网络交换机对应，分别为S1、S2、S3和S4，S1依次连接S2、S3至S4，S1检测到端口1存在误码故障，且端口1的误码率大于对网络交换机设定的预设阈 值，S1将端口1的端口误码率故障上报给SNC。在S1上报故障参数之前，S2也由于端口2的端口误码率超过预设阈值向SNC上报了故障参数，且在S1上报端口1的故障参数之前，S2的端口2的误码率没有达到在SNC中设定的误码率超过10％的预设条件。由于S1向SNC上报了故障参数，与S1的端口1相关的转发路径也与S2的端口2相关，SNC发现在S1上报故障参数后，S1的端口1的端口误码率与S2的端口2的端口误码率之和大于预设条件10％，那么SNC就确定由端口1和端口2所在的S1-S2-S3-S4的这条路径需要拆除，并重建这条路径，例如S1的端口3同时与S4的端口4连接，SNC便可以为S1的端口3至S4的端口4创建路径S1-S4，当然也可以为其它路径，只要使得将要转发的报文不经过S1的端口1至S2的端口2所在的路径。具体在拆除路径时可以通过向S1、S2、S3和S4下发删除流表项的控制信息，在重建路径时，可以通过向S1和S4下发重建路径的流表项。
针对第二种实现，示例性的，转发路径可以有一条主路径和备份路径，当经由发生故障的端口的主路径上端口的总劣化值大于预设阈值时，SNC可以向转发设备发送切换消息，该消息中携带一倒换标记，以指示转发设备的端口从主路径切换至备份路径，其中，备份路径可以是预先计算好存储在转发设备中的，也可以是SNC在确定满足预设条件时再计算备份路径的路径信息，这时切换消息中不仅包括倒换标记，还包括备份路径的路径信息。
再进一步的，当然，如果故障恢复的话，控制器可以通过与转发设备间的南向接口接收转发设备发送的另一通知消息，另一通知消息包括转发设备用于表示故障恢复的故障参数，该故障参数包括恢复故障的故障位置，故障位置包括恢复故障的设备标识和端口标识，还可以包括故障状态，该故障状态为故障恢复，进而根据表示故障恢复的故障参数删除控制器中保存的发生劣化的端口的故障参数。也即网络交换机在检测到故障并通知给SNC后，如果故障恢复，也需要向SNC上报，使得SNC删除之前保存的故障参数。
示例性的，当网络交换机1的端口1发生单纤故障后，由于人为干预对该故障进行了修复，使得故障恢复，那么网络交换机1需要将故障恢复通知给SNC，以便于SNC在建立路径时，将该网络交换机1的端口1纳入考虑范围。再比如，网络交换机1的端口2发生端口误码且误码率较高，将故障参数通知给SNC后，可能由于交换机通过检错纠错等方式恢复了该故障，那么交换机也需要将故障恢复通知给SNC，SNC在得到该故障恢复的通知消息后，将该通知消息所指示的故障参数删除。
此外，如图4所示，由于在SDN网络架构中，SNC可以有多个，每个SNC对应多个用于转发的转发设备，在将报文转发至目的设备时，可能会不只经过一个SNC控制下的转发 设备，而要经过至少两个控制器下的转发设备进行转发，因此，还需要将发生故障的转发设备的故障参数经过其所属的SNC通知给其它所有SNC，也就是说，SNC在接收到转发设备发送的故障参数后，需要将该故障参数分别通知给其它SNC，其它SNC中的任一SNC在接收到故障参数后，如果转发路径要经过两个SNC下的转发设备，该任一SNC就需要结合当前SNC中保存的自身的故障参数和接收到的另一SNC的故障参数，在确定故障参数满足一定预设条件时，重建经过多个SNC下的转发设备的转发路径，再将新的转发路径发送给该新转发路径涉及到的转发设备。当然，通知给其它SNC的故障参数也有可能是恢复故障的参数，以便于其它SNC删除之前保存现在又恢复的故障参数。
这样，在步骤204的基础上，如图5所示，本发明实施例还包括：
205、SNC通过与其它SNC之间的东西向接口向其它SNC发送第一转发设备的故障参数。
其中，在SNC与SNC之间传递故障参数时，由于是控制平面的协同工作，SNC在向另一SNC发送故障参数时，需要通过东西向接口向另一SNC发送故障参数。
这样，以两个SNC：SNC1、SNC2、SNC1控制下的转发设备1，SNC2控制下的转发设备2为例，转发设备1和转发设备2可以为多个，并由步骤201～步骤204可知，SNC1、SNC2、转发设备1和转发设备2之间的信号流程图可以如图6所示。
本发明实施例提供一种转发设备故障处理的方法，通过SNC接收第一转发设备发送的通知消息，通知消息包括第一转发设备的故障参数，第一转发设备的故障参数包括第一转发设备的设备标识，第一转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值，根据设备标识及端口标识，确定经过端口标识所标识的端口的至少一个转发路径，再获取至少一个转发路径中的一个转发路径上除第一转发设备外的其他转发设备的故障参数，其他转发设备的故障参数包括其他转发设备的设备标识，其他转发设备在一个转发路径上的端口的端口标识及在一个转发路径上的端口的劣化值，控制器根据第一转发设备的故障参数和一个转发路径上除第一转发设备外的其他转发设备的故障参数，确定是否需要更新该一个转发路径，这样，不用通过传统的通过转发设备间传递故障信息，而是将转发设备的故障信息通知给控制器，使控制器计算更新后的转发路径，能够解决通过转发设备传递故障造成故障信息传递耗时，使得重新计算转发路径效率低的问题。
与图2所示的实施例相对应的，本发明实施例还体用一种转发设备故障处理的方法，如图7所示，包括：
701、转发设备向SNC发送通知消息，通知消息包括转发设备的故障参数，转发设备的故障参数包括转发设备的设备标识，转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值。
702、转发设备接收SNC发送的路径建立消息，路径建立消息包括更新后的转发路径的路径信息。
具体的，当转发设备检测到本地故障时，转发设备通过与SNC之间的南向接口向SNC发送一通知消息，该通知消息包括转发设备的故障参数，且通知消息可以为开放流OpenFlow协议的异步消息，通知消息包括类型值为35的TLV，TLV包括转发设备的故障参数。
此外，当转发设备的检测到故障恢复时，转发设备向SNC发送另一通知消息，另一通知消息用于使控制器删除之前保存的故障参数。
本发明实施例中的转发设备和SNC的具体实现方式可以参见上述图2至图6所示的实现方式，此处不再赘述。
本发明实施例提供一种转发设备故障处理的方法，转发设备向SNC发送通知消息，通知消息包括转发设备的故障参数，转发设备的故障参数包括转发设备的设备标识，转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值，进而，转发设备接收SNC发送的路径建立消息，路径建立消息包括更新后的转发路径的路径信息，这样，不用通过传统技术中通过转发设备间传递故障参数，而是将转发设备的故障参数通知给SNC，使控制器计算新的转发路径，能够解决通过转发设备传递故障造成故障信息传递耗时，使得重新计算转发路径效率低的问题。
本发明实施例还提供一种控制器80，如图8所示，包括：
接收单元801，用于接收第一转发设备发送的通知消息，通知消息包括第一转发设备的故障参数，第一转发设备的故障参数包括第一转发设备的设备标识，第一转发设备发生劣化的端口的端口标识及端口标识的端口的劣化值；
处理单元802，用于根据设备标识及端口标识，确定经过端口标识所标识的端口的至少一个转发路径；
获取单元803，用于获取至少一个转发路径中的一个转发路径上除第一转发设备外的其他转发设备的故障参数，其他转发设备的故障参数包括其他转发设备的设备标识，其他转发设备在一个转发路径上的端口的端口标识及在一个转发路径上的端口的劣化值；
处理单元802，还用于根据第一转发设备的故障参数和一个转发路径上除第一转发设备外的其他转发设备的故障参数，确定是否需要更新一个转发路径。
可选的，接收单元801可以用于：
通过与转发设备间的南向接口接收转发设备发送的通知消息。
处理单元802可以用于：
根据第一转发设备的端口标识所标识的端口的劣化值和其他转发设备在一个转发路径上的端口的劣化值计算一个转发路径上端口的总劣化值；
若一个转发路径上端口的总劣化值大于预设阈值，则更新第一转发路径。
可选的，处理单元802可以用于：
计算更新后的第一转发路径，拆除第一转发路径，并按照更新后的第一转发路径建立更新后的第一转发路径；
或，用第一转发路径的备份路径替换第一转发路径。
可选的，还可以包括:发送单元804，用于与其它SNC之间的东西向接口向其它SNC发送故障参数。
可选的，通知消息为开放流OpenFlow协议的异步消息，通知消息包括类型值为35的类型-长度-值TLV，TLV包括第一转发设备的故障参数。
本发明实施例提供一种控制器SNC，通过SNC接收第一转发设备发送的通知消息，通知消息包括第一转发设备的故障参数，第一转发设备的故障参数包括第一转发设备的设备标识，第一转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值，根据设备标识及端口标识，确定经过端口标识所标识的端口的至少一个转发路径，再获取至少一个转发路径中的一个转发路径上除第一转发设备外的其他转发设备的故障参数，其他转发设备的故障参数包括其他转发设备的设备标识，其他转发设备在一个转发路径上的端口的端口标识及在一个转发路径上的端口的劣化值，控制器根据第一转发设备的故障参数和一个转发路径上除第一转发设备外的其他转发设备的故障参数，确定是否需要更新该一个转发路径，这样，不用通过传统的通过转发设备间传递故障信息，而是将转发设备的故障信息通知给控制器，使控制器计算更新后的转发路径，能够解决通过转发设备传递故障造成故障信息传递耗时，使得重新计算转发路径效率低的问题。
本发明实施例还提供一种转发设备90，如图9所示，包括：
发送单元901，用于向软件定义网络SDN控制器SNC发送通知消息，通知消息包括转发设备的故障参数，转发设备的故障参数包括转发设备的设备标识，转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值；
接收单元902，用于接收SNC发送的路径建立消息，路径建立消息包括更新后的转发路径的路径信息。
可选的，发送单元901可以用于：
通过与SNC之间的南向接口向SNC发送的通知消息。
可选的，发送单元901还可以用于：
当转发设备的检测到故障恢复时，向SNC发送另一通知消息，该另一通知消息用于使SNC删除故障参数；
可选的，通知消息为开放流OpenFlow协议的异步消息，通知消息包括类型值为35的类型-长度-值TLV，TLV包括转发设备的故障参数。
本发明实施例提供一种转发设备，转发设备向SNC发送通知消息，通知消息包括转发设备的故障参数，转发设备的故障参数包括转发设备的设备标识，转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值，进而，转发设备接收SNC发送的路径建立消息，路径建立消息包括更新后的转发路径的路径信息，这样，不用通过传统技术中通过转发设备间传递故障参数，而是将转发设备的故障参数通知给SNC，使控制器计算新的转发路径，能够解决通过转发设备传递故障造成故障信息传递耗时，使得重新计算转发路径效率低的问题。
本发明实施例还提供一种控制器SNC10，如图10所示为SNC的结构示意图，本发明具体实施例不对SNC的具体实现做限定，该SNC可以包括：
处理器(英文：pocessor)101，通信接口(英文：communications interface)102，存储器(英文：memory)103，总线104。
其中，处理器101，通信接口102，存储器103通过总线104连接。
通信接口102，用于与转发设备通信，比如与网络交换机通信。
处理器101，用于执行程序代码，以执行上述图2和图5所示的方法实施例中的相关步骤。
处理器101可能是一个中央处理器(英文：central processing unit，CPU)。
存储器103用于存放程序105，存储器103可能包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，RAM)；存储器103也 可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，HDD)或固态硬盘(英文：solid-state drive，SSD)；存储器103还可以包括上述种类的存储器的组合。程序105具体可以包括：
接收第一转发设备发送的通知消息，通知消息包括第一转发设备的故障参数，第一转发设备的故障参数包括第一转发设备的设备标识，第一转发设备发生劣化的端口的端口标识及端口标识的端口的劣化值；
根据设备标识及端口标识，确定经过端口标识所标识的端口的至少一个转发路径；
获取至少一个转发路径中的一个转发路径上除第一转发设备外的其他转发设备的故障参数，其他转发设备的故障参数包括其他转发设备的设备标识，其他转发设备在一个转发路径上的端口的端口标识及在一个转发路径上的端口的劣化值；
根据第一转发设备的故障参数和一个转发路径上除第一转发设备外的其他转发设备的故障参数，确定是否需要更新一个转发路径。
在本发明实施例中，可选的，程序105执行根据第一转发设备的故障参数和一个转发路径上除第一转发设备外的其他转发设备的故障参数，确定是否需要更新一个转发路径可以包括：
根据第一转发设备的端口标识所标识的端口的劣化值和其他转发设备在一个转发路径上的端口的劣化值计算一个转发路径上端口的总劣化值；
若一个转发路径上端口的总劣化值大于预设阈值，则更新第一转发路径。
在本发明实施例中，可选的，程序105执行更新第一转发路径可以包括：
计算更新后的第一转发路径，拆除第一转发路径，并按照更新后的第一转发路径建立更新后的第一转发路径；
或，用第一转发路径的备份路径替换第一转发路径。
在本发明实施例中，可选的，通知消息为开放流OpenFlow协议的异步消息，通知消息包括类型值为35的类型-长度-值TLV，TLV包括第一转发设备的故障参数。
本发明实施例提供一种SNC，接收第一转发设备发送的通知消息，通知消息包括第一转发设备的故障参数，第一转发设备的故障参数包括第一转发设备的设备标识，第一转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值，根据设备标识及端口标识，确定经过端口标识所标识的端口的至少一个转发路径，再获取至少一个转发路径中的一个转发路径上除第一转发设备外的其他转发设备的故障参数，其他转发 设备的故障参数包括其他转发设备的设备标识，其他转发设备在一个转发路径上的端口的端口标识及在一个转发路径上的端口的劣化值，控制器根据第一转发设备的故障参数和一个转发路径上除第一转发设备外的其他转发设备的故障参数，确定是否需要更新该一个转发路径，这样，不用通过传统的通过转发设备间传递故障信息，而是将转发设备的故障信息通知给控制器，使控制器计算更新后的转发路径，能够解决通过转发设备传递故障造成故障信息传递耗时，使得重新计算转发路径效率低的问题。
本发明实施例提供一种软件定义网络SDN转发设备11，该转发设备可以为网络交换机，如图11为转发设备的结构示意图。以网络交换机进行说明，该网络交换机可以处理器111、存储器112、接口电路113和连接处理器、存储器和接口电路的总线114组成。
其中，处理器111可以是(英文：central processing unit，CPU)；存储器用于存储运行配置、流表等；接口电路为网络交换机各端口的内部电路。
因此，在本发明实施例中，如果某一端口发生故障，则CPU可以应用OpenFlow协议并通过与SNC连接的端口向SNC发送通知消息，通知消息包括转发设备的故障参数，转发设备的故障参数包括转发设备的设备标识，转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值，进而接收SNC发送的路径建立消息，路径建立消息包括更新后的转发路径的路径信息。
在本发明实施例中，可选的，通知消息为开放流OpenFlow协议的异步消息，通知消息包括类型值为35的类型-长度-值TLV，TLV包括转发设备的故障参数。
本发明实施例提供一种转发设备，转发设备向SNC发送通知消息，通知消息包括转发设备的故障参数，转发设备的故障参数包括转发设备的设备标识，转发设备的发生劣化的端口的端口标识及端口标识所标识的端口的劣化值，进而，转发设备接收SNC发送的路径建立消息，路径建立消息包括更新后的转发路径的路径信息，这样，不用通过传统技术中通过转发设备间传递故障参数，而是将转发设备的故障参数通知给SNC，使SNC计算新的转发路径，能够解决通过转发设备传递故障造成故障信息传递耗时，使得重新计算转发路径效率低的问题。
在本申请所提供的几个实施例中，应该理解到，所揭露的设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所 显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接。
实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，处理器执行包括上述方法实施例的步骤；而前述的存储介质包括：USB闪存盘(英文：USB flash drive)、硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (18)

  1. 一种转发设备故障处理的方法，其特征在于，包括：
    软件定义网络控制器(SNC)接收第一转发设备发送的通知消息，所述通知消息包括所述第一转发设备的故障参数，所述第一转发设备的故障参数包括所述第一转发设备的设备标识，所述第一转发设备的发生劣化的端口的端口标识及所述端口标识所标识的端口的劣化值；
    所述SNC根据所述设备标识及所述端口标识，确定经过所述端口标识所标识的端口的至少一个转发路径；
    所述SNC获取所述至少一个转发路径中的一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，所述其他转发设备的故障参数包括所述其他转发设备的设备标识，所述其他转发设备在所述一个转发路径上的端口的端口标识及在所述一个转发路径上的端口的劣化值；
    所述SNC根据所述第一转发设备的故障参数和所述一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，确定是否需要更新所述一个转发路径。
  2. 根据权利要求1所述的方法，其特征在于，所述SNC根据第一转发设备的故障参数和所述一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，确定是否需要更新所述一个转发路径包括：
    所述SNC根据所述第一转发设备的所述端口标识所标识的端口的劣化值和所述其他转发设备在所述一个转发路径上的端口的劣化值计算所述一个转发路径上端口的总劣化值；
    若所述一个转发路径上端口的总劣化值大于预设阈值，则所述SNC更新所述第一转发路径。
  3. 根据权利要求1或2所述的方法，其特征在于，所述SNC更新第一转发路径包括：
    所述SNC计算更新后的第一转发路径，拆除所述第一转发路径，并按照所述更新后的第一转发路径建立所述更新后的第一转发路径；
    或，所述SNC用所述第一转发路径的备份路径替换所述第一转发路径。
  4. 一种转发设备故障处理的方法，其特征在于，包括：
    转发设备向软件定义网络控制器(SNC)发送通知消息，所述通知消息包括所述转发设备的故障参数，所述转发设备的故障参数包括所述转发设备的设备标识，所述转发设备的发生劣化的端口的端口标识及所述端口标识所标识的端口的劣化值；
    所述转发设备接收所述SNC发送的路径建立消息，所述路径建立消息包括更新后的转发路径的路径信息。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述通知消息为OpenFlow协议的异步消息，所述通知消息包括类型值为35的类型-长度-值(TLV)，所述TLV包括所述第一转发设备的故障参数。
  6. 一种软件定义网络控制器(SNC)，其特征在于，包括：
    接收单元，用于接收第一转发设备发送的通知消息，所述通知消息包括所述第一转发设备的故障参数，所述第一转发设备的故障参数包括所述第一转发设备的设备标识，所述第一转发设备发生劣化的端口的端口标识及所述端口标识的端口的劣化值；
    处理单元，用于根据所述设备标识及所述端口标识，确定经过所述端口标识所标识的端口的至少一个转发路径；
    获取单元，用于获取所述至少一个转发路径中的一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，所述其他转发设备的故障参数包括所述其他转发设备的设备标识，所述其他转发设备在所述一个转发路径上的端口的端口标识及在所述一个转发路径上的端口的劣化值；
    所述处理单元，还用于根据所述第一转发设备的故障参数和所述一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，确定是否需要更新所述一个转发路径。
  7. 根据权利要求6所述的SNC，其特征在于，所述处理单元用于：
    根据所述第一转发设备的所述端口标识所标识的端口的劣化值和所述其他转发设备在所述一个转发路径上的端口的劣化值计算所述一个转发路径上端口的总劣化值；
    若所述一个转发路径上端口的总劣化值大于预设阈值，则更新所述第一转发路径。
  8. 根据权利要求6或7所述的SNC，其特征在于，所述处理单元用于：
    计算更新后的第一转发路径，拆除所述第一转发路径，并按照所述更新后的第一转发路径建立所述更新后的第一转发路径；
    或，用所述第一转发路径的备份路径替换所述第一转发路径。
  9. 根据权利要求6-8任一项所述的SNC，其特征在于，所述通知消息为OpenFlow协议的异步消息，所述通知消息包括类型值为35的类型-长度-值(TLV)，所述TLV包括所述第一转发设备的故障参数。
  10. 一种转发设备，其特征在于，包括：
    发送单元，用于向软件定义网络控制器(SNC)发送通知消息，所述通知消息包括所述转发设备的故障参数，所述转发设备的故障参数包括所述转发设备的设备标识，所述转发设备的发生劣化的端口的端口标识及所述端口标识所标识的端口的劣化值；
    接收单元，用于接收所述SNC发送的路径建立消息，所述路径建立消息包括更新后的转发路径的路径信息。
  11. 根据权利要求10所述的转发设备，其特征在于，所述通知消息为OpenFlow协议的异步消息，所述通知消息包括类型值为35的类型-长度-值(TLV)，所述TLV包括所述转发设备的故障参数。
  12. 一种通信系统，其特征在于，包括如权利要求6～9所述的控制器SNC，和如权利要求10～11所述的转发设备。
  13. 一种软件定义网络控制器(SNC)，包括处理器和通信接口，其中
    所述处理器，用于：
    通过所述通信接口接收第一转发设备发送的通知消息，所述通知消息包括所述第一转发设备的故障参数，所述第一转发设备的故障参数包括所述第一转发设备的设备标识，所述第一转发设备发生劣化的端口的端口标识及所述端口标识的端口的劣化值；
    根据所述设备标识及所述端口标识，确定经过所述端口标识所标识的端口的至少一个转发路径；
    获取所述至少一个转发路径中的一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，所述其他转发设备的故障参数包括所述其他转发设备的设备标识，所述其他转发设备在所述一个转发路径上的端口的端口标识及在所述一个转发路径上的端口的劣化值；并
    根据所述第一转发设备的故障参数和所述一个转发路径上除所述第一转发设备外的其他转发设备的故障参数，确定是否需要更新所述一个转发路径。
  14. 根据权利要求13所述的SNC，其特征在于，所述处理器用于：
    根据所述第一转发设备的所述端口标识所标识的端口的劣化值和所述其他转发设备在所述一个转发路径上的端口的劣化值计算所述一个转发路径上端口的总劣化值；
    若所述一个转发路径上端口的总劣化值大于预设阈值，则更新所述第一转发路径。
  15. 根据权利要求13或14所述的SNC，其特征在于，所述处理器用于：
    计算更新后的第一转发路径，拆除所述第一转发路径，并按照所述更新后的第一转发路径建立所述更新后的第一转发路径；
    或，用所述第一转发路径的备份路径替换所述第一转发路径。
  16. 根据权利要求13-15任一项所述的SNC，其特征在于，所述通知消息为OpenFlow协议的异步消息，所述通知消息包括类型值为35的类型-长度-值(TLV)，所述TLV包括所述第一转发设备的故障参数。
  17. 一种转发设备，包括处理器，存储器和接口电路，其中，
    所述存储器用于存储流表；
    所述接口电路是所述转发设备的至少一个端口的电路；
    所述处理器，用于向软件定义网络控制器(SNC)发送通知消息，所述通知消息包括所述转发设备的故障参数，所述转发设备的故障参数包括所述转发设备的设备标识，所述转发设备的发生劣化的端口的端口标识及所述端口标识所标识的端口的劣化值，并接收所述SNC发送的路径建立消息，所述路径建立消息包括更新后的转发路径的路径信息。
  18. 根据权利要求17所述的转发设备，其特征在于，所述通知消息为OpenFlow协议的异步消息，所述通知消息包括类型值为35的类型-长度-值(TLV)，所述TLV包括所述转发设备的故障参数。
PCT/CN2016/070159 2015-01-05 2016-01-05 一种转发设备故障处理的方法、设备和控制器 WO2016110248A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP16734908.3A EP3232616B1 (en) 2015-01-05 2016-01-05 Failure processing method for forwarding device, and controller
US15/641,027 US10756958B2 (en) 2015-01-05 2017-07-03 Method, device, and controller for processing forwarding device faults received from forwarding devices on a forwarding path
US16/931,708 US11496355B2 (en) 2015-01-05 2020-07-17 Method for processing forwarding device fault, device, and controller

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510003991.3A CN105827419B (zh) 2015-01-05 2015-01-05 一种转发设备故障处理的方法、设备和控制器
CN201510003991.3 2015-01-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/641,027 Continuation US10756958B2 (en) 2015-01-05 2017-07-03 Method, device, and controller for processing forwarding device faults received from forwarding devices on a forwarding path

Publications (1)

Publication Number Publication Date
WO2016110248A1 true WO2016110248A1 (zh) 2016-07-14

Family

ID=56355530

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/070159 WO2016110248A1 (zh) 2015-01-05 2016-01-05 一种转发设备故障处理的方法、设备和控制器

Country Status (4)

Country Link
US (2) US10756958B2 (zh)
EP (1) EP3232616B1 (zh)
CN (1) CN105827419B (zh)
WO (1) WO2016110248A1 (zh)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105827419B (zh) * 2015-01-05 2020-03-10 华为技术有限公司 一种转发设备故障处理的方法、设备和控制器
US10313231B1 (en) 2016-02-08 2019-06-04 Barefoot Networks, Inc. Resilient hashing for forwarding packets
US10063407B1 (en) 2016-02-08 2018-08-28 Barefoot Networks, Inc. Identifying and marking failed egress links in data plane
US10103968B2 (en) * 2016-12-13 2018-10-16 Industrial Technology Research Institute Tree recovery method, controller and recording medium for software-defined network
US10237206B1 (en) 2017-03-05 2019-03-19 Barefoot Networks, Inc. Equal cost multiple path group failover for multicast
US10404619B1 (en) 2017-03-05 2019-09-03 Barefoot Networks, Inc. Link aggregation group failover for multicast
CN107682257A (zh) * 2017-11-21 2018-02-09 凌云天博光电科技股份有限公司 数据传输方法和系统
US11500678B2 (en) * 2018-09-17 2022-11-15 Hewlett Packard Enterprise Development Lp Virtual fibre channel port migration
US11252258B2 (en) * 2018-09-27 2022-02-15 Hewlett Packard Enterprise Development Lp Device-aware dynamic protocol adaptation in a software-defined network
WO2020091918A1 (en) * 2018-10-31 2020-05-07 Commscope Technologies Llc Systems and methods for automated network cabling integrity monitoring
CN111385120B (zh) 2018-12-29 2021-10-26 华为技术有限公司 一种确定转发故障位置的方法和设备
CN112039771A (zh) * 2019-06-03 2020-12-04 华为技术有限公司 一种基于链路误码的处理方法和装置
CN112860496A (zh) * 2019-11-27 2021-05-28 华为技术有限公司 故障修复操作推荐方法、装置及存储介质
CN111277440B (zh) * 2020-01-20 2022-04-08 新华三信息安全技术有限公司 网络设备
CN111385166A (zh) * 2020-02-21 2020-07-07 苏州浪潮智能科技有限公司 一种网络交换机测试方法、装置、设备及存储介质
CN113422735B (zh) * 2021-06-22 2022-08-05 恒安嘉新（北京）科技股份公司 负载均衡配置方法、汇聚分流器及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103346971A (zh) * 2013-06-19 2013-10-09 华为技术有限公司 数据转发方法、控制器、转发设备及系统
CN103795570A (zh) * 2014-01-23 2014-05-14 杭州华三通信技术有限公司 环形拓扑的堆叠交换机系统的单播报文恢复方法及装置
CN103891204A (zh) * 2013-12-31 2014-06-25 华为技术有限公司 链路倒换的方法和交换设备
CN103986651A (zh) * 2014-05-30 2014-08-13 杭州华三通信技术有限公司 一种软件定义网络控制器及其控制方法
CN104253745A (zh) * 2013-06-29 2014-12-31 华为技术有限公司 一种路由撤销方法和网络设备

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4209758B2 (ja) * 2003-11-20 2009-01-14 富士通株式会社 迂回通信経路設計方法
US7983173B2 (en) * 2004-05-10 2011-07-19 Cisco Technology, Inc. System and method for detecting link failures
JP2007235628A (ja) * 2006-03-01 2007-09-13 Fujitsu Ltd 伝送装置及び通信制御方法
US8176526B1 (en) * 2006-09-29 2012-05-08 Juniper Networks, Inc. Configurable redundant security device failover
US20090092054A1 (en) * 2007-10-09 2009-04-09 Compton Matthew C Method for providing notifications of a failing node to other nodes within a computer network
US8885463B1 (en) * 2011-10-17 2014-11-11 Juniper Networks, Inc. Path computation element communication protocol (PCEP) extensions for stateful label switched path management
CN103248645B (zh) * 2012-02-08 2018-03-16 深圳市腾讯计算机系统有限公司 Bt离线数据下载系统及方法
US9038151B1 (en) * 2012-09-20 2015-05-19 Wiretap Ventures, LLC Authentication for software defined networks
JPWO2014129624A1 (ja) * 2013-02-25 2017-02-02 日本電気株式会社 制御装置、通信システム、経路切替方法及びプログラム
US9276827B2 (en) * 2013-03-15 2016-03-01 Cisco Technology, Inc. Allocating computing resources based upon geographic movement
CN105827419B (zh) * 2015-01-05 2020-03-10 华为技术有限公司 一种转发设备故障处理的方法、设备和控制器

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103346971A (zh) * 2013-06-19 2013-10-09 华为技术有限公司 数据转发方法、控制器、转发设备及系统
CN104253745A (zh) * 2013-06-29 2014-12-31 华为技术有限公司 一种路由撤销方法和网络设备
CN103891204A (zh) * 2013-12-31 2014-06-25 华为技术有限公司 链路倒换的方法和交换设备
CN103795570A (zh) * 2014-01-23 2014-05-14 杭州华三通信技术有限公司 环形拓扑的堆叠交换机系统的单播报文恢复方法及装置
CN103986651A (zh) * 2014-05-30 2014-08-13 杭州华三通信技术有限公司 一种软件定义网络控制器及其控制方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3232616A4 *

Also Published As

Publication number Publication date
EP3232616A4 (en) 2017-12-27
CN105827419A (zh) 2016-08-03
US10756958B2 (en) 2020-08-25
EP3232616A1 (en) 2017-10-18
US11496355B2 (en) 2022-11-08
US20170302504A1 (en) 2017-10-19
CN105827419B (zh) 2020-03-10
EP3232616B1 (en) 2019-11-27
US20210006454A1 (en) 2021-01-07

Similar Documents

Publication Publication Date Title
WO2016110248A1 (zh) 一种转发设备故障处理的方法、设备和控制器
US10708132B2 (en) Technique for handling a status change in an interconnect node
US8018844B2 (en) Reliable message transfer over an unreliable network
US9106523B2 (en) Communication device and method of controlling the same
EP3082309A1 (en) Sdn controller, data centre system and router connection method
US9838245B2 (en) Systems and methods for improved fault tolerance in solicited information handling systems
US8934335B2 (en) System and method for enhancing loop free alternative coverage
KR20150007623A (ko) 패킷 전달 시스템에서의 보호 절체 방법 및 장치
US9960993B2 (en) Packet network linear protection systems and methods in a dual home or multi-home configuration
US10033573B2 (en) Protection switching method, network, and system
CN114389972A (zh) 一种丢包检测方法及装置、存储介质
WO2016165061A1 (zh) 一种业务保护方法及装置
JP2010239593A (ja) パケット処理装置およびインタフェースユニット
JP5518771B2 (ja) 冗長ネットワークシステム、終端装置及び中継点隣接装置
WO2021017890A1 (zh) 一种通信方法和通信设备
EP3955531A1 (en) Processing method and apparatus based on link error code
CN109039728B (zh) 基于bfd的流量拥塞检测方法及系统
EP3107242B1 (en) Network diagnosis processing method and device
JP6007138B2 (ja) 伝送システムおよび伝送装置並びに伝送品質検出方法
CN114157557B (zh) 一种点到多点业务传输方法和装置
KR101880222B1 (ko) 오류 복구를 위한 오픈플로우 스위치, 오픈플로우 컨트롤러 및 오류 복구 방법
EP3012993B1 (en) Communication device
WO2023167735A1 (en) System and method for fault recovery in spray based networks
JP2018148265A (ja) 伝送ノード及び回線切替方法
KR20140131480A (ko) 루트화된 다점 연결 네트워크에서 보호절체 방법 및 장치

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: 16734908

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2016734908

Country of ref document: EP