WO2014113957A1 - 一种链路管理方法、设备和通信系统 - Google Patents

一种链路管理方法、设备和通信系统 Download PDF

Info

Publication number
WO2014113957A1
WO2014113957A1 PCT/CN2013/070945 CN2013070945W WO2014113957A1 WO 2014113957 A1 WO2014113957 A1 WO 2014113957A1 CN 2013070945 W CN2013070945 W CN 2013070945W WO 2014113957 A1 WO2014113957 A1 WO 2014113957A1
Authority
WO
WIPO (PCT)
Prior art keywords
switching device
link
switching
state information
flow table
Prior art date
Application number
PCT/CN2013/070945
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 CN201380000151.0A priority Critical patent/CN104081743A/zh
Priority to PCT/CN2013/070945 priority patent/WO2014113957A1/zh
Publication of WO2014113957A1 publication Critical patent/WO2014113957A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0695Management of faults, events, alarms or notifications the faulty arrangement being the maintenance, administration or management system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity

Definitions

  • the present invention relates to the field of communication networks, and in particular, to a link management method, device, and communication system. Background technique
  • the network switching model protocol OpenFlow implements the separation of the control plane and the forwarding plane as an exchange standard in the SDN network.
  • the main components of the SDN network Some include: OpenFlow-enabled switching devices and control devices for managing switching devices.
  • Control devices configure and manage switching devices through the OpenFlow protocol. Switching devices are key nodes in the network, and interfaces developed in existing devices are very limited.
  • the forwarding behavior of the switching device is determined by the control device. For the control device, the control device can only obtain the port information and routing information of the single switching device.
  • the control device sends the feature request information and the statistical request information stats request to the switching device, and receives the feature reply message, the statistical reply message stats reply, and the feedback information fed back by the switching device according to the feature request and the stats request.
  • the routing information is used to obtain the current running state of the switching device.
  • control device can only obtain port information and routing information of each switching device according to the current operating state of the switching device, when the switching device failure occurs, the control device cannot timely The service data transmitted on the failed switching device is sent to other normal switching devices to continue the data communication, thereby causing the communication to be interrupted.
  • Embodiments of the present invention provide a link management method, device, and communication system, which can implement flexible configuration for a service transmission link between switching devices, thereby avoiding communication interruption.
  • a control device including: a processor and a memory connected through a data bus, and at least one connected to the processor and the memory respectively Communication interface, wherein
  • the processor is configured to receive, by using the at least one communication interface, link state information sent by each switching device;
  • the processor is further configured to configure a service data transmission link for each of the switching devices according to the link state information.
  • the processor receives the link state information sent by each switching device by using the at least one communication interface,
  • the processor is further configured to send, by using the at least one communication interface, a link detection request to the respective switching device, so that each of the switching devices performs proximity detection device detection according to the link detection request, and acquires a location of the opposite end.
  • the link state information is generated after the neighboring switching device port information is described.
  • the processor is further configured to start a link update timer that is separately set for each of the switching devices, and when any of the links After the path update timer expires, the link detection request is sent to the switching device corresponding to any link update timer;
  • the processor After the processor receives the link state information sent by the switching devices by using the at least one communication interface,
  • the processor is further configured to reset the link update timer corresponding to each of the switching devices.
  • the processor is further configured to determine, according to the link state information, whether the switching devices are configured according to any one of the foregoing devices. a faulty link exists; if there is a faulty link between the switching devices, the first switching device at one end of the faulty link configures a first flow table according to the link state information, so that the first switching device And sending, according to the first flow table, the received service packet to a third switching device that establishes a normal link with the first switching device; and receiving data of the third switching device by using the at least one communication interface. Forwarding the request, and configuring a second flow table for the third switching device according to the data forwarding request, so that the third switching device forwards the received service data to the fault according to the second flow table.
  • the second flow table is configured to instruct the third switching device to receive the service data that is transmitted by the faulty link between the first switching device and the second switching device And outputting the service data through a port that is connected to the third switching device by the second switching device.
  • the processor is further configured to: if the faulty link between the first switching device and the second switching device returns to normal The control device configures a third flow table for the first switching device, so that the first switching device sends a service packet to the second switching device according to the third flow table.
  • the processor is further configured to send, by using the at least one communication interface, a switching device status information request, where the switching device status information is sent by using the at least one communication interface.
  • a switching device status information request for obtaining port information of the each switching device, and the packet statistics information; and receiving, by the at least one communication interface, switching device status information sent by each switching device; according to the providing by the receiving unit Determining, by the status information of each switching device, whether the switching device is overloaded; if the first switching device of the each switching device is overloaded, the second switching device connected to the first switching device is configured according to The link state information is configured with a fourth flow table, so that the second switching device forwards the service packet sent to the first switching device to the third switching device according to the fourth flow table.
  • the processor is further configured to: if the first switching device is overloaded, the control device is the second exchange The device configures a sixth flow table, and configures a seventh flow table for the first switching device, so that the second switching device forwards the service packet to the first switching device according to the sixth flow table, and The first switching device forwards the service packet to the other switching device according to the seventh flow table.
  • the link status information includes:
  • a switching device including: a processor and a memory connected through a data bus, and at least one communication interface respectively connected to the processor and the memory, wherein
  • the processor is configured to send link state information to the control device by using the at least one communication interface, so that the control device configures a service data transmission link for each of the switching devices according to the link state information;
  • the processor is further configured to forward service data to the switching device according to the service data transmission link configured by the control device by using the at least one communication interface.
  • the processor is further configured to receive, by using the at least one communication interface, a link detection request sent by the control device, and according to the link detection request Performing detection by the neighboring switching device, and generating the link state information after acquiring the neighboring switching device port information of the opposite end.
  • the processor is further configured to start a survival timer; and perform a proximity switch after the survival timer expires And detecting, by acquiring the neighboring switching device port information of the peer end by using the at least one communication interface, generating the link state information and resetting the surviving timer.
  • the processor is further configured to send a probe packet to the neighboring switching device by using each port; Receiving, by the at least one communication interface, the neighboring switching device port information that is sent by the neighboring switching device according to the probe packet; generating the link according to the port information of the switching device and the neighboring switching device port information status information.
  • a link management method including:
  • the control device receives link state information sent by each switching device
  • the control device configures a service data transmission link for each of the switching devices according to the link state information.
  • the method before the control device receives the link state information sent by each switching device, the method further includes:
  • the control device sends a link detection request to the respective switching device, so that the switching devices perform probing by the neighboring switching device according to the link detection request, and obtain the neighboring switching device port information of the opposite end to generate the chain. Road status information.
  • control device starts to set a link update timer for each of the switching devices, and when any of the link update timers expires And sending the link detection request to the switching device corresponding to any of the link update timers;
  • control device After receiving the link state information sent by the switching devices, the control device further includes:
  • the method further includes:
  • the first switching device of the terminal configures the first flow table according to the link state information, so that the first switching device sends the received service packet according to the first flow table to establish a normal chain with the first switching device.
  • the service packet is forwarded to the second switching device at the other end of the faulty link, and the second flow table is configured to instruct the third switching device to receive the first switching device and the second switching device.
  • the service packet transmitted by the faulty link is output, and the service packet is output through a port that is connected to the third switching device by the second switching device.
  • the method further includes:
  • the control device configures a third flow table for the first switching device, so that the first switching device is configured according to The third flow table sends a service message to the second switching device.
  • the method further includes:
  • the control device sends a switching device status information request to the respective switching device, where the switching device status information request is used to obtain port information of the each switching device and the data packet statistical information;
  • the control device receives the switching device status information sent by the switching devices, and determines, according to the status information of each switching device, whether the switching device is overloaded;
  • the third switching device Receiving a data forwarding request of the third switching device, and forwarding according to the data And requesting, by the third switching device, a fifth flow table that is forwarded by the service packet, so that the third switching device forwards the received service packet to another according to the fifth flow table.
  • the switching device, the fifth flow table is configured to instruct the third switching device to receive the service packet sent by the second switching device, and forward the service packet to the other switching device.
  • the method further includes:
  • the control device configures a sixth flow table for the second switching device, and configures a seventh flow table for the first switching device, so that the second Forwarding, by the switching device, the service packet to the first switching device according to the sixth flow table, and forwarding, by the first switching device, the service packet to the other switching device according to the seventh flow table .
  • the link state information includes:
  • the identifier of the switching device at both ends of the link the number of the switching device port, the MAC address of the multiple access channel of the switching device port, and the connection status of the link between the switching devices.
  • the fourth aspect provides a link management method, including:
  • the switching device sends link state information to the control device, so that the control device configures a service data transmission link for the each switching device according to the link state information; and the switching device transmits the service data according to the control device configuration.
  • the link forwards service data.
  • the method before the sending, by the switching device, the link state information to the control device, the method further includes:
  • the switching device receives, by the switching device, the link detection request sent by the control device; the switching device performs proximity detection by the neighboring switching device according to the link detection request, and generates the link state after acquiring the neighboring switching device port information of the opposite end information.
  • the method before the sending, by the switching device, the link state information to the control device, the method further includes: The switching device starts a survival timer;
  • the switching device After the timeout period expires, the switching device performs proximity neighboring device detection, obtains the neighboring switching device port information of the opposite end, generates the link state information, and resets the survival timer.
  • the neighboring switching device detects the neighboring switching device according to the link detection request, and acquires the neighboring switching device at the opposite end.
  • the link state information is generated after the port information, including:
  • the switching device sends a probe message to the neighboring switching device through each port;
  • a control device including:
  • a receiving unit configured to receive link state information sent by each switching device
  • a configuration unit configured to configure a service data transmission link for each switching device according to the link state information provided by the receiving unit.
  • the method before the control device receives the link state information sent by each switching device, the method further includes:
  • a sending unit configured to send a link detection request to each of the switching devices, so that each of the switching devices performs proximity detecting device detection according to the link detection request, and obtains the neighboring switching device port information of the opposite end to generate the Link status information.
  • the sending unit further includes:
  • timing subunit configured to start a link update timer set for each of the switching devices, and send the to the switching device corresponding to any link update timer after any of the link update timers expires Link detection request;
  • control device After the control device receives the link state information sent by the switching devices, Also includes:
  • the timing subunit is further configured to reset the link update timer corresponding to each of the switching devices.
  • control device further includes:
  • a determining unit configured to determine, according to the link state information provided by the receiving unit, whether there is a faulty link between the switching devices;
  • a detecting configuration unit configured to: if a faulty link exists between the switching devices, configure a first flow table according to the link state information, so that the first switching device at one end of the faulty link is configured to perform the first switching Sending, by the device according to the first flow table, the received service packet to a third switching device that establishes a normal link with the first switching device;
  • the receiving unit is further configured to receive a data forwarding request of the third switching device, and configure a second flow table for the third switching device according to the data forwarding request, so that the third switching device is configured according to the The second flow table forwards the received service message to the second switching device at the other end of the faulty link, where the second flow table is used to instruct the third switching device to receive the first switching device And the service packet transmitted by the faulty link between the second switching device, and the service packet is output through a port that is connected to the third switching device by the second switching device.
  • the detecting configuration unit is configured to: if the faulty link between the first switching device and the second switching device returns to normal, The control device configures a third flow table for the first switching device, so that the first switching device sends a service packet to the second switching device according to the third flow table.
  • control device further includes:
  • the sending unit is further configured to send a switching device status information request to the each switching device, where the switching device status information request is used to obtain port information of the each switching device and the data packet statistics information;
  • the receiving unit is further configured to receive switching device status information sent by each switching device;
  • a detecting unit configured to determine, according to status information of each of the switching devices that is provided by the receiving unit, whether the switching device is overloaded;
  • Configuring a query unit configured to: if a first switching device of the switching device is overloaded, configure a fourth flow table according to the link state information, so that the second switching device connected to the first switching device is configured, so that The second switching device forwards the service packet sent to the first switching device to the third switching device according to the fourth flow table, and the receiving unit is further configured to receive data of the third switching device. Forwarding the request, and configuring, according to the data forwarding request, a fifth flow table corresponding to the service packet forwarding, for the third switching device, so that the third switching device receives the received according to the fifth flow table.
  • the service packet is forwarded to the other switching device, and the fifth flow table is configured to instruct the third switching device to receive the service packet sent by the second switching device, and forward the service packet to the Said other switching devices.
  • the configuration query unit is further configured to: if the first switching device is overloaded, the control device is the The second switching device configures a sixth flow table, and configures a seventh flow table for the first switching device, so that the second switching device forwards the service packet to the first switching device according to the sixth flow table, And forwarding, by the first switching device, the service packet to the other switching device according to the seventh flow table.
  • the link status information includes:
  • the identifier of the switching device at both ends of the link the number of the switching device port, the MAC address of the multiple access channel of the switching device port, and the connection status of the link between the switching devices.
  • a switching device including:
  • a sending unit configured to send link state information to the control device, so that the control device configures a service data transmission link for the each switching device according to the link state information
  • a forwarding unit configured to forward the service data according to the service data transmission link configured by the control device.
  • the switching device further includes:
  • a receiving unit configured to receive a link detection request sent by the control device, and a detecting unit, configured to perform proximity detection device detection according to the link detection request, and generate a location after acquiring the neighboring switching device port information of the opposite end Link status information.
  • the switching device further includes:
  • a startup unit configured to start a survival timer
  • an obtaining unit configured to perform neighboring switching device detection after the timeout period expires, obtain the neighboring switching device port information of the opposite end, generate the link state information, and reset the surviving timer.
  • the acquiring unit includes:
  • a detecting subunit configured to send a probe message to the neighboring switching device by using each port
  • a receiving subunit configured to receive the neighboring switching device port information that is sent by the neighboring switching device according to the probe packet
  • a communication system including: a control device and at least two switching devices, where
  • control device is any one of the control devices of the first aspect, and the switching device is any one of the switching devices of the second aspect;
  • control device is any one of the control devices described in the fifth aspect, or the switching device is any one of the switching devices described in the sixth aspect.
  • the link management method, the device, and the communication system provided by the embodiment of the present invention the control device obtains link state information between the switching devices through link detection, and can implement flexible configuration for the service transmission link between the switching devices, thereby avoiding A communication interruption occurred.
  • FIG. 1 is a schematic flowchart of a link management method according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of another link management method according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of another embodiment of the present invention. Schematic diagram of the road management method
  • FIG. 4 is a schematic flow chart of another link management method according to another embodiment of the present invention.
  • FIG. 5 is a schematic flow chart of still another link management method according to another embodiment of the present invention.
  • FIG. 6 is a schematic flowchart diagram of a link management method according to another embodiment of the present invention.
  • FIG. 7 is a schematic flow chart of another link management method according to another embodiment of the present invention.
  • FIG. 8 is a schematic flow chart of a link management method according to still another embodiment of the present invention.
  • FIG. 9 is a schematic flow chart of another link management method according to still another embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a control device according to an embodiment of the present invention
  • FIG. 11 is a schematic structural diagram of another control device according to an embodiment of the present invention
  • FIG. 12 is still another control device according to an embodiment of the present invention
  • FIG. 13 is a schematic structural diagram of still another control device according to an embodiment of the present invention
  • FIG. 14 is a schematic structural diagram of a switching device according to an embodiment of the present disclosure
  • FIG. 16 is a schematic structural diagram of still another switching device according to an embodiment of the present invention
  • FIG. 17 is a schematic structural diagram of another switching device according to an embodiment of the present invention
  • FIG. 19 is a schematic structural diagram of a switching device according to another embodiment of the present invention.
  • FIG. 20 is a schematic structural diagram of a communication system according to the present invention. detailed description
  • the OpenFlow protocol transforms the traditional physical fixed hardware into a dynamically variable Software Defined Network (SDN), which realizes the separation of the control plane and the forwarding plane.
  • SDN Software Defined Network
  • the main components of the network include: a control device and at least one switching device supporting the OpenFlow protocol, wherein the control device configures and manages the switching device according to the OpenFlow protocol.
  • the switching device may be an electronic device for forwarding data such as a switch, a router, a hub, etc.; the control device may be a control board supporting the OpenFlow protocol.
  • the components of the switching device supporting the OpenFlow protocol include: a flow table, a secure channel, and an OpenFlow protocol, and the switching device is connected to the control device through a secure channel, and the control device passes the switching device.
  • the flow table query manages the switching device.
  • the embodiment of the invention provides a link management method, which is shown in FIG.
  • the process is as follows:
  • the control device receives link state information sent by each switching device.
  • control device obtains link state information between the switching devices by receiving a link detection reply link detection reply message sent by each switching device.
  • the link state information obtained by the neighboring device is obtained by the neighboring device, and then the link state information is encapsulated into a link detection reply by the switching device to be sent to the control device.
  • the control device configures a service data transmission link for each switching device according to the link state information.
  • the control device learns the current running status of each switching device and the link status between the switching devices according to the link state information, so that when the link between the switching devices fails or a switching device is overloaded, the control device can
  • the link state information configures a service data transmission link for each switching device.
  • the service data on the service data transmission link may be not only the upper-level switching device in the service data transmission link. Obtained at the port, but also from the client connected to the switching device.
  • the link state information includes: an identifier of the switching device at both ends of the link, a port number, a MAC address of the multiple access channel of the port, and a connection state of the link between the switching devices.
  • the method before the control device receives the link state information sent by each switching device, the method further includes:
  • the control device sends a link detection request to each switching device, so that each switching device performs probing by the neighboring switching device according to the link detection request, and obtains link state information of the neighboring switching device port information of the peer end.
  • the control device obtains link state information between the switching devices through link detection, and can implement flexible configuration for the service transmission link between the switching devices, thereby avoiding communication interruption.
  • the embodiment of the invention provides a link management method, which is shown in FIG.
  • the process is as follows:
  • the switching device sends link state information to the control device, so that the control device configures a service data transmission link for each switching device according to the link state information.
  • the switching device obtains the link state information on the switching device at the opposite end of the link connected to the switching device according to the triggering neighbor discovery function, where the link state information is the identifier of the switching device at both ends of the link, the port number, and the port number. Address access channel MAC address and connection status on the connected link.
  • the switching device that initiates the neighbor discovery function encapsulates the link state information into the link detection reply message, and sends the link detection reply message to the control device, so that the control device detects the reply message according to the link.
  • the link state information configures a service data transmission link for each switching device.
  • the switching device forwards the service data according to the service data transmission link configured by the control device.
  • the control device obtains link state information between the switching devices through link detection, and can implement flexible configuration for the service transmission link between the switching devices, thereby avoiding communication interruption.
  • an embodiment of the present invention provides a link management method, which provides a control device that is sent by a receiving switching device.
  • the link state information is used to update the link state information of each switching device, which mainly includes: a link update process initiated by the control device and a link update process initiated by the switching device; wherein, as shown in FIG. 3, the control device initiates The link update process, the specific steps are as follows:
  • the control device starts to set a link update timer for each switching device, and sends a link detection request to the switching device corresponding to any link update timer after any link update timer expires.
  • the control device sets a link update timer for each switch device. When any link update timer expires, a link update process is initiated. At this time, the control device sends a link to the switch device corresponding to the link update timer. The request message is detected, so that the switching device feeds back the current link update status according to the link detection request message. 302a. The switching device performs the detection of the neighboring switching device by receiving the link detection request sent by the control device, and obtains the link state information of the neighboring switching device port information of the peer end.
  • the switching device triggers the detection of the neighboring switching device according to the received link detection request.
  • the switching device performs the detection of the neighboring switching device according to the link detection request, and obtains the link state information of the neighboring switching device port information, which includes: a.
  • the switching device sends the probe packet to the neighboring switching device through each port. .
  • the switching device triggers the detection process of the neighboring switching device according to the link detection request packet sent by the control device, and sends the probe packet to the neighboring switching device, so as to obtain the link state information of the peer switching device.
  • the switching device receives the neighboring switching device port information that the neighboring switching device responds according to the probe message.
  • the switching device receives the neighboring switching device port information sent by the neighboring switching device, including: an identifier of the neighboring switching device, a port number of the neighboring switching device, and a multiple access channel MAC address of the port of the neighboring switching device.
  • the switching device generates link state information by using the port information of the neighboring switching device and the identity of the switching device, the port number, and the multiple access channel MAC address of the port in the foregoing step, where the link state information further includes the switching device and the neighboring device.
  • the link connection status of the switching device is not limited to the switching device.
  • the switching device sends link state information to the control device, so that the control device configures a service data transmission link for each switching device according to the link state information.
  • the switching device obtains the link state information on the switching device at the opposite end of the link connected to the switching device according to the triggering neighbor discovery function, where the link state information is the identifier of the switching device at both ends of the link, the port number, and the port number. Address access channel MAC address and connection status on the connected link.
  • the switching device that initiates the neighbor discovery function encapsulates the link state information into the link detection reply message, and the link is The detection reply message is sent to the control device, so that the control device configures the service data transmission link for each switching device according to the link state information in the link detection reply message.
  • the control device receives link state information sent by each switching device, and resets a link update timer corresponding to each switching device.
  • the link state information received by the control device is received in the form of a link detection reply message, and the control device delivers the link detection reply message to the link management entity LME (Link Management Entity) in the control device.
  • LME Link Management Entity
  • the LME extracts the link state information from the link detection reply message, and stores the link state information in the Link Management Data Base (LMDB) to record the updated information.
  • LMDB Link Management Data Base
  • the link management method provided by the embodiment of the present invention, when the link update timer of the control device times out, triggers the detection of the neighboring switch device by sending the link detection request to the switch device, and acquires the probe according to the proximity switch device.
  • the link state information of the switching device and the neighboring switching device so that when a link failure occurs between the switching devices, the control device can process the link failure according to the link state information obtained by the link detection, thereby preventing the communication interruption from occurring.
  • the link update process initiated by the switching device is as follows:
  • the switching device starts the survival timer.
  • the link update process initiated by the switching device initiates a surviving timer, which is used to trigger the detecting process of the switching device to the neighboring switching device.
  • the switching device After the timeout period expires, the switching device performs probing by the neighboring switching device, obtains the neighboring switching device port information of the peer end, generates link state information, and resets the egress timer.
  • the updated link status information in the link update process initiated by the switching device includes: an identifier of the switching device at both ends of the link, a number of the switching device port at both ends of the link, and a multiple access channel MAC of the port.
  • the specific detection process is as described in step 303 a in the embodiment shown in FIG. 3 , and details are not described herein again.
  • the switching device sends link state information to the control device, so that the control device configures a service data transmission link for each switching device according to the link state information.
  • the switching device sends the link state information to the link detection packet of the OpenFlow protocol, and sends the link detection reply packet to the control device, where the switching device sends the link detection reply message.
  • the switching device After controlling the device, the switching device resets its own survival timer so that the switching device prepares to proceed to the next cycle to start the link update according to the survival timer.
  • the link management method provided by the embodiment of the present invention, when the survival timer of the switching device expires, triggers the detection of the neighboring switching device, and acquires the state information of the neighboring switching device according to the detecting neighboring switching device, and generates according to the state information.
  • the link state information sends the link state information to the control device, so that when a link failure between the switching devices occurs, the control device can timely process the link failure according to the link state information obtained by the link detection, thereby avoiding communication An interrupt occurs.
  • the method for link update further includes: setting a link update timer corresponding to each switching device on the control device end, and setting a survival timing corresponding to the control device end on the switch device end
  • the link update timer of the control device is synchronized with the surviving timer of the switching device.
  • the control device sends a link detection request to the switching device, so that the switching device detects the request according to the link.
  • the switching device triggers the detection of the neighboring switching device due to the timeout of the survival timer, and sends the link state information obtained by the detection to the control device, and resets the survival timer, so that the control device or the switching device is controlled. Can avoid one more time in a short time Since the timer at either end is not reset, the link update is initiated again after the timing expires, thereby avoiding waste of network resources;
  • the timer may have different timing periods due to different settings, but the link update timer of the control device and the survival timer of the switching device are both after the link update initiated by the control device or the link update initiated by the switching device ends. All resets are required, so that the survival timer of the switching device is not reset after the link update initiated by the control device ends, and then the switching device actively performs the link again after the survival timer of the switching device expires.
  • the update is to avoid the burden on the network resource caused by the control device receiving the link state information sent by the switching device to the link management database LMDE of the control device.
  • an embodiment of the present invention provides a link management method, which provides a control device according to a link.
  • a specific solution is required when the status information is faulty on the switching device.
  • the specific processes include:
  • the control device sends a link detection request to each switching device.
  • the control device may trigger the detection of the neighboring switching device between the switching devices by sending a link detection request, and learn the current link state information between the switching devices by using the link state information fed back by the switching device. Therefore, when the link between the switching devices fails or the switching device is overloaded, the control device can obtain the link state between the currently controlled switching devices according to the link state information, and perform link configuration in time to avoid communication interruption on the transmission path.
  • the link update process described in the embodiment shown in FIG. 3 may be further included, that is, before the step 401, the control device side further includes triggering the link update according to the control device end link update timer timing timeout. .
  • the switching device performs proximity node switching device detection, and obtains link state information of the neighboring switching device port information of the peer end.
  • the switching device may trigger detection of the neighboring switching device according to the link detection request sent by the control device, and may also be based on The switch device lifetime timer expires to trigger the detection of the neighboring switching device (only when the switching device triggers the detection of the neighboring switching device according to the switching device lifetime surviving timer timeout, not included in the process of a link state update) Step 401).
  • the link state information is generated after the neighboring switching device port information is obtained by detecting the neighboring switching device.
  • the method for triggering the detecting of the neighboring switching device is that the control device sends a link detection request trigger and the switching device lifetime timer expires.
  • the link update process described in the embodiment shown in FIG. 4 is further included, that is, before the step 402, the switching device side is further exchanged.
  • the timeout of the device-side survival timer triggers a link update.
  • the switching device performs the detection of the neighboring switching device in step 402 not only by detecting the link detection request sent by the control device end due to the link update timer timeout, but also triggering detection on the neighboring switching device. Probing to neighboring switching devices may be triggered based on a timeout of the switching device side survival timer.
  • the switching device sends link state information to the control device, so that the control device configures a service data transmission link for each switching device according to the link state information.
  • the control device receives the chain sent by the switching device.
  • the link state information is stored in the link management database LMDB through the link management entity LME in the control device, and the link update timer is reset, and the link update initiated by the device is controlled.
  • the process ends; or, after step 403, referring to the embodiment shown in FIG. 4, after the switching device sends the link state information, the switching device resets its own survival timer, and the switching device initiated link update process ends.
  • the control device determines, according to the link state information, whether a faulty link exists between the switching devices.
  • the link management entity LME in the control device discovers whether there is a faulty link between the switching devices by using link state information stored in the link management database LMDB, so as to control the device to perform traffic on the failed link. Adjustment.
  • the first switching device configures the first flow table according to the link state information, so that the first switching device sends the received service packet according to the first flow table to the third switching device that establishes a normal link with the first switching device.
  • the control device finds that there is a faulty link between the switching devices according to the connection state of the switching devices in the link state information, and configures a first flow table for the first switching device at both ends of the faulty link, where the control device performs the first switching.
  • the first flow table configured by the device is configured to send the service packet to the third switching device according to the first flow table reconfigured to the first switching device, where the service packet is sent to the third switching device, where the control device is configured.
  • the link between the first switching device and the third switching device is normal through the link state information between the first switching device and the third switching device, and the forwarding of the service packet is completed.
  • the link state information includes: an identifier of the switching device at both ends of the link, a number of the switching device port, a multiple access channel MAC address of the switching device port, and a connection state of the link between the switching devices.
  • the first switching device forwards the service packet scheduled to be sent to the second switching device to the first packet according to the first flow table configured by the control device.
  • the three switching device (the service message in which the first switching device is scheduled to be sent to the second switching device is shown by a broken line in the figure).
  • the control device receives the data forwarding request of the third switching device, and configures the second flow table for the third switching device according to the data forwarding request, so that the third switching device forwards the received service packet to the fault according to the second flow table.
  • the second switching device at the other end of the link.
  • the second flow table is configured to instruct the third switching device to receive the service packet transmitted by the faulty link between the first switching device and the second switching device, and connect the service packet to the third switching device by using the second switching device. Port output.
  • the third switching device cannot find a matching item after receiving the service packet from the first switching device, that is, the third switching device cannot find the peer switching device that receives the third switching device to forward the service packet.
  • the third switching device sends a data forwarding request to the control device, and the control device receives the data forwarding request of the third switching device.
  • the third switching device configures the second flow table, so that the third switching device forwards the received service packet to the next-level device connected to the second switching device at the other end of the faulty link according to the second flow table, where the next
  • the level device may be a client connected to the second switching device, or may be another switching device connected to the second switching device and responsible for forwarding service data.
  • the control device configures a third flow table for the first switching device, so that the first switching device sends the service packet to the third flow table according to the third flow table. Second switching device.
  • the control device discovers the faulty link between the first switching device and the second switching device by using a periodic link update, and the control device re-establishes the current connection state of the first switching device and the second switching device according to the link state information. And configuring, by the first switching device, a flow table, that is, a third flow table, so that the first switching device sends the service packet sent to the third switching device to the second switching device according to the indication of the third flow table, that is, the first switching device is restored.
  • the service data transmission link between the second switching device and the second switching device is no longer forwarded by the third switching device to the second switching device.
  • the control device obtains link state information between the switching devices through link detection, so that when the link failure between the switching devices occurs, the control device can detect the obtained link according to the link detection.
  • Status information handles link failures in a timely manner, thereby avoiding communication interruptions.
  • a network architecture is formed in an OpenFlow protocol control device, a switching device, and a client.
  • the client may be an access device used by a user, such as a personal computer (PC) or a mobile phone.
  • a tablet computer can also refer to a higher-level device connected to a switching device in a transmission network; a specific control device is connected to three switching devices, wherein the switching device 1 is connected to the client 1, and the switching device 2 is connected to the client 2, and the switching device 1 There is a link relationship between the switching device 2 and the switching device 3, that is, the switching device 1 is connected to the switching device 2, the switching device 2 is connected to the switching device 3, and the switching device 1 is connected to the switching device 3, and if the switching device 3 is connected,
  • the control device can obtain link state information between the switching devices, thereby implementing the switching.
  • the link status between the devices is updated, and the specific processing methods of steps 404 to 406 after the link failure occurs
  • the control device obtains link state information between the switching devices, and finds that the link state between the switching device 1 and the switching device 2 is abnormal according to the link state information.
  • the abnormality of the link state between the switching device 1 and the switching device 2 can be expressed as follows: When the switching device 1 performs the service communication with the switching device 2, the timer corresponding to the receiving and receiving packets in the switching device 1 or the switching device 2 is received. Timeout, such that when the control device initiates a link update, or when the switching device 1 or the switching device 2 initiates a link update, the information that the link between the switching device 1 and the switching device 2 fails is sent to the control device for control. The device learns that the link between the switching device 1 and the switching device 2 is faulty according to the link state information, and reconfigures the transmission path for the service packet transmitted on the link between the switching device 1 and the switching device 2.
  • the control device sends a flow table modification message flow-mod message to the switching device 1 to modify the flow table of the switching device 1 so as to send the scheduled transmission on the switching device 1.
  • the service message from the client 1 to the switching device 2 is forwarded to the switching device 3.
  • the flow-mod message sent by the control device to the switching device 1 is used to modify the flow table of the switching device 1.
  • the switching device 3 receives the service packet sent by the switching device 1, and the switching device 3 requests the corresponding switching device 3 from the control device through the packet-in message because there is no switching device at the opposite end of the link receiving the service packet of the switching device 3.
  • the flow table after receiving the request sent by the switching device 3, the control device sends a flow-mod message to configure the flow table for the switching device 3, so that the switching device 3 configures the flow table of the corresponding switching device 3 according to the flow-mod message.
  • the service packet sent by the switching device 1 is sent to the client 2 via the switching device 2 through the port connected to the switching device 2 by the switching device 3.
  • the control device re-adjusts the peer-to-peer switching device for the switching device 1, so that the switching device 1 receives the service packet and forwards it via the switching device 3, and then the switching device 3 forwards the service.
  • the service message is forwarded to the switching device 2, and the service packet is sent by the switching device 2 to the client 2, so that the normal service transmission is continued between the client 1 and the client 2; wherein, the control device periodically performs the chain
  • the road update process is to detect whether the link status between the switching devices is normal.
  • the link management database LMDB in the control device is updated by obtaining the link state information in steps 401 to 403.
  • the control device restores the service between the client 1 and the client 2 to the original link by modifying the flow table on the switching device 1, the switching device 2, and the switching device 3, that is, between the switching device 1 and the switching device 2
  • the link while deleting the flow table of the switching device 3, avoids the transmission of the service packet between the client 1 and the client 2 between the switching device 1 and the switching device 2, and the switching device 1 once again connects the client
  • the service packet of the terminal 1 is forwarded by the switching device 3 to the switching device 2 and forwarded by the switching device 2 to the client 2.
  • the control device sends the link state information sent by each switching device.
  • the control device flexibly configures the service transmission link according to the link state information in time. The interruption of communication between the clients occurred.
  • the embodiment of the present invention provides a link management method, which provides a control device according to a link.
  • the specific process includes: 501.
  • the control device sends a link detection request to each switching device.
  • the control device may trigger the detection of the neighboring switching device between the switching devices by sending a link detection request, and learn the current link state information between the switching devices by using the link state information fed back by the switching device.
  • the control device can obtain the link state between the currently controlled switching devices according to the link state information, and perform link configuration in time to avoid communication between the clients.
  • the interruption may include the link update process described in the embodiment shown in FIG. 3 before the step 501, that is, before the step 501, the control device side further includes a timer timeout trigger chain according to the control device link update timer. Road update.
  • the switching device performs proximity node switching device detection, and obtains link state information of the neighboring switching device port information of the peer end.
  • the switching device may trigger the detection of the neighboring switching device according to the link detection request sent by the control device, and may also trigger the detection of the neighboring switching device according to the switching device lifetime surviving timer timeout.
  • step 501 is not included in the process of one link state update.
  • the link state information is generated after the neighboring switching device port information is obtained by detecting the neighboring switching device.
  • the method for triggering the detecting of the neighboring switching device is that the control device sends a link detection request trigger and the switching device lifetime timer expires.
  • the link update process described in the embodiment shown in FIG. 4 is further included, that is, before the step 502, the switching device side is also included.
  • the timeout of the device-side survival timer triggers a link update. Different from the embodiment shown in FIG. 3, in which the switching device performs the detection of the neighboring switching device in step 502, not only by detecting the link detection request sent by the control device end due to the link update timer timeout, but also triggering detection on the neighboring switching device. Probing to neighboring switching devices may be triggered based on a timeout of the switching device side survival timer.
  • the switching device sends link state information to the control device, so that the control device configures a service data transmission link for each switching device according to the link state information.
  • the control device receives the chain sent by the switching device.
  • the link state information is stored in the link management database LMDB through the link management entity LME in the control device, and the link update timer is reset, and the link update initiated by the device is controlled.
  • the process ends; or, after step 503, referring to the embodiment shown in FIG. 4, after the switching device sends the link state information, the switching device resets its own survival timer, and the link update process initiated by the switching device ends.
  • the control device sends a switching device status information request to each switching device.
  • the switching device status information request is used to obtain port information and packet statistics information of each switching device.
  • the specific control device periodically initiates a switching device status information request to each switching device, so as to obtain the real-time switching device status information of each switching device in time, wherein the switching device status information request of the controlling device sends a feature request to the feature request. And the statistical request stats request is sent to each switching device in two forms.
  • the control device receives the switching device status information sent by each switching device, and determines, according to the status information of each switching device, whether the switching device is overloaded.
  • the control device determines, according to the switching device status information, whether the switching device is overloaded in each switching device, where the switching device status information includes: a CPU load value of the switching device and a maximum bandwidth of the forwarding rate of the switching device port.
  • control device obtains the flow table, the data flow feature, or the characteristics of each switching device port of each switching device by receiving a feature reply signature message sent by each switching device, and obtains each switching device by receiving a statistical response stats reply message. Receiving statistics of the data packet, so that the control device learns the current state of each switching device according to the switching device status information;
  • the control device can determine that the switching device is overloaded according to the feature that the packet loss rate on the port of the switching device is too high.
  • the link management entity LME in the control device obtains the link configuration attribute of the first switching device by querying the link management database LMDB, so as to find whether another service transmission path exists between the clients.
  • control device is a second switching device connected to the first switching device according to
  • the link state information is configured to correspond to a fourth flow table of the second switching device, and the second switching device forwards the service packet sent to the first switching device to the third switching device according to the fourth flow table.
  • the second switching device forwards the service packet sent to the first switching device to the third switching device according to the third flow table configured by the control device, where the second switching device is overloaded.
  • the service message scheduled to be sent to the first switching device is shown in dashed lines in the figure).
  • the control device receives the data forwarding request of the third switching device, and configures, by the third forwarding device, the fifth flow table that is forwarded by the third switching device according to the data forwarding request, so that the third switching device receives the received according to the fifth flow table. Service packets are forwarded to other switching devices.
  • the fifth flow table is configured to instruct the third switching device to receive a service packet that is sent by the second switching device to the first switching device, and forward the service packet to another switching device. .
  • the control device configures a sixth flow table for the second switching device, and configures a seventh flow table for the first switching device, so that the second switching device according to the sixth flow table
  • the service packet is forwarded to the first switching device, and the first switching device forwards the service packet to the other switching device according to the seventh flow table.
  • a network architecture is formed in an OpenFlow protocol control device, a switching device, and a client.
  • the client may be an access device used by a user, such as a personal computer (PC) or a mobile phone.
  • a tablet computer can also refer to a higher-level device connected to a switching device in a transmission network.
  • a specific control device is connected to four switching devices, wherein the switching device 2 is connected to the client 1, and the switching device 4 is connected to the client 2, and the switching device is connected.
  • the switching device 4, the switching device 1 is connected to the switching device 4, the switching device 1, the switching device 2 and the switching device 3 have a link relationship, that is, the switching device 1 is connected to the switching device 2, and the switching device 2 is connected to the switching device 3, At the same time, the switching device 1 is connected to the switching device 3 and connected to the switching device 4 respectively.
  • the control device can obtain the link state information between the switching devices according to the method described in the foregoing embodiment, and further The link state update between the switching devices is implemented, and the specific processing methods of steps 504 to 506 after the switching device is overloaded are:
  • the control device confirms the existence of the link between the switching devices according to the link state information sent by each switching device, and then sends a status message to each switching device, requests a feature request message, and receives a status message sent by each switching device.
  • the reply packet is used to collect the current status of each switching device by using the status information of each switching device, so as to determine whether there is an overloaded switching device in each switching device.
  • the overload of the switching device can be represented as a high packet loss rate. If the control device finds that the packet loss rate of the switching device 1 is high, the LME of the control device queries the LMDB to obtain the configuration attribute of the link where the switching device 1 is located. There is another service transmission channel between Client 1 and Client 2.
  • the control device configures the flow table corresponding to the switching device 2 for the switching device 2 connected to the switching device 1, so that the switching packet 2 forwards the service packet of the client 1 to the switching device 1 by the switching device 1 Device 2 forwards to switching device 3.
  • the switching device 3 receives the service packet sent by the switching device 2, and if the matching flow table is not matched, the packet is requested by the packet-in message to the control device, and the control device receives the data of the switching device 3. After the forwarding request is sent, the data stream is repaired, and the flow-mod message is configured to configure the corresponding flow table for the switching device 3, so that the switching device 3 can forward the service packet to the port connected to the switching device 4, and forwarded by the switching device 4 to the client. 2.
  • control device re-adjusts the peer-to-peer switching device for the switching device 2, so that the switching device 2 receives the service packet sent by the client 1 and forwards the service packet to the switching device 4, and then the switching device 3 forwards the service packet to the switching device 4, and finally The service packet is sent by the switching device 4 to the client 2; wherein, the control device periodically performs a link update process to detect whether the link state between the switching devices is normal.
  • the transmission path between the client 1 and the client 2 is switched to the transmission path where the original switching device 1 is located; the specific process is: The device sends a flow-mod packet to the switching device 2, modifies the flow table of the switching device 2, and forwards the service packet from the client 1 to the
  • the switching device 1 configures a flow table corresponding to the switching device 1 for the switching device 1 so that the switching device 1 forwards the received service packet to the switching device 4 and forwards it to the client 2 by the switching device 4.
  • the control device sends the link state information sent by each switching device.
  • the control device flexibly configures the service transmission link according to the link state information, thereby avoiding the client.
  • the embodiment of the present invention provides a control device.
  • the control device may be an electronic device in the software-definable SDN network that performs the OpenFlow protocol and is responsible for configuring data transmission between the switching devices.
  • the specific form of the control device in the embodiment of the present invention is provided.
  • the control device includes: a receiving unit 61 and a configuration unit 62, wherein the control device is configured to be implemented according to any one of the above-mentioned link management methods provided by the embodiments of the present invention.
  • the receiving unit 61 is configured to receive link state information sent by each switching device.
  • the configuration unit 62 is configured to configure a service data transmission link for each switching device according to the link state information provided by the receiving unit.
  • the control device obtains link state information between the switching devices through link detection, so that when the link fault between the switching devices occurs, the control device can obtain the link state information obtained according to the link detection. Handle link failures in time to avoid communication interruptions.
  • control device 6 as shown in FIG. 10, further includes: a sending unit 63, where
  • the sending unit 63 is configured to send a link detection request to each switching device, so that each switching device performs probing by the neighboring switching device according to the link detection request, and obtains link state information of the neighboring switching device port information of the peer end.
  • the sending unit 63 includes: a timing subunit 63 1 , where
  • the timing sub-unit 63 1 is used to start the link set for each switching device. a new timer, and sending, after any one of the link update timers expires, the link detection request to a switching device corresponding to any link update timer;
  • control device After receiving the link state information sent by the switching devices, the control device further includes:
  • the timing subunit 63 1 is further configured to reset the link update timer corresponding to each of the switching devices.
  • control device 6 as shown in FIG. 12, further includes: a determining unit 64, a detecting and configuring unit 65, where
  • the determining unit 64 is configured to determine, according to the link state information provided by the receiving unit, whether there is a faulty link between the switching devices;
  • the detecting configuration unit 65 is configured to configure a first flow table for the first switching device at both ends of the faulty link, if the faulty link exists between the switching devices, so that the first switching device receives the received service packet according to the first flow table. Sending to a third switching device that establishes a normal link with the first switching device;
  • the receiving unit 61 is further configured to receive a data forwarding request of the third switching device, and configure a second flow table corresponding to the service packet forwarding by the third switching device according to the data forwarding request, so that the third switching device according to the second flow table The received service packet is forwarded to the other switching device, and the second flow table is used to instruct the third switching device to receive the service packet sent by the second switching device, and forward the service packet to the other switching device.
  • the detecting configuration unit 65 is further configured to: if the faulty link between the first switching device and the second switching device returns to normal, the control device configures a third flow table for the first switching device, so that the first switching device is configured according to the first switching device.
  • the third flow table sends the service packet to the second switching device.
  • the control device provided by the present invention controls the link state information sent by the switching device.
  • the control device flexibly configures the service transmission link according to the link state information, thereby avoiding the client. Interruption of communication occurs.
  • control device 6, as shown in FIG. 13, further includes: a detecting unit 66 and a configuration query unit 67, where The sending unit 63 is further configured to send, to each switching device, a switching device status information request, where the switching device status information request is used to obtain port information and data packet statistical information of each switching device;
  • the receiving unit 61 is further configured to receive switching device status information sent by each switching device.
  • the detecting unit 66 is configured to determine, according to status information of each switching device provided by the receiving unit, whether the switching device is overloaded in each switching device;
  • the configuration query unit 67 is further configured to: if the first switching device in each switching device is overloaded, configure a fourth flow table according to the link state information by the second switching device connected to the first switching device, so that the second switching device is configured according to the second switching device.
  • the fourth flow table forwards the service packet sent to the first switching device to the third switching device;
  • the receiving unit 61 is further configured to receive a data forwarding request of the third switching device, and configure a third flow table corresponding to the service packet forwarding by the third switching device according to the data forwarding request, so that the third switching device according to the fifth flow table
  • the received service packet is forwarded to the other switching device
  • the fifth flow table is configured to instruct the third switching device to receive the service packet sent by the second switching device, and forward the service packet to the other switching device.
  • the configuration query unit 67 is further configured to: if the first switching device is overloaded, the control device configures a sixth flow table for the second switching device, and is configured as the first switch The device configures a seventh flow table, so that the second switching device forwards the service packet to the first switching device according to the sixth flow table, and the first switching device according to the seventh flow table The service message is forwarded to the other switching device.
  • the link status information includes:
  • the identifier of the switching device at both ends of the link the number of the switching device port, the MAC address of the switching device port, and the connection status of the link between the switching devices.
  • the control device controls the link state information sent by the device through the switching device.
  • the control device flexibly configures the service transmission link according to the link state information, thereby avoiding the relationship between the clients.
  • the embodiment of the present invention provides a switching device 7, which may be an electronic device that performs OpenFlow protocol and is responsible for forwarding data transmission in a software-definable SDN network, and may be an electronic device responsible for forwarding data, such as a switch, a router, a hub, and the like.
  • the specific configuration of the switching device is not specifically limited, and any of the foregoing link management methods provided by the embodiments of the present invention may be implemented. Referring to FIG. 14, the method includes: a sending unit 71 and a forwarding unit. 72 , where
  • the sending unit 71 is configured to send link state information to the control device, so that the control device configures a service data transmission link for the each switching device according to the link state information.
  • the forwarding unit 72 is configured to forward the service data according to the service data transmission link configured by the control device.
  • the control device obtains link state information between the switching devices through link detection, so that when the link fault between the switching devices occurs, the control device can detect the link state information obtained according to the link detection. Handle link failures in time to avoid communication interruptions.
  • the switching device 7 includes: a receiving unit 73 and a detecting unit 74, where
  • the receiving unit 73 is configured to receive a link detection request sent by the control device, and the detecting unit 74 is configured to perform detection by the neighboring switching device according to the link detection request, and generate link state information after acquiring the neighboring switching device port information of the opposite end.
  • the switching device 7 further includes: a starting unit 75 and an obtaining unit 76, where
  • a starting unit 75 configured to start a survival timer
  • the obtaining unit 76 is configured to perform neighboring switching device detection after the survival timer expires, obtain link state information of the neighboring switching device, and generate link state information and reset the survival timer.
  • the obtaining unit 76 includes: a detecting subunit 761, a receiving subunit 762, and a generating subunit 763, where
  • a detecting subunit 761 configured to send a probe to a neighboring switching device through each port Message
  • the receiving subunit 762 is configured to receive, by the neighboring switching device, the neighboring switching device port information according to the probe message response;
  • the generating subunit 763 is configured to generate link state information according to the port information of the changing device and the neighboring switching device port information.
  • the control device obtains link state information between the switching devices through link detection, so that when the link fault between the switching devices occurs, the control device can detect the link state information obtained according to the link detection. Handle link failures in time to avoid communication interruptions.
  • the embodiment of the present invention provides a control device 8 , which may be an electronic device that performs an OpenFlow protocol in an SDN network and is responsible for configuring data transmission between the switching devices.
  • the specific form of the control device is not specifically The limitation, which is any one of the foregoing link management methods that can be implemented by the embodiments of the present invention, as shown in FIG.
  • processor 81 includes: at least one processor 81, a memory 82, a communication port 83, and a bus 84, the at least one processing
  • the processor 81, the memory 82, and the communication interface 83 are connected by a bus 84 and complete communication with each other.
  • the bus 84 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus 84 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 18, but it does not mean that there is only one bus or one type of bus.
  • the memory 82 is for storing executable program code, the program code including computer operation instructions.
  • the memory 82 may include a high speed RAM memory and may also include a non-volatile memory, for example: at least one disk saver.
  • the storage device stores: an operating system, an application, and a program code for implementing the embodiment of the present invention.
  • the operating system is for controlling and implementing processing functions performed by the processing unit.
  • the application contains program code, such as word processing software, email software.
  • the processor 81 may be a central processing unit (CPU) or an application specific integrated circuit (Application Specific Integrated Circuit). An ASIC) or one or more integrated circuits configured to implement embodiments of the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the communication interface 83 is mainly used to implement communication between devices in the embodiment.
  • the processor 81 is configured to receive, by using at least one communication interface, link state information sent by each switching device.
  • the processor 8 1 is further configured to configure a service data transmission link for each switching device according to the link state information.
  • the control device obtains link state information between the switching devices through link detection, so that when the link fault between the switching devices occurs, the control device can obtain the link state information obtained according to the link detection. Handle link failures in time to avoid communication interruptions.
  • the processor 81 receives the link state information sent by each switching device by using at least one communication interface
  • the processor 8 1 is further configured to send a link detection request to each switching device by using at least one communication interface, so that each switching device performs proximity detecting device detection according to the link detection request, and obtains a link of the neighboring switching device port information of the opposite end to generate a link. status information.
  • the processor 81 is further configured to start a link update timer that is separately set for each switch device, and send a link detection request to the switching device corresponding to any link update timer after any link update timer expires;
  • the processor 8 1 After the processor 8 1 receives the link state information sent by each switching device through the at least one communication interface,
  • the processor 81 is further configured to reset a link update timer corresponding to each switching device.
  • the processor 81 is further configured to determine, according to the link state information, whether there is a faulty link between the switching devices; if there is a faulty link between the switching devices, the first switching device at one end of the faulty link Configuring the first flow table according to the link state information, so that the first switching device sends the received service packet to the third switching device that establishes a normal link with the first switching device according to the first flow table; and passes at least one communication interface.
  • the switching device configures the second flow table, so that the third switching device forwards the received service data to the second switching device at the other end of the faulty link according to the second flow table, where the second flow table is used to instruct the third switching device to receive the first
  • the service data transmitted by the faulty link between the switching device and the second switching device, and the service data is output through the port connected to the third switching device by the second switching device.
  • the processor 81 is further configured to: if the faulty link between the first switching device and the second switching device is restored, the control device configures a third flow table for the first switching device, so that the first switching device is configured according to the first The third-stream table sends the service packet to the second switching device.
  • the processor 81 is further configured to send, by using the at least one communication interface, a switching device status information request, where the switching device status information request is used to obtain port information and data packet statistics information of each switching device;
  • the at least one communication interface receives the switching device status information sent by each switching device; and determines, according to the status information of each switching device provided by the receiving unit, whether the switching device is overloaded; if the first switching device in each switching device is overloaded, And configuring, by the second switching device connected to the first switching device, the fourth flow table according to the link state information, so that the second switching device forwards the service packet sent to the first switching device to the third exchange according to the fourth flow table.
  • the device receives the data forwarding request of the third switching device, and configures, by the data forwarding request, a fifth flow table that is forwarded by the third switching device, so that the third switching device receives the received service according to the fifth flow table.
  • the fifth flow table Indicating a third switching device receives the second switching device sending a service packet and forward the service packet to the other switching devices.
  • the processor 81 is further configured to: if the first switching device is overloaded, the control device configures the sixth flow table for the second switching device, and configures the seventh flow table for the first switching device, so that The second switching device forwards the service packet to the first switching device according to the sixth flow table, and the first switching device forwards the service packet to the other switching device according to the seventh flow table.
  • the link status information includes:
  • the control device obtains link state information between the switching devices through link detection, so that when the link fault between the switching devices occurs, the control device can obtain the link state information obtained according to the link detection. Handle link failures in time to avoid communication interruptions.
  • the embodiment of the present invention provides a switching device 9 , which may be an electronic device that performs OpenFlow protocol forwarding data transmission in an SDN network, and may be an electronic device responsible for forwarding data, such as a switch, a router, a hub, etc., in the present invention.
  • the switching device 9 includes: at least one processor 91, The memory 92, the communication port 93, and the bus 94, the at least one processor 91, the memory 92, and the communication interface 93 are connected by a bus 94 and complete communication with each other.
  • the bus 94 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus 94 can be divided into an address bus, a data bus, a control bus, and the like.
  • the memory 92 is configured to store executable program code, the program code including computer operating instructions.
  • the memory 92 may include a high speed RAM memory, and may also include a non-volatile memory, for example: at least one disk saver.
  • the storage device stores: an operating system, an application, and a program code for implementing the embodiment of the present invention.
  • the operating system is for controlling and implementing processing functions performed by the processing unit.
  • the application includes program code, such as word processing software, email software.
  • the processor 91 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more configured to implement the embodiments of the present invention. integrated circuit.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the communication interface 93 is mainly used to implement communication between devices in this embodiment.
  • the processor 91 is configured to send a link to the control device by using at least one communication interface. State information, so that the control device configures a service data transmission link for each switching device according to the link state information;
  • the processor 91 is further configured to forward the service data according to the service data transmission link configured by the control device through the at least one communication interface.
  • the control device obtains link state information between the switching devices through link detection, so that when the link fault between the switching devices occurs, the control device can obtain the link state information obtained according to the link detection. Handle link failures in a timely manner.
  • the processor 91 is further configured to receive, by using the at least one communication interface, a link detection request sent by the control device, and perform detection by the neighboring switching device according to the link detection request, and generate the information of the neighboring switching device port of the opposite end. Link status information.
  • the processor 91 is further configured to: initiate a surviving timer; and perform probing by the neighboring switching device after the surviving timer expires, obtain link state information of the neighboring switching device by using the at least one communication interface, and generate link state information and The survival timer is reset.
  • the processor 91 is further configured to: send, by using each port, a probe packet to the neighboring switching device; and receive, by using the at least one communications interface, the neighboring switching device port information that is sent by the neighboring switching device according to the probe packet; The port information and the neighboring switching device port information generate link state information.
  • the control device obtains link state information between the switching devices through link detection, so that when the link fault between the switching devices occurs, the control device can detect the link state information obtained according to the link detection. Handle link failures in time to avoid communication interruptions.
  • the present invention provides a communication system 10, as shown in FIG. 20, comprising: a control device 1001 and at least two switching devices 1002, wherein
  • the control device 1001 is any of the control devices shown in FIG. 9 to FIG. 13
  • the switching device 1002 is any one of the switching devices shown in FIG. 14 to FIG. 17;
  • control device 1001 is the control device shown in Fig. 18.
  • the switching device 1002 is the switching device shown in Fig. 19.
  • the control device obtains each through link detection.
  • the link state information between the switching devices so that when a link failure occurs between the switching devices, the control device can process the link failure according to the link state information obtained by the link detection, thereby preventing the communication interruption from occurring.

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

本发明提供一种链路管理方法、设备和通信系统,涉及通讯网络领域,解决了控制设备在链路故障发生时不能对交换设备间的业务传输链路进行灵活配置的问题。该方法包括:控制设备接收各个交换设备发送的链路状态信息;所述控制设备根据所述链路状态信息为所述各个交换设备配置业务数据传输链路。本发明实施例应用于通讯网络领域。

Description

一种链路管理方法、 设备和通信系统 技术领域
本发明涉及通讯网络领域, 尤其涉及一种链路管理方法、 设备 和通信系统。 背景技术
在软件可定义网络( Software Defined Network , 简称 SDN )中, 网络交换模型协议 OpenFlow作为 SDN 网络中的一种交换标准实现 了控制面与转发面的分离, 基于 OpenFlow 这一标准, SDN 网络的 主要组成部分包括: 支持 OpenFlow 的交换设备和用于管理交换设 备的控制设备, 控制设备通过 OpenFlow 协议对交换设备进行配置 和管理。 交换设备作为网络中的关键节点, 在现有设备中开发的接 口又十分有限。 其中, 交换设备的转发行为由控制设备决定, 对控 制设备来说, 控制设备只能获取单个交换设备的端口信息和路由信 息。
在现有 SDN 网络中, 控制设备通过向交换设备发送特征请求 信息 feature request和统计请求信息 stats request , 并接收交换设备 根据 feature request 和 stats request 反馈的特征回复信息 feature reply、 统计回复信息 stats reply和路由信息以便获取交换设备当前 的运行状态, 而当交换设备间发生链路故障时, 控制设备无法根据 交换设备当前的运行状态利用没有链路故障的交换设备继续完成数 据通信。
发明人发现现有技术中至少存在如下问题: 控制设备由于只能 根据交换设备当前的运行状态获取每个交换设备的端口信息和路由 信息, 因此当交换设备故障发生时, 控制设备无法及时将当前在发 生故障的交换设备上传输的业务数据发送至其他正常的交换设备继 续完成数据通信, 从而导致通信中断。 发明内容
本发明的实施例提供一种链路管理方法、 设备和通信系统, 能 够实现对交换设备间用于业务传输链路的灵活配置, 从而避免通讯 中断发生。
为达到上述目 的, 本发明的实施例采用如下技术方案: 第一方面, 提供一种控制设备, 包括: 通过数据总线连接的处 理器和存储器, 以及分别与所述处理器和存储器连接的至少一个通 信接口, 其中,
所述处理器, 用于通过所述至少一个通信接口接收各个交换设 备发送的链路状态信息;
所述处理器, 还用于根据所述链路状态信息为所述各个交换设 备配置业务数据传输链路。
在第一种可能的实现方式中, 结合第一方面, 所述处理器通过 所述至少一个通信接口接收各个交换设备发送的链路状态信息之 前,
所述处理器, 还用于通过所述至少一个通信接口向所述各个交 换设备发送链路检测请求, 以便所述各个交换设备根据所述链路检 测请求进行邻近交换设备探测, 获取对端的所述邻近交换设备端口 信息后生成所述链路状态信息。
在第二种可能的实现方式中, 结合第一种可能的实现方式, 所 述处理器, 还用于启动为所述各个交换设备分别设置的链路更新定 时器, 并当任一所述链路更新定时器超时后向所述任一链路更新定 时器对应的交换设备发送所述链路检测请求;
所述处理器通过所述至少一个通信接口接收到所述各个交换设 备发送的链路状态信息后,
所述处理器, 还用于将所述各个交换设备分别对应的所述链路 更新定时器复位。
在第三种可能的实现方式中, 结合上述任一设备, 所述处理 器, 还用于根据所述链路状态信息判断所述各个交换设备之间是否 存在故障链路; 若所述各个交换设备之间存在故障链路, 则为所述 故障链路一端的第一交换设备根据所述链路状态信息配置第一流 表, 以便所述第一交换设备根据所述第一流表将接收到的业务报文 发送至与所述第一交换设备建立有正常链路的第三交换设备; 并通 过所述至少一个通信接口接收所述第三交换设备的数据转发请求, 并根据所述数据转发请求为所述第三交换设备配置第二流表, 以便 所述第三交换设备根据所述第二流表将所述接收到的业务数据转发 至所述故障链路另一端的第二交换设备, 所述第二流表用于指示所 述第三交换设备接收所述第一交换设备与所述第二交换设备之间故 障链路传输的所述业务数据, 并将所述业务数据通过所述第二交换 设备与所述第三交换设备连接的端口输出。
在第四种可能实现的方式中, 结合第三种可能实现的方式, 所 述处理器, 还用于若所述第一交换设备与所述第二交换设备间的所 述故障链路恢复正常, 则所述控制设备为所述第一交换设备配置第 三流表, 以便所述第一交换设备根据所述第三流表将业务报文发送 至所述第二交换设备。
在第五种可能的实现方式中, 结合上述任一设备, 所述处理 器, 还用于通过所述至少一个通信接口向所述各个交换设备发送交 换设备状态信息请求, 所述交换设备状态信息请求用于获取所述各 个交换设备的端口信息和所述数据包统计信息; 并通过所述至少一 个通信接口接收所述各个交换设备发送的交换设备状态信息; 根据 所述接收单元提供的所述各个交换设备的状态信息判断所述各个交 换设备中是否有交换设备发生过载; 若所述各个交换设备中第一交 换设备发生过载, 则对与所述第一交换设备连接的第二交换设备根 据所述链路状态信息配置第四流表, 以便所述第二交换设备根据所 述第四流表将发送至所述第一交换设备的业务报文转发至第三交换 设备; 接收所述第三交换设备的数据转发请求, 并根据所述数据转 发请求为所述第三交换设备配置对应所述业务报文转发的第五流 表, 以便所述第三交换设备根据所述第五流表将所述接收到的所述 业务报文转发至其他交换设备, 所述第五流表用于指示所述第三交 换设备接收所述第二交换设备发送的业务报文, 并将所述业务报文 转发至所述其他交换设备。
在第六种可能的实现方式中, 结合第五种可能的实现方式, 所 述处理器还用于若所述第一交换设备发生过载的情况消除, 则所述 控制设备为所述第二交换设备配置第六流表, 并为所述第一交换设 备配置第七流表, 以便所述第二交换设备根据所述第六流表将业务 报文转发至所述第一交换设备, 并由所述第一交换设备根据所述第 七流表将所述业务报文转发至所述其他交换设备。
在第七种可能的实现方式中, 结合上述任一设备, 所述链路状 态信息包括:
链路两端的交换设备的标识, 所述交换设备端口的编号, 所述 交换设备端口的多址接入信道 MAC 地址和所述交换设备间链路的 连接状态。 第二方面, 提供一种交换设备, 包括: 通过数据总线连接的处 理器和存储器, 以及分别与所述处理器和存储器连接的至少一个通 信接口, 其中,
所述处理器, 用于通过所述至少一个通信接口向控制设备发送 链路状态信息, 以便所述控制设备根据所述链路状态信息为所述各 个交换设备配置业务数据传输链路;
所述处理器, 还用于通过所述至少一个通信接口根据所述控制 设备配置的业务数据传输链路向与所述交换设备转发业务数据。
在第一种可能的实现方式中, 结合第二方面, 所述处理器, 还 用于通过所述至少一个通信接口接收所述控制设备发送的链路检测 请求; 并根据所述链路检测请求进行邻近交换设备探测, 并在获取 对端的所述邻近交换设备端口信息后生成所述链路状态信息。
在第二种可能实现的方式中, 结合第二方面, 所述处理器, 还 用于启动存活计时器; 并在所述存活计时器超时后进行邻近交换设 备探测, 通过所述至少一个通信接口获取对端的所述邻近交换设备 端口信息后生成所述链路状态信息并对所述存活计时器复位。
在第三种可能的实现方式中, 结合第一种可能的实现方式或第 二种可能的实现方式, 所述处理器, 还用于通过各个端口向所述邻 近交换设备发送探测报文; 并通过所述至少一个通信接口接收所述 邻近交换设备根据所述探测报文响应的所述邻近交换设备端口信 息; 根据所述交换设备的端口信息及所述邻近交换设备端口信息生 成所述链路状态信息。
第三方面, 提供一种链路管理方法, 包括:
控制设备接收各个交换设备发送的链路状态信息;
所述控制设备根据所述链路状态信息为所述各个交换设备配置 业务数据传输链路。
在第一种可能的实现方式中, 结合第三方面, 所述控制设备接 收各个交换设备发送的链路状态信息之前, 还包括:
所述控制设备向所述各个交换设备发送链路检测请求, 以便所 述各个交换设备根据所述链路检测请求进行邻近交换设备探测, 获 取对端的所述邻近交换设备端口信息后生成所述链路状态信息。
在第二种可能的实现方式中, 结合第一种可能的实现方式, 所述控制设备启动为所述各个交换设备分别设置链路更新定时 器, 并当任一所述链路更新定时器超时后向所述任一链路更新定时 器对应的交换设备发送所述链路检测请求;
所述控制设备接收到所述各个交换设备发送的链路状态信息后 还包括:
将所述各个交换设备分别对应的所述链路更新定时器复位。 在第三种可能的实现方式中, 结合上述方法, 所述控制设备接 收各个交换设备发送的链路状态信息后, 还包括:
根据所述链路状态信息判断所述各个交换设备之间是否存在 故障链路;
若所述各个交换设备之间存在故障链路, 则为所述故障链路一 端的第一交换设备根据所述链路状态信息配置第一流表, 以便所述 第一交换设备根据所述第一流表将接收到的业务报文发送至与所述 第一交换设备建立有正常链路的第三交换设备;
接收所述第三交换设备的数据转发请求, 并根据所述数据转发 请求为所述第三交换设备配置第二流表, 以便所述第三交换设备根 据所述第二流表将所述接收到的业务报文转发至所述故障链路另一 端的第二交换设备, 所述第二流表用于指示所述第三交换设备接收 所述第一交换设备与所述第二交换设备之间故障链路传输的所述业 务报文, 并将所述业务报文通过所述第二交换设备与所述第三交换 设备连接的端口输出。
在第四种可能的实现方式中, 结合第三种可能的实现方式, 所 述方法还包括:
若所述第一交换设备与所述第二交换设备间的所述故障链路恢 复正常, 则所述控制设备为所述第一交换设备配置第三流表, 以便 所述第一交换设备根据所述第三流表将业务报文发送至所述第二交 换设备。
在第五种可能实现的方式中, 结合第三方面至第二种可能的实 现方式所述的任一方法, 所述方法还包括:
所述控制设备向所述各个交换设备发送交换设备状态信息请 求, 所述交换设备状态信息请求用于获取所述各个交换设备的端口 信息和所述数据包统计信息;
所述控制设备接收所述各个交换设备发送的交换设备状态信 息, 并根据所述各个交换设备的状态信息判断所述各个交换设备中 是否有交换设备发生过载;
若所述各个交换设备中第一交换设备发生过载, 则对与所述第 一交换设备连接的第二交换设备根据所述链路状态信息配置第四流 表, 以便所述第二交换设备根据所述第四流表将发送至所述第一交 换设备的业务报文转发至第三交换设备;
接收所述第三交换设备的数据转发请求, 并根据所述数据转发 请求为所述第三交换设备配置对应所述业务报文转发的第五流表, 以便所述第三交换设备根据所述第五流表将所述接收到的所述业务 报文转发至其他交换设备, 所述第五流表用于指示所述第三交换设 备接收所述第二交换设备发送的业务报文, 并将所述业务报文转发 至所述其他交换设备。
在第六种可能实现的方式中, 结合第五种可能实现的方式, 所 述方法还包括:
若所述第一交换设备发生过载的情况消除, 则所述控制设备为 所述第二交换设备配置第六流表, 并为所述第一交换设备配置第七 流表, 以便所述第二交换设备根据所述第六流表将业务报文转发至 所述第一交换设备, 并由所述第一交换设备根据所述第七流表将所 述业务报文转发至所述其他交换设备。
在第七种可能实现的方式中, 结合上述方法, 所述链路状态信 息包括:
链路两端的交换设备的标识, 所述交换设备端口的编号, 所述 交换设备端口的多址接入信道 MAC 地址和所述交换设备间链路的 连接状态。
第四方面, 提供一种链路管理方法, 包括:
交换设备向控制设备发送链路状态信息, 以便所述控制设备根 据所述链路状态信息为所述各个交换设备配置业务数据传输链路; 所述交换设备根据所述控制设备配置的业务数据传输链路转发 业务数据。
在第一种可能的实现方式中, 结合第四方面, 所述交换设备向 控制设备发送链路状态信息前, 还包括:
所述交换设备接收所述控制设备发送的链路检测请求; 所述交换设备根据所述链路检测请求进行邻近交换设备探测, 获取对端的所述邻近交换设备端口信息后生成所述链路状态信息。
在第二种可能的实现方式中, 结合第四方面, 所述交换设备向 控制设备发送链路状态信息前, 还包括: 所述交换设备启动存活计时器;
所述交换设备在所述存活计时器超时后进行邻近交换设备探 测, 获取对端的所述邻近交换设备端口信息后生成所述链路状态信 息并对所述存活计时器复位。
在第三种可能的实现方式中, 结合第一种可能的实现方式或第 二种可能的实现方式, 所述根据所述链路检测请求进行邻近交换设 备探测, 获取对端的所述邻近交换设备端口信息后生成所述链路状 态信息, 包括:
所述交换设备通过各个端口向所述邻近交换设备发送探测报 文;
所述交换设备接收所述邻近交换设备根据所述探测报文响应的 所述邻近交换设备端口信息;
根据所述交换设备的端口信息及所述邻近交换设备端口信息生 成所述链路状态信息。
第五方面, 提供一种控制设备, 包括:
接收单元, 用于接收各个交换设备发送的链路状态信息; 配置单元, 用于根据所述接收单元提供的所述链路状态信息为 所述各个交换设备配置业务数据传输链路。
在第一种可能的实现方式中, 结合第五方面, 所述控制设备接 收各个交换设备发送的链路状态信息之前, 还包括:
发送单元, 用于向所述各个交换设备发送链路检测请求, 以便 所述各个交换设备根据所述链路检测请求进行邻近交换设备探测, 获取对端的所述邻近交换设备端口信息后生成所述链路状态信息。
在第二种可能的实现方式中, 结合第一种可能的实现方式, 所 述发送单元还包括:
计时子单元, 用于启动为所述各个交换设备分别设置的链路更 新定时器, 并当任一所述链路更新定时器超时后向所述任一链路更 新定时器对应的交换设备发送所述链路检测请求;
所述控制设备接收到所述各个交换设备发送的链路状态信息后 还包括:
所述计时子单元, 还用于将所述各个交换设备分别对应的所述 链路更新定时器复位。
在第三种可能的实现方式中, 结合上述任一设备, 所述控制设 备还包括:
判别单元, 用于根据所述接收单元提供的所述链路状态信息判 断所述各个交换设备之间是否存在故障链路;
检测配置单元, 用于若所述各个交换设备之间存在故障链路, 则为所述故障链路一端的第一交换设备根据所述链路状态信息配置 第一流表, 以便所述第一交换设备根据所述第一流表将接收到的业 务报文发送至与所述第一交换设备建立有正常链路的第三交换设 备;
所述接收单元, 还用于接收所述第三交换设备的数据转发请 求, 并根据所述数据转发请求为所述第三交换设备配置第二流表, 以便所述第三交换设备根据所述第二流表将所述接收到的业务报文 转发至所述故障链路另一端的第二交换设备, 所述第二流表用于指 示所述第三交换设备接收所述第一交换设备与所述第二交换设备之 间故障链路传输的所述业务报文, 并将所述业务报文通过所述第二 交换设备与所述第三交换设备连接的端口输出。
在第四种可能的实现方式中, 结合第三种可能的实现方式, 检 测配置单元, 用于若所述第一交换设备与所述第二交换设备间的所 述故障链路恢复正常, 则所述控制设备为所述第一交换设备配置第 三流表, 以便所述第一交换设备根据所述第三流表将业务报文发送 至所述第二交换设备。
在第五种可能实现的方式中, 结合第五方面至第二种可能实现 的方式所述的任一设备, 所述控制设备还包括:
所述发送单元, 还用于向所述各个交换设备发送交换设备状态 信息请求, 所述交换设备状态信息请求用于获取所述各个交换设备 的端口信息和所述数据包统计信息; 所述接收单元, 还用于接收所述各个交换设备发送的交换设备 状态信息;
检测单元, 用于根据所述接收单元提供的所述各个交换设备的 状态信息判断所述各个交换设备中是否有交换设备发生过载;
配置查询单元, 还用于若所述各个交换设备中第一交换设备发 生过载, 则对与所述第一交换设备连接的第二交换设备根据所述链 路状态信息配置第四流表, 以便所述第二交换设备根据所述第四流 表将发送至所述第一交换设备的业务报文转发至第三交换设备; 所述接收单元, 还用于接收所述第三交换设备的数据转发请 求, 并根据所述数据转发请求为所述第三交换设备配置对应所述业 务报文转发的第五流表, 以便所述第三交换设备根据所述第五流表 将所述接收到的所述业务报文转发至其他交换设备, 所述第五流表 用于指示所述第三交换设备接收所述第二交换设备发送的业务报 文, 并将所述业务报文转发至所述其他交换设备。
在第六种可能的实现方式中, 结合第五种可能实现的方式, 所 述配置查询单元, 还用于若所述第一交换设备发生过载的情况消 除, 则所述控制设备为所述第二交换设备配置第六流表, 并为所述 第一交换设备配置第七流表, 以便所述第二交换设备根据所述第六 流表将业务报文转发至所述第一交换设备, 并由所述第一交换设备 根据所述第七流表将所述业务报文转发至所述其他交换设备。
在第七种可能的实现方式中, 结合上述任一设备, 所述链路状 态信息包括:
链路两端的交换设备的标识, 所述交换设备端口的编号, 所述 交换设备端口的多址接入信道 MAC 地址和所述交换设备间链路的 连接状态。
第六方面, 提供一种交换设备, 包括:
发送单元, 用于向控制设备发送链路状态信息, 以便所述控制 设备根据所述链路状态信息为所述各个交换设备配置业务数据传输 链路; 转发单元, 用于根据所述控制设备配置的业务数据传输链路转 发业务数据。
在第一种可能的实现方式中, 结合第六方面, 所述交换设备还 包括:
接收单元, 用于接收所述控制设备发送的链路检测请求; 检测单元, 用于根据所述链路检测请求进行邻近交换设备探 测, 并在获取对端的所述邻近交换设备端口信息后生成所述链路状 态信息。
在第二种可能的实现方式中, 结合第六方面, 所述交换设备还 包括:
启动单元, 用于启动存活计时器;
获取单元, 用于在所述存活计时器超时后进行邻近交换设备探 测, 获取对端的所述邻近交换设备端口信息后生成所述链路状态信 息并对所述存活计时器复位。
在第三种可能的实现方式中, 结合第一种可能的实现方式或第 二种可能的实现方式, 所述获取单元包括:
检测子单元, 用于通过各个端口向所述邻近交换设备发送探测 报文;
接收子单元, 用于接收所述邻近交换设备根据所述探测报文响 应的所述邻近交换设备端口信息;
生成子单元, 用于根据所述交换设备的端口信息及所述邻近交 换设备端口信息生成所述链路状态信息。 在第七方面, 提供一种通信系统, 包括: 控制设备和至少两个 交换设备, 其中,
所述控制设备为第一方面所述任一控制设备, 所述交换设备为 第二方面所述任一交换设备;
或者, 所述控制设备为第五方面所述任一控制设备, 或所述交 换设备为第六方面所述任一交换设备。 本发明实施例提供的链路管理方法、 设备和通信系统, 控制设 备通过链路检测获得各个交换设备间链路状态信息, 能够实现对交 换设备间用于业务传输链路的灵活配置, 从而避免通讯中断发生。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下 面将对实施例或现有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是本发明的一些实施例, 对于 本领域普通技术人员来讲, 在不付出创造性劳动的前提下, 还可以 根据这些附图获得其他的附图。
图 1 为本发明实施例提供一种链路管理方法的流程示意图; 图 2为本发明实施例提供另一种链路管理方法的流程示意图; 图 3 为本发明另一实施例提供一种链路管理方法的流程示意 图;
图 4为本发明另一实施例提供另一种链路管理方法的流程示意 图;
图 5 为本发明另一实施例提供又一种链路管理方法的流程示意 图;
图 6 为本发明又一实施例提供一种链路管理方法的流程示意 图;
图 7为本发明又一实施例提供另一种链路管理方法的流程示意 图;
图 8 为本发明再一实施例提供一种链路管理方法的流程示意 图;
图 9为本发明再一实施例提供另一种链路管理方法的流程示意 图;
图 10为本发明实施例提供的一种控制设备的结构示意图; 图 1 1 为本发明实施例提供的另一种控制设备的结构示意图; 图 12为本发明实施例提供的又一种控制设备的结构示意图; 图 13为本发明实施例提供的再一种控制设备的结构示意图; 图 14为本发明实施例提供的一种交换设备的结构示意图; 图 15为本发明实施例提供的另一种交换设备的结构示意图; 图 16为本发明实施例提供的又一种交换设备的结构示意图; 图 17为本发明实施例提供的再一种交换设备的结构示意图; 图 1 8 为本发明另一实施例提供的一种控制设备的结构示意 图;
图 19 为本发明另一实施例提供的一种交换设备的结构示意 图;
图 20为本发明提供的一种通信系统结构示意图。 具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术 方案进行清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明 一部分实施例, 而不是全部的实施例。 基于本发明中的实施例, 本 领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他 实施例, 都属于本发明保护的范围。
在网络交换模型 OpenFlow协议下, OpenFlow协议将传统的物 理固定的硬件改造成为动态可变的软件可定义网络 ( Software Defined Network , SDN ) , 实现了控制面与转发面的分离, 基于 OpenFlow 协议的 SDN 网络主要组成部分包括: 控制设备和至少 1 个支持 OpenFlow协议的交换设备, 其中控制设备根据 OpenFlow协 议对交换设备进行配置和管理。 这里交换设备可以为交换机、 路由 器、 集线器等用 于转发数据的电子设备; 控制设备可以为支持 OpenFlow协议的控制板。 具体的, 支持 OpenFlow协议的交换设备 组成部分包括: 流表 ( Flow Table )、 安全通道 ( Secure Channel ) 和 OpenFlow协议 ( OF Protocol ) , 交换设备通过安全通道连接到控制 设备, 控制设备通过对交换设备流表的查询对交换设备进行管理。
本发明实施例提供了一种链路管理方法, 参照图 1 所示, 具体 流程如下:
101、 控制设备接收各个交换设备发送的链路状态信息。
这里控制设备通过接收各个交换设备发送的链路检测回复 link detection reply报文获取各个交换设备间的链路状态信息。
其中, 各个交换设备通过邻居发现功能获得的链路状态信息, 然后各个交换设备将生成的链路状态信息用 OF 协议封装成 link detection reply才艮文发送至控制设备。
102、控制设备根据该链路状态信息为各个交换设备配置业务数 据传输链路。
这里由于控制设备根据链路状态信息获知各个交换设备当前 的运行状态, 以及各个交换设备间的链路状态, 以便当交换设备间 链路发生故障或者某个交换设备发生过载时, 控制设备能够根据链 路状态信息为各个交换设备配置业务数据传输链路。 具体的, 控制 设备根据该链路状态信息为各个交换设备配置的业务数据传输链路 中, 该业务数据传输链路上的业务数据不仅可以由业务数据传输链 路中的上一级交换设备的端口处得到, 还可以来自与交换设备连接 的客户端。
其中, 该链路状态信息包括: 链路两端的交换设备的标识, 端 口编号,端口的多址接入信道 MAC地址和交换设备间链路的连接状 态。
可选的, 控制设备接收各个交换设备发送的链路状态信息之 前, 还包括:
控制设备向各个交换设备发送链路检测请求, 以便各个交换设 备根据链路检测请求进行邻近交换设备探测, 获取对端的邻近交换 设备端口信息后生成链路状态信息。
本发明实施例提供的链路管理方法, 控制设备通过链路检测获 得各个交换设备间链路状态信息, 能够实现对交换设备间用于业务 传输链路的灵活配置, 从而避免通讯中断发生。
本发明实施例提供了一种链路管理方法, 参照图 2所示, 具体 流程如下:
201、 交换设备向控制设备发送链路状态信息, 以便控制设备 根据链路状态信息为各个交换设备配置业务数据传输链路。
这里交换设备根据触发邻居发现功能获取与该交换设备相连 链路对端的交换设备上的链路状态信息, 其中, 链路状态信息为链 路两端的交换设备的标识, 端口的编号, 端口的多址接入信道 MAC 地址以及所连接链路上的连接状态。 这里发起邻居发现功能的交换 设备将上述链路状态信息封装入链路检测回复报文中, 并将该链路 检测回复报文发送至控制设备, 以便控制设备根据链路检测回复报 文中的链路状态信息对各个交换设备配置业务数据传输链路。
202、 交换设备根据该控制设备配置的业务数据传输链路转发 业务数据。
本发明实施例提供的链路管理方法, 控制设备通过链路检测获 得各个交换设备间链路状态信息, 能够实现对交换设备间用于业务 传输链路的灵活配置, 从而避免通讯中断发生。
具体的, 以下结合具体的实施例进行说明。
可以在图 1和图 2所示的实施例的基础上, 参照图 3、 4、 5所示, 本发明的实施例提供了一种链路管理方法, 提供了控制设备通过接 收交换设备发送的链路状态信息更新各个交换设备间链路状态信息 的具体方法, 主要包括: 控制设备发起的链路更新流程和交换设备 发起的链路更新流程; 其中参照图 3 所示, 为控制设备发起的链路 更新流程, 具体步骤如下:
301 a ,控制设备启动为各个交换设备分别设置链路更新定时器, 并当任一链路更新定时器超时后向任一链路更新定时器对应的交换 设备发送链路检测请求。
这里控制设备为各个交换设备分别设置链路更新定时器, 当任 一链路更新定时器超时后, 会发起一段链路更新过程, 此时控制设 备向该链路更新定时器对应的交换设备发送链路检测请求报文, 以 便交换设备根据链路检测请求报文反馈当前链路更新状态。 302a , 交换设备通过接收控制设备发送的链路检测请求进行邻 近交换设备探测, 获取对端的邻近交换设备端口信息后生成链路状 态信息。
这里交换设备根据接收的链路检测请求触发对邻近交换设备的 探测。
其中,交换设备根据所述链路检测请求进行邻近交换设备探测, 获取对端的邻近交换设备端口信息后生成链路状态信息, 具体包括: a、 交换设备通过各个端口向邻近交换设备发送探测报文。
其中, 交换设备根据控制设备发送的链路检测请求报文触发对 邻近交换设备的探测流程, 并向邻近的交换设备发送探测报文, 以 便获取对端交换设备的链路状态信息。
b、交换设备接收邻近交换设备根据探测报文响应的邻近交换设 备端口信息。
这里交换设备接收邻近交换设备发送的邻近交换设备端口信息 包括: 邻近交换设备的标识, 邻近交换设备的端口编号, 邻近交换 设备的端口的多址接入信道 MAC地址。
c、根据交换设备的端口信息及邻近交换设备端口信息生成链路 状态信息。
交换设备将上述步骤中邻近交换设备的端口信息及该交换设备 自身的标识, 端口编号, 端口的多址接入信道 MAC地址生成链路状 态信息, 其中链路状态信息还包括该交换设备与邻近交换设备的链 路连接状态。
303 a , 交换设备向控制设备发送链路状态信息, 以便控制设备 根据链路状态信息为各个交换设备配置业务数据传输链路。
这里交换设备根据触发邻居发现功能获取与该交换设备相连 链路对端的交换设备上的链路状态信息, 其中, 链路状态信息为链 路两端的交换设备的标识, 端口的编号, 端口的多址接入信道 MAC 地址以及所连接链路上的连接状态。 这里发起邻居发现功能的交换 设备将上述链路状态信息封装入链路检测回复报文中, 并将该链路 检测回复报文发送至控制设备, 以便控制设备根据链路检测回复报 文中的链路状态信息对各个交换设备配置业务数据传输链路。
304a , 控制设备接收各个交换设备发送的链路状态信息, 并将 各个交换设备分别对应的链路更新定时器复位。
其中, 控制设备接收到的链路状态信息是以链路检测回复报文 的形式接收的, 控制设备将链路检测回复报文交给控制设备中链路 管理实体 LME ( Link Management Entity ) 处理, 并由 LME从链路 检测回复报文中抽取出链路状态信息, 并将该链路状态信息储存至 链路管理数据库 LMDB(Link Management Data Base)中,从而对更新 的信息进行统计记录。
本发明实施例提供的链路管理方法, 当控制设备的链路更新定 时器超时时, 通过向交换设备发送链路检测请求触发交换设备对邻 近交换设备的探测, 并根据探测邻近交换设备获取该交换设备与邻 近交换设备的链路状态信息, 以便当交换设备间的链路故障发生 时, 控制设备能够根据链路检测获得的链路状态信息及时处理链路 故障, 从而避免通讯中断发生。
其中参照图 4所示, 为交换设备发起的链路更新流程, 具体步 骤如下:
301 b , 交换设备启动存活计时器。
这里由交换设备主动发起的链路更新流程, 交换设备启动存活 计时器, 该存活计时器用于触发交换设备对邻近交换设备的探测流 程。
302b , 交换设备在存活计时器超时后进行邻近交换设备探测, 获取对端的邻近交换设备端口信息后生成链路状态信息并对所述存 活计时器复位。
其中, 交换设备发起的链路更新流程中, 所更新的链路状况信 息包括: 链路两端的交换设备的标识, 该链路两端的交换设备端口 的编号,该端口的多址接入信道 MAC地址和交换设备间链路的连接 状态。 具体探测流程如图 3所示的实施例中步骤 303 a所述,此处不再 贅述。
303b , 交换设备向控制设备发送链路状态信息, 以便控制设备 根据链路状态信息为各个交换设备配置业务数据传输链路。
这里交换设备将生成的链路状态信息通过封装为 Open Flow协 议的链路检测回复报文, 并将该链路检测回复报文发送至控制设备, 当交换设备将该链路检测回复报文发送至控制设备之后, 交换设备 将自身的存活计时器复位, 以便交换设备根据存活计时器计时预备 进入下一个周期开始链路更新。
本发明实施例提供的链路管理方法, 当交换设备的存活计时器 超时时, 通过触发对邻近交换设备的探测, 并根据探测邻近交换设 备获取邻近交换设备的状态信息, 并根据该状态信息生成的链路状 态信息将该链路状态信息发送至控制设备, 以便当交换设备间的链 路故障发生时, 控制设备能够根据链路检测获得的链路状态信息及 时处理链路故障, 从而避免通讯中断发生。
参照图 5所示, 结合图 3与图 4所示的实施例, 链路更新的方 法还包括: 控制设备端对应各个交换设备设置链路更新定时器, 交 换设备端对应控制设备端设置存活计时器, 其中, 控制设备端的链 路更新定时器与交换设备端的存活计时器同步计时, 当链路更新定 时器超时时, 控制设备发送链路检测请求至交换设备, 以便交换设 备根据链路检测请求触发对邻近交换设备的探测, 并将由探测获得 的链路状态信息发送至控制设备, 再由控制设备根据接收到交换设 备发送的链路状态信息将链路更新定时器复位; 或者, 当交换设备 的存活计时器超时, 交换设备由于存活计时器超时触发对邻近交换 设备的探测, 并将由探测获得的链路状态信息发送至控制设备, 同 时将存活计时器复位, 这样对于控制设备端或交换设备端都可以避 免在短时间内再一次由于任一端的计时器没有复位, 进而在计时超 时后再一次的发起链路更新, 避免了网络资源的浪费;
具体的, 由于控制设备的链路更新定时器与交换设备的存活计 时器可能由于设定的不同而计时周期也不相同, 但在控制设备发起 的链路更新或交换设备发起的链路更新结束后控制设备的链路更新 定时器与交换设备的存活计时器都需要全部复位, 这样就能够避免 由于控制设备端发起的链路更新结束后交换设备的存活计时器没有 复位, 进而在交换设备的存活计时器超时后, 再一次的由交换设备 端主动进行链路更新, 从而避免由于控制设备接收该交换设备发送 的链路状态信息为控制设备端的链路管理数据库 LMDE增加负担, 造成网络资源上的浪费。
进一步的还可以避免由于其中一端计时器的故障使得链路更新 停止, 从而阻碍了控制设备对交换设备间数据的调配以及客户端间 的通信传输。
参照图 6所示, 可在图 1 , 图 2 , 图 3 , 图 4和图 5所示的实施 例的基础上, 本发明实施例提供一种链路管理方法, 提供了控制设 备根据链路状态信息对交换设备间存在链路故障时具体解决办法, 具体流程包括:
401、 控制设备向各个交换设备发送链路检测请求。
这里对照图 3 所示的实施例, 控制设备可以通过发送链路检测 请求触发交换设备间对邻近交换设备的探测, 并通过交换设备反馈 的链路状态信息获悉各个交换设备间当前链路状态信息, 以便当交 换设备间链路发生故障或交换设备发生过载时, 控制设备可以根据 链路状态信息获取当前控制的交换设备之间的链路状态, 及时进行 链路调配避免传输路径上的通信中断, 当然在步骤 401 之前还可以 包括如图 3 所示的实施例所述的链路更新过程, 即在步骤 401 之前 还包括控制设备侧根据控制设备端链路更新定时器计时超时触发链 路更新。
402、 交换设备进行邻近交换设备探测, 获取对端的邻近交换设 备端口信息后生成链路状态信息。
这里对照图 4所示的实施例, 交换设备可以根据控制设备端发 出的链路检测请求而触发对邻近交换设备的探测, 当然还可以根据 交换设备端存活计时器超时触发对邻近交换设备的探测 (只是当采 用交换设备根据交换设备端存活计时器超时触发对邻近交换设备的 探测的方案时, 在一个链路状态更新的过程中不包括步骤 401 )。 通 过对邻近交换设备的探测获取对端的邻近交换设备端口信息后生成 链路状态信息, 由于触发对邻近交换设备进行探测的方式有控制设 备发送链路检测请求触发和交换设备端存活计时器超时触发两种, 对照图 3与图 4所示的实施例, 则在步骤 402之前还包括如图 4所 示的实施例所述的链路更新过程, 即在步骤 402之前还包括交换设 备侧由于交换设备端存活计时器的超时触发链路更新。 区别于图 3 所示的实施例, 其中步骤 402 中交换设备进行邻近交换设备的探测 不仅可以通过接收控制设备端由于链路更新定时器超时发送的链路 检测请求触发对邻近交换设备探测, 还可以根据由于交换设备端存 活计时器超时触发对邻近交换设备探测。
403、 交换设备向控制设备发送链路状态信息, 以便控制设备根 据链路状态信息为各个交换设备配置业务数据传输链路。
这里, 对照图 3 , 图 4 所示的实施例, 当交换设备将链路状态 信息发送至控制设备后, 即步骤 403之后, 对照图 3所示的实施例, 控制设备接收交换设备发送的链路状态信息后将链路状态信息通过 控制设备中的链路管理实体 LME 将链路状态信息储存至链路管理 数据库 LMDB 中, 并将链路更新定时器复位, 控制设备端发起的链 路更新过程结束; 或者, 在步骤 403之后, 对照图 4所示的实施例, 当交换设备发送链路状态信息后, 交换设备将自身的存活计时器复 位, 交换设备发起的链路更新过程结束。
404、控制设备根据链路状态信息判断各个交换设备之间是否存 在故障链路。
这里控制设备中的链路管理实体 LME 通过对链路管理数据库 LMDB 中储存的链路状态信息发现各个交换设备间是否存在故障链 路, 以便控制设备对发生故障链路上的业务流进行路径上的调整。
405、 若各个交换设备之间存在故障链路, 则为故障链路一端的 第一交换设备根据链路状态信息配置第一流表, 以便第一交换设备 根据第一流表将接收到的业务报文发送至与第一交换设备建立有正 常链路的第三交换设备。
这里控制设备根据链路状态信息中的各个交换设备的连接状态 发现各个交换设备之间存在故障链路, 并为故障链路两端的第一交 换设备配置第一流表, 其中控制设备对第一交换设备配置的第一流 表用于将原有要发送至第二交换设备的业务报文, 根据对第一交换 设备重新配置的第一流表将该业务报文发送至第三交换设备, 其中 控制设备通过第一交换设备与第三交换设备间的链路状态信息发现 第一交换设备与第三交换设备间的链路正常, 可完成业务报文的转 发。
具体的, 链路状态信息包括: 链路两端的交换设备的标识, 该 交换设备端口的编号,交换设备端口的多址接入信道 MAC地址和所 述交换设备间链路的连接状态。
其中如图 6所示, 由于第一交换设备与第二交换设备间存在链 路故障, 第一交换设备根据控制设备配置的第一流表将预定发送至 第二交换设备的业务报文转发至第三交换设备 (其中第一交换设备 预定发送至第二交换设备的业务报文在图中用虚线示出 )。
406、 控制设备接收第三交换设备的数据转发请求, 并根据数据 转发请求为第三交换设备配置第二流表, 以便第三交换设备根据第 二流表将接收到的业务报文转发至故障链路另一端的第二交换设 备。
其中, 第二流表用于指示第三交换设备接收第一交换设备与第 二交换设备之间故障链路传输的业务报文, 并将业务报文通过第二 交换设备与第三交换设备连接的端口输出。
这里由于第三交换设备接收来自第一交换设备上的业务报文后 找不到匹配项, 即第三交换设备无法查找到接收第三交换设备转发 业务报文的对端交换设备, 此时第三交换设备向控制设备发送数据 转发请求, 控制设备在接收到第三交换设备的数据转发请求后为第 三交换设备配置第二流表, 以便第三交换设备根据第二流表将接收 到的业务报文转发至与故障链路另一端的第二交换设备相连的下一 级设备, 其中该下一级设备可以是与第二交换设备相连的客户端, 也可以是与第二交换设备相连的其他负责转发业务数据的交换设 备。
407、 若第一交换设备与第二交换设备间的故障链路恢复正常, 则控制设备为第一交换设备配置第三流表, 以便第一交换设备根据 第三流表将业务报文发送至第二交换设备。
这里控制设备通过周期性的链路更新发现第一交换设备与第 二交换设备间的故障链路消除, 控制设备根据链路状态信息中第一 交换设备与第二交换设备当前的连接状态, 重新对第一交换设备配 置流表即第三流表, 以便第一交换设备根据第三流表的指示将发送 至第三交换设备的业务报文发送至第二交换设备, 即恢复第一交换 设备与第二交换设备间的业务数据传输链路, 不再由第三交换设备 转发第一交换设备的业务报文至第二交换设备。
本发明实施例提供的链路管理方法, 控制设备通过链路检测获 得各个交换设备间链路状态信息, 以便当交换设备间的链路故障发 生时, 控制设备能够根据链路检测获得的链路状态信息及时处理链 路故障, 从而避免通讯中断发生。
参照图 7所示, 提供一种在 OpenFlow协议控制设备、 交换设 备及客户端的所组成的网络架构, 其中客户端可以是用户使用的接 入设备, 如个人计算机 ( Personal Computer,PC ) , 手机, 平板电脑, 也可以泛指传输网络中与交换设备相连的上一级设备; 具体的控制 设备连接 3 台交换设备, 其中交换设备 1连接客户端 1 , 交换设备 2 连接客户端 2 , 交换设备 1、 交换设备 2及交换设备 3之间存在链接 关系, 即交换设备 1 与交换设备 2 连接, 交换设备 2 与交换设备 3 连接, 同时交换设备 1 与交换设备 3 连接, 在该网络架构下若出现 交换设备之间的链路故障时, 按照上述实施例所述的方法, 控制设 备可以获取各个交换设备间的链路状态信息, 进而实现对各个交换 设备间的链路状态更新, 而当交换设备间出现链路故障后步骤 404〜 步骤 406的具体处理方法为:
a、 控制设备通过获取各个交换设备间的链路状态信息, 并根据 该链路状态信息发现交换设备 1 与交换设备 2之间的链路状态出现 异常。
这里交换设备 1 与交换设备 2之间的链路状态出现异常可以表 现为: 在交换设备 1 与交换设备 2进行业务通信时, 交换设备 1 或 交换设备 2 中对应收发报文的定时器发生接收超时, 这样在控制设 备发起链路更新时, 或者交换设备 1 或交换设备 2主动发起链路更 新时会将交换设备 1 与交换设备 2之间链路发生故障的信息发送至 控制设备, 以便控制设备根据链路状态信息获悉交换设备 1 与交换 设备 2之间链路发生故障, 并对交换设备 1 与交换设备 2之间链路 上传输的业务报文重新配置传输路径。
b、 当交换设备 1与交换设备 2之间的链路发生故障, 控制设备 向交换设备 1发送流表修改消息 flow-mod报文修改交换设备 1的流 表, 以便将交换设备 1 上预定发送至交换设备 2的来自客户端 1 的 业务报文转发至交换设备 3。
其中,控制设备发送至交换设备 1 的 flow-mod报文用于修改交 换设备 1 的流表。
c、 交换设备 3接收交换设备 1发送的业务报文, 由于没有接收 交换设备 3 的业务报文的链路对端的交换设备, 交换设备 3 通过 packet-in消息向控制设备请求对应交换设备 3 的流表, 控制设备在 接收到交换设备 3发送的请求后发送 flow-mod报文为交换设备 3配 置对应的流表, 以便交换设备 3根据 flow-mod报文配置对应交换设 备 3 的流表将交换设备 1发送的业务报文通过交换设备 3 与交换设 备 2相连的端口, 经由交换设备 2将客户端 1 的业务报文发送至客 户 端 2。
这里控制设备为交换设备 1 重新调配对端交换设备, 使得交换 设备 1接收业务报文经由交换设备 3转发, 再由交换设备 3将该业 务报文转发至交换设备 2 , 并由交换设备 2 将业务报文发送至客户 端 2 , 以便客户端 1 与客户端 2之间继续进行正常的业务传输; 其 中, 控制设备周期性的进行链路更新流程, 以便检测交换设备间的 链路状态是否正常。
d、 若控制设备的周期性的检测发现交换设备 1 与交换设备 2 之间的链路故障消除, 则通过步骤 401〜步骤 403用获取链路状态信 息更新控制设备中链路管理数据库 LMDB , 这里控制设备通过修改 交换设备 1 , 交换设备 2和交换设备 3 上的流表, 将客户端 1 与客 户端 2之间的业务恢复至原有链路上, 即交换设备 1 与交换设备 2 之间的链路, 同时删除交换设备 3 的流表, 避免客户端 1 与客户端 2 的业务报文在交换设备 1 与交换设备 2之间的链路传输的同时, 交换设备 1再一次的将客户端 1 的业务报文通过交换设备 3转发至 交换设备 2并由交换设备 2转发至客户端 2。
本发明实施例提供的链路管理方法, 控制设备通过各个交换设 备发送的链路状态信息, 当交换设备间链路发生故障时, 控制设备 根据链路状态信息及时灵活配置业务传输链路, 避免了客户端之间 通信中断的发生。
参照图 8所示, 可在图 1 , 图 2 , 图 3 , 图 4和图 5所示的实施 例的基础上, 本发明实施例提供一种链路管理方法, 提供了控制设 备根据链路状态信息对过载的交换设备的处理方法, 具体流程包括: 501、 控制设备向各个交换设备发送链路检测请求。
这里对照图 3 所示的实施例, 控制设备可以通过发送链路检测 请求触发交换设备间对邻近交换设备的探测, 并通过交换设备反馈 的链路状态信息获悉各个交换设备间当前链路状态信息, 以便当交 换设备间链路发生故障或交换设备发生过载时, 控制设备可以根据 链路状态信息获取当前控制的交换设备之间的链路状态, 及时进行 链路调配避免客户端之间的通信中断, 当然在步骤 501 之前还可以 包括如图 3 所示的实施例所述的链路更新过程, 即在步骤 501 之前 还包括控制设备侧根据控制设备端链路更新定时器计时超时触发链 路更新。
502、 交换设备进行邻近交换设备探测, 获取对端的邻近交换设 备端口信息后生成链路状态信息。
这里对照图 4所示的实施例, 交换设备可以根据控制设备端发 出的链路检测请求而触发对邻近交换设备的探测, 当然还可以根据 交换设备端存活计时器超时触发对邻近交换设备的探测 (只是当采 用交换设备根据交换设备端存活计时器超时触发对邻近交换设备的 探测的方案时, 在一个链路状态更新的过程中不包括步骤 501 )。 通 过对邻近交换设备的探测获取对端的邻近交换设备端口信息后生成 链路状态信息, 由于触发对邻近交换设备进行探测的方式有控制设 备发送链路检测请求触发和交换设备端存活计时器超时触发两种, 对照图 3与图 4所示的实施例, 则在步骤 502之前还包括如图 4所 示的实施例所述的链路更新过程, 即在步骤 502之前还包括交换设 备侧由于交换设备端存活计时器的超时触发链路更新。 区别于图 3 所示的实施例, 其中步骤 502 中交换设备进行邻近交换设备的探测 不仅可以通过接收控制设备端由于链路更新定时器超时发送的链路 检测请求触发对邻近交换设备探测, 还可以根据由于交换设备端存 活计时器超时触发对邻近交换设备探测。
503、 交换设备向控制设备发送链路状态信息, 以便控制设备根 据链路状态信息为各个交换设备配置业务数据传输链路。
这里, 对照图 3 , 图 4 所示的实施例, 当交换设备将链路状态 信息发送至控制设备后, 即步骤 503之后, 对照图 3所示的实施例, 控制设备接收交换设备发送的链路状态信息后将链路状态信息通过 控制设备中的链路管理实体 LME 将链路状态信息储存至链路管理 数据库 LMDB 中, 并将链路更新定时器复位, 控制设备端发起的链 路更新过程结束; 或者, 在步骤 503之后, 对照图 4所示的实施例, 当交换设备发送链路状态信息后, 交换设备将自身的存活计时器复 位, 交换设备发起的链路更新过程结束。
504、 控制设备向各个交换设备发送交换设备状态信息请求。 其中交换设备状态信息请求用于获取各个交换设备的端口信息 和数据包统计信息。
具体的控制设备周期性的向各个交换设备发起交换设备状态信 息请求, 以便及时获取各个交换设备的实时交换设备状态信息, 其 中控制设备发器的交换设备状态信息请求以特征请求 feature request才艮文和统计请求 stats request才艮文两种形式发送至各个交换 设备。
505、 控制设备接收各个交换设备发送的交换设备状态信息, 并 根据各个交换设备的状态信息判断各个交换设备中是否有交换设备 发生过载。
这里控制设备根据交换设备状态信息判断各个交换设备中是否 有交换设备发生过载,其中交换设备状态信息包括:交换设备的 CPU 负载值和交换设备端口的转发速率的最大带宽。
具体的, 控制设备通过接收各个交换设备发送的特征回复 feature reply报文获取各个交换设备的流表、数据流特征或者各个交 换设备端口的特征; 并通过接收统计回复 stats reply报文获取各个 交换设备接收数据包的统计信息, 以便控制设备根据交换设备状态 信息获悉各个交换设备的当前状态;
其中若 stats reply 文中统计的某个交换设备的端口上丟包率 过高, 则控制设备可以根据该交换设备的端口上丟包率过高这一特 征判断该交换设备发生过载。
506、 若各个交换设备中第一交换设备发生过载, 则对与第一交 换设备连接的第二交换设备根据链路状态信息配置第四流表, 以便 该第二交换设备根据第四流表将发送至第一交换设备的业务报文转 发至第三交换设备。
这里若第一交换设备发生过载, 控制设备中的链路管理实体 LME通过查询链路管理数据库 LMDB获取第一交换设备的链路配置 属性, 以便发现客户端之间是否存在另一条业务传输路径。
具体的, 控制设备为与第一交换设备连接的第二交换设备根据 链路状态信息配置对应第二交换设备的第四流表, 该第二交换设备 根据第四流表将发送至第一交换设备的业务报文转发至第三交换设 备。
如图 8所示, 由于第一交换设备发生过载, 第二交换设备根据 控制设备配置的第三流表将发送至第一交换设备的业务报文转发至 第三交换设备 (其中第二交换设备预定发送至第一交换设备的业务 报文在图中用虚线示出 )。
507、 控制设备接收第三交换设备的数据转发请求, 并根据数据 转发请求为第三交换设备配置对应业务报文转发的第五流表, 以便 第三交换设备根据第五流表将接收到的业务报文转发至其他交换设 备。
其中, 第五流表用于指示所述第三交换设备接收所述第二交换 设备预定发送至所述第一交换设备上的业务报文, 并将所述业务报 文转发至其他交换设备处。
508、 若第一交换设备发生过载的情况消除, 则控制设备为第 二交换设备配置第六流表, 并为第一交换设备配置第七流表, 以便 第二交换设备根据第六流表将业务报文转发至第一交换设备, 并由 第一交换设备根据第七流表将业务报文转发至所述其他交换设备。
参照图 9 所示, 提供一种在 OpenFlow协议控制设备、 交换设 备及客户端的所组成的网络架构, 其中客户端可以是用户使用的接 入设备, 如个人计算机 ( Personal Computer,PC ) , 手机, 平板电脑, 也可以泛指传输网络中与交换设备相连的上一级设备; 具体的控制 设备连接 4台交换设备, 其中交换设备 2连接客户端 1 , 交换设备 4 与客户端 2连接, 交换设备 3 连接交换设备 4 , 交换设备 1 连接交 换设备 4 ,交换设备 1 ,交换设备 2及交换设备 3之间存在链接关系, 即交换设备 1 与交换设备 2 连接, 交换设备 2 与交换设备 3连接, 同时交换设备 1 与交换设备 3连接分别与交换设备 4连接。 在该网 络架构下若出现交换设备之间的链路故障时, 按照上述实施例所述 的方法, 控制设备可以获取各个交换设备间的链路状态信息, 进而 实现对各个交换设备间的链路状态更新, 而当交换设备出过载后步 骤 504〜步骤 506的具体处理方法为:
a、控制设备根据各个交换设备发送的链路状态信息确认各个交 换设备间链路是否存在, 然后向各个交换设备发送状态信 , 请求 feature request 报文, 并接收各个交换设备发送的状态信息回复 feature reply报文,通过各个交换设备的状态信息统计各个交换设备 当前状态, 以便判断各个交换设备中是否存在过载的交换设备。
这里交换设备过载可以表现为较高的丟包率, 若此时控制设备 发现交换设备 1 的丟包率较高, 则通过控制设备上 LME查询 LMDB 获取交换设备 1 所在链路的配置属性, 发现在客户端 1 与客户端 2 之间存在另一条业务传输通道。
b、 若交换设备 1发生过载, 则控制设备对与交换设备 1相连的 交换设备 2配置对应交换设备 2的流表, 以便交换设备 2将客户端 1转发至交换设备 1 的业务报文由交换设备 2转发至交换设备 3。
c、 交换设备 3接收交换设备 2发送的业务报文, 由于匹配不到 对应的流表, 则通过 packet-in消息向控制设备请求对应交换设备 3 的流表, 控制设备接收交换设备 3 的数据转发请求后发送数据流修 复 flow-mod报文为交换设备 3配置对应的流表, 以便交换设备 3 能 够将业务报文转发至与交换设备 4相连的端口, 并由交换设备 4转 发至客户端 2。
这里控制设备为交换设备 2重新调配对端交换设备, 使得交换 设备 2接收客户端 1发送的业务报文经由交换设备 3转发, 再由交 换设备 3 将该业务报文转发至交换设备 4 , 最后由交换设备 4将业 务报文发送至客户端 2 ; 其中, 控制设备周期性的进行链路更新流 程, 以便检测交换设备间的链路状态是否正常。
d、 若控制设备的周期性的检测发现交换设备 1过载现象消除, 则将客户端 1 与客户端 2之间的传输路径切换至原有交换设备 1 所 在的传输路径上;具体过程为:控制设备向交换设备 2发送 flow-mod 报文, 修改交换设备 2 的流表, 将来自客户端 1 的业务报文转发至 交换设备 1 , 为交换设备 1 配置对应交换设备 1 的流表, 以便交换 设备 1 将接收到的业务报文转发至交换设备 4 , 并由交换设备 4 转 发至客户端 2。
本发明实施例提供的链路管理方法, 控制设备通过各个交换设 备发送的链路状态信息, 当交换设备发生过载时, 控制设备根据链 路状态信息及时灵活配置业务传输链路, 避免了客户端之间通信中 断的发生。 本发明实施例提供一种控制设备 6 , 该控制设备具体可以为软 件可定义 SDN 网络中执行 OpenFlow协议负责配置交换设备间数据 传输的电子设备, 在本发明的实施例中对控制设备的具体形式不做具体 限制, 以可以实现本发明的实施例所提供的上述任一链路管理方法为准, 具体参照图 10所示, 该控制设备包括: 接收单元 61和配置单元 62 , 其中,
接收单元 61 , 用于接收各个交换设备发送的链路状态信息; 配置单元 62 , 用于根据接收单元提供的链路状态信息为各个交 换设备配置业务数据传输链路。
本发明实施例提供的控制设备, 控制设备通过链路检测获得各 个交换设备间链路状态信息, 以便当交换设备间的链路故障发生时, 控制设备能够根据链路检测获得的链路状态信息及时处理链路故 障, 从而避免通讯中断发生。
可选的, 控制设备 6 , 参照图 10所示, 还包括: 发送单元 63 , 其中,
发送单元 63 , 用于向各个交换设备发送链路检测请求, 以便各 个交换设备根据链路检测请求进行邻近交换设备探测, 获取对端的 邻近交换设备端口信息后生成链路状态信息。
可选的, 参照图 1 1 所示, 发送单元 63 包括: 计时子单元 63 1 , 其中,
计时子单元 63 1 , 用于启动为各个交换设备分别设置的链路更 新定时器, 并当任一所述链路更新定时器超时后向所述任一链路更 新定时器对应的交换设备发送所述链路检测请求;
控制设备接收到所述各个交换设备发送的链路状态信息后还包 括:
计时子单元 63 1 , 还用于将所述各个交换设备分别对应的所述 链路更新定时器复位。
可选的, 控制设备 6 , 如图 12所示, 还包括: 判别单元 64 , 检测配置单元 65 , 其中,
判别单元 64 ,用于根据接收单元提供的链路状态信 , 判断各个 交换设备之间是否存在故障链路;
检测配置单元 65 , 用于若各个交换设备之间存在故障链路, 则 为故障链路两端的第一交换设备配置第一流表, 以便第一交换设备 根据第一流表将接收到的业务报文发送至与第一交换设备建立有正 常链路的第三交换设备;
接收单元 61 , 还用于接收第三交换设备的数据转发请求, 并根 据数据转发请求为第三交换设备配置对应业务报文转发的第二流 表, 以便第三交换设备根据第二流表将接收到的业务报文转发至其 他交换设备, 第二流表用于指示第三交换设备接收第二交换设备发 送的业务报文, 并将业务报文转发至其他交换设备处。
可选的, 检测配置单元 65 , 还用于若第一交换设备与第二交换 设备间的故障链路恢复正常, 则控制设备为第一交换设备配置第三 流表, 以便第一交换设备根据第三流表将业务报文发送至第二交换 设备。
本发明提供的控制设备, 控制设备通过各个交换设备发送的链 路状态信息, 当交换设备间链路发生故障时, 控制设备根据链路状 态信息及时灵活配置业务传输链路, 避免了客户端之间通信中断的 发生。
可选的, 控制设备 6 , 参照图 13 所示, 还包括: 检测单元 66 和配置查询单元 67 , 其中, 发送单元 63 ,还用于向各个交换设备发送交换设备状态信息请 求, 该交换设备状态信息请求用于获取各个交换设备的端口信息和 数据包统计信息;
接收单元 61 , 还用于接收各个交换设备发送的交换设备状态信 息;
检测单元 66 , 用于根据接收单元提供的各个交换设备的状态信 息判断各个交换设备中是否有交换设备发生过载;
配置查询单元 67 ,还用于若各个交换设备中第一交换设备发生 过载, 则对与第一交换设备连接的第二交换设备根据链路状态信息 配置第四流表, 以便第二交换设备根据第四流表将发送至第一交换 设备的业务报文转发至第三交换设备;
接收单元 61 , 还用于接收第三交换设备的数据转发请求, 并根 据数据转发请求为第三交换设备配置对应业务报文转发的第五流 表, 以便第三交换设备根据第五流表将接收到的业务报文转发至其 他交换设备, 第五流表用于指示第三交换设备接收第二交换设备发 送的业务报文, 并将业务报文转发至其他交换设备。
可选的, 配置查询单元 67 , 还用于若所述第一交换设备发生过 载的情况消除, 则所述控制设备为所述第二交换设备配置第六流表, 并为所述第一交换设备配置第七流表, 以便所述第二交换设备根据 所述第六流表将业务报文转发至所述第一交换设备, 并由所述第一 交换设备根据所述第七流表将所述业务报文转发至所述其他交换设 备。
可选的, 链路状态信息包括:
链路两端的交换设备的标识, 交换设备端口的编号, 交换设备 端口的多址接入信道 MAC地址和交换设备间链路的连接状态。
本发明实施例提供的控制设备, 控制设备通过各个交换设备发 送的链路状态信息, 当交换设备发送过载时, 控制设备根据链路状 态信息及时灵活配置业务传输链路, 避免了客户端之间通信中断的 发生。 本发明实施例提供一种交换设备 7 , 该交换设备具体可以为软 件可定义 SDN 网络中执行 OpenFlow协议负责转发数据传输的电子 设备, 可以为交换机, 路由器, 集线器等负责转发数据的电子设备, 在本发明的实施例中对交换设备的具体形式不做具体限制,以可以实现本 发明的实施例所提供的上述任一链路管理方法为准, 参照图 14 所示, 包括: 发送单元 71和转发单元 72 , 其中,
发送单元 71 , 用于向控制设备发送链路状态信息, 以便所述控 制设备根据所述链路状态信息为所述各个交换设备配置业务数据传 输链路;
转发单元 72 , 用于根据所述控制设备配置的业务数据传输链路 转发业务数据。
本发明实施例提供的交换设备, 控制设备通过链路检测获得各 个交换设备间链路状态信息, 以便当交换设备间的链路故障发生时, 控制设备能够根据链路检测获得的链路状态信息及时处理链路故 障, 从而避免通讯中断发生。
可选的, 交换设备 7 , 参照图 15 所示, 包括: 接收单元 73 和 检测单元 74 , 其中,
接收单元 73 , 用于接收控制设备发送的链路检测请求; 检测单元 74 , 用于根据链路检测请求进行邻近交换设备探测, 并在获取对端的邻近交换设备端口信息后生成链路状态信息。
可选的, 交换设备 7 , 参照图 16 所示, 还包括: 启动单元 75 和获取单元 76 , 其中,
启动单元 75 , 用于启动存活计时器;
获取单元 76 , 用于在存活计时器超时后进行邻近交换设备探 测, 获取对端的邻近交换设备端口信息后生成链路状态信息并对存 活计时器复位。
进一步的,参照图 17所示,获取单元 76包括:检测子单元 761 , 接收子单元 762和生成子单元 763 , 其中,
检测子单元 761 , 用于通过各个端口向邻近交换设备发送探测 报文;
接收子单元 762 , 用于接收邻近交换设备根据探测报文响应的 邻近交换设备端口信息;
生成子单元 763 , 用于根据换设备的端口信息及邻近交换设备 端口信息生成链路状态信息。
本发明实施例提供的交换设备, 控制设备通过链路检测获得各 个交换设备间链路状态信息, 以便当交换设备间的链路故障发生时, 控制设备能够根据链路检测获得的链路状态信息及时处理链路故 障, 从而避免通讯中断发生。 本发明实施例提供一种控制设备 8 , 该控制设备具体可以为 SDN网络中执行 OpenFlow协议负责配置交换设备间数据传输的电 子设备, 在本发明的实施例中对控制设备的具体形式不做具体限制, 以 可以实现本发明的实施例所提供的上述任一链路管理方法为准,参照图 1 8所示, 包括: 至少一个处理器 81、 存储器 82、 通信端口 83和总线 84 , 该至少一个处理器 81、 存储器 82和通信接口 83通过总线 84连接 并完成相互间的通信。
该总线 84可以是工业标准体系结构( Industry Standard Architecture , 简称为 ISA )总线、 外部设备互连( Peripheral Component, 简称为 PCI ) 总线或扩展工业标准体系结构( Extended Industry Standard Architecture , 简称为 EISA ) 总线等。 该总线 84可以分为地址总线、 数据总线、 控制 总线等。 为便于表示, 图 18 中仅用一条粗线表示, 但并不表示仅有一 根总线或一种类型的总线。 其中: 存储器 82 用于存储可执行程序代码, 该程序代码包括计算机操作 指令。 存储器 82可能包含高速 RAM存储器, 也可能还包括非易失性存 者器 ( non- volatile memory ), 例: ¾口至少一个磁盘存者器。 所述存 4诸设备 中存储: 操作系统、 应用程序, 用于实现本发明实施例的程序代码。 所 述操作系统用于控制和实现所述处理单元执行的处理功能。 所述应用程 序包含程序代码, 如字处理软件、 email软件。
处理器 81可能是一个中央处理器( Central Processing Unit, 简称为 CPU ), 或者是特定集成电路 ( Application Specific Integrated Circuit, 简 称为 ASIC ) , 或者是被配置成实施本发明实施例的一个或多个集成电 路。
通信接口 83 , 主要用于实现本实施例中的装置之间的通信。
其中, 处理器 81 , 用于通过至少一个通信接口接收各个交换设 备发送的链路状态信息;
处理器 8 1 ,还用于根据链路状态信息为各个交换设备配置业务 数据传输链路。
本发明实施例提供的控制设备, 控制设备通过链路检测获得各 个交换设备间链路状态信息, 以便当交换设备间的链路故障发生时, 控制设备能够根据链路检测获得的链路状态信息及时处理链路故 障, 从而避免通讯中断发生。
可选的, 处理器 81 通过至少一个通信接口接收各个交换设备 发送的链路状态信息之前,
处理器 8 1 ,还用于通过至少一个通信接口向各个交换设备发送 链路检测请求, 以便各个交换设备根据链路检测请求进行邻近交换 设备探测, 获取对端的邻近交换设备端口信息后生成链路状态信息。
可选的, 处理器 81 , 还用于启动为各个交换设备分别设置的链 路更新定时器, 并当任一链路更新定时器超时后向任一链路更新定 时器对应的交换设备发送链路检测请求;
处理器 8 1 通过至少一个通信接口接收到各个交换设备发送的 链路状态信息后,
处理器 81 , 还用于将各个交换设备分别对应的链路更新定时器 复位。
可选的, 处理器 81 , 还用于根据链路状态信息判断各个交换设 备之间是否存在故障链路; 若各个交换设备之间存在故障链路, 则 为故障链路一端的第一交换设备根据链路状态信息配置第一流表, 以便第一交换设备根据第一流表将接收到的业务报文发送至与第一 交换设备建立有正常链路的第三交换设备; 并通过至少一个通信接 口接收第三交换设备的数据转发请求, 并根据数据转发请求为第三 交换设备配置第二流表, 以便第三交换设备根据第二流表将接收到 的业务数据转发至故障链路另一端的第二交换设备, 第二流表用于 指示第三交换设备接收第一交换设备与第二交换设备之间故障链路 传输的业务数据, 并将业务数据通过第二交换设备与第三交换设备 连接的端口输出。
可选的, 处理器 81 , 还用于若第一交换设备与第二交换设备间 的故障链路恢复正常, 则控制设备为第一交换设备配置第三流表, 以便第一交换设备根据第三流表将业务报文发送至第二交换设备。
可选的, 处理器 81 , 还用于通过至少一个通信接口向各个交换 设备发送交换设备状态信息请求, 该交换设备状态信息请求用于获 取各个交换设备的端口信息和数据包统计信息; 并通过至少一个通 信接口接收各个交换设备发送的交换设备状态信息; 根据接收单元 提供的各个交换设备的状态信息判断各个交换设备中是否有交换设 备发生过载; 若各个交换设备中第一交换设备发生过载, 则对与第 一交换设备连接的第二交换设备根据链路状态信息配置第四流表, 以便第二交换设备根据第四流表将发送至第一交换设备的业务报文 转发至第三交换设备; 接收第三交换设备的数据转发请求, 并根据 数据转发请求为第三交换设备配置对应业务报文转发的第五流表, 以便第三交换设备根据第五流表将接收到的业务报文转发至其他交 换设备, 该第五流表用于指示第三交换设备接收第二交换设备发送 的业务报文, 并将业务报文转发至其他交换设备。
可选的, 处理器 81 , 还用于若第一交换设备发生过载的情况消 除, 则控制设备为第二交换设备配置第六流表, 并为第一交换设备 配置第七流表, 以便第二交换设备根据第六流表将业务报文转发至 第一交换设备, 并由第一交换设备根据第七流表将业务报文转发至 其他交换设备。
可选的, 链路状态信息包括:
链路两端的交换设备的标识, 交换设备端口的编号, 交换设备 端口的多址接入信道 MAC地址和交换设备间链路的连接状态。 本发明实施例提供的控制设备, 控制设备通过链路检测获得各 个交换设备间链路状态信息, 以便当交换设备间的链路故障发生时, 控制设备能够根据链路检测获得的链路状态信息及时处理链路故 障, 从而避免通讯中断发生。 本发明实施例提供一种交换设备 9 , 该交换设备具体可以为 SDN网络中执行 OpenFlow协议负责转发数据传输的电子设备, 可 以为交换机, 路由器, 集线器等负责转发数据的电子设备, 在本发 明的实施例中对交换设备的具体形式不做具体限制, 以可以实现本发明 的实施例所提供的上述任一链路管理方法为准, 参照图 19所示, 交换 设备 9 包括: 至少一个处理器 91、 存储器 92、 通信端口 93和总线 94 , 该至少一个处理器 91、 存储器 92和通信接口 93通过总线 94连接并完 成相互间的通信。 该总线 94可以是工业标准体系结构( Industry Standard Architecture , 简称为 ISA )总线、 外部设备互连( Peripheral Component, 简称为 PCI ) 总线或扩展工业标准体系结构( Extended Industry Standard Architecture , 简称为 EISA ) 总线等。 该总线 94可以分为地址总线、 数据总线、 控制 总线等。 为便于表示, 图 19 中仅用一条粗线表示, 但并不表示仅有一 根总线或一种类型的总线。 其中: 存储器 92 用于存储可执行程序代码, 该程序代码包括计算机操作 指令。 存储器 92可能包含高速 RAM存储器, 也可能还包括非易失性存 者器 ( non- volatile memory ), 例: ¾口至少一个磁盘存者器。 所述存 4诸设备 中存储: 操作系统、 应用程序, 用于实现本发明实施例的程序代码。 所 述操作系统用于控制和实现所述处理单元执行的处理功能。 所述应用程 序包含程序代码, 如字处理软件、 email软件。
处理器 91可能是一个中央处理器(Central Processing Unit, 简称为 CPU ), 或者是特定集成电路 ( Application Specific Integrated Circuit, 简 称为 ASIC ) , 或者是被配置成实施本发明实施例的一个或多个集成电 路。
通信接口 93 , 主要用于实现本实施例中的装置之间的通信。 其中, 处理器 91 , 用于通过至少一个通信接口向控制设备发送链路 状态信息, 以便控制设备根据链路状态信息为各个交换设备配置业务数 据传输链路;
处理器 91 ,还用于通过至少一个通信接口根据控制设备配置的业务 数据传输链路转发业务数据。
本发明实施例提供的交换设备, 控制设备通过链路检测获得各 个交换设备间链路状态信息, 以便当交换设备间的链路故障发生时, 控制设备能够根据链路检测获得的链路状态信息及时处理链路故 障。
可选的, 处理器 91 , 还用于通过至少一个通信接口接收控制设 备发送的链路检测请求; 并根据链路检测请求进行邻近交换设备探 测, 并在获取对端的邻近交换设备端口信息后生成链路状态信息。
可选的, 处理器 91 , 还用于启动存活计时器; 并在存活计时器 超时后进行邻近交换设备探测, 通过至少一个通信接口获取对端的 邻近交换设备端口信息后生成链路状态信息并对存活计时器复位。
进一步, 可选的, 处理器 91 , 还用于通过各个端口向邻近交换 设备发送探测报文; 并通过至少一个通信接口接收邻近交换设备根 据探测报文响应的邻近交换设备端口信息; 根据交换设备的端口信 息及邻近交换设备端口信息生成链路状态信息。
本发明实施例提供的交换设备, 控制设备通过链路检测获得各 个交换设备间链路状态信息, 以便当交换设备间的链路故障发生时, 控制设备能够根据链路检测获得的链路状态信息及时处理链路故 障, 从而避免通讯中断发生。
本发明提供一种通信系统 10 , 参照图 20所示, 包括: 控制设 备 1001和至少两个交换设备 1002 , 其中,
控制设备 1001 为图 9〜图 13 所示的任一控制设备, 交换设备 1002为图 14〜图 17所示的任一交换设备;
或者, 控制设备 1001 为图 1 8所示的控制设备, 交换设备 1002 为图 19所示的交换设备。
本发明实施例提供的通信系统, 控制设备通过链路检测获得各 个交换设备间链路状态信息, 以便当交换设备间的链路故障发生时, 控制设备能够根据链路检测获得的链路状态信息及时处理链路故 障, 从而避免通讯中断发生。
以上所述, 仅为本发明的具体实施方式, 但本发明的保护范围 并不局限于此, 任何熟悉本技术领域的技术人员在本发明揭露的技 术范围内, 可轻易想到变化或替换, 都应涵盖在本发明的保护范围 之内。 因此, 本发明的保护范围应所述以权利要求的保护范围为准。

Claims

权 利 要 求 书
1、 一种控制设备, 其特征在于, 包括: 通过数据总线连接的处 理器和存储器, 以及分别与所述处理器和存储器连接的至少一个通信 接口, 其中,
所述处理器, 用于通过所述至少一个通信接口接收各个交换设 备发送的链路状态信息;
所述处理器, 还用于根据所述链路状态信息为所述各个交换设 备配置业务数据传输链路。
2、 根据权利要求 1所述的设备, 其特征在于, 所述处理器通过 所述至少一个通信接口接收各个交换设备发送的链路状态信息之前, 所述处理器, 还用于通过所述至少一个通信接口向所述各个交 换设备发送链路检测请求, 以便所述各个交换设备根据所述链路检测 请求进行邻近交换设备探测, 获取对端的所述邻近交换设备端口信息 后生成所述链路状态信息。
3、 根据权利要求 2所述的设备, 其特征在于,
所述处理器, 还用于启动为所述各个交换设备分别设置的链路 更新定时器, 并当任一所述链路更新定时器超时后向所述任一链路更 新定时器对应的交换设备发送所述链路检测请求;
所述处理器通过所述至少一个通信接口接收到所述各个交换设 备发送的链路状态信息后,
所述处理器, 还用于将所述各个交换设备分别对应的所述链路 更新定时器复位。
4、 根据权利要求 1〜3任一项所述的设备, 其特征在于, 所述处理器, 还用于根据所述链路状态信息判断所述各个交换 设备之间是否存在故障链路; 若所述各个交换设备之间存在故障链 路, 则为所述故障链路一端的第一交换设备根据所述链路状态信息配 置第一流表, 以便所述第一交换设备根据所述第一流表将接收到的业 务报文发送至与所述第一交换设备建立有正常链路的第三交换设备; 并通过所述至少一个通信接口接收所述第三交换设备的数据转发请 求, 并根据所述数据转发请求为所述第三交换设备配置第二流表, 以 便所述第三交换设备根据所述第二流表将所述接收到的业务数据转 发至所述故障链路另一端的第二交换设备, 所述第二流表用于指示所 述第三交换设备接收所述第一交换设备与所述第二交换设备之间故 障链路传输的所述业务数据, 并将所述业务数据通过所述第二交换设 备与所述第三交换设备连接的端口输出。
5、 根据权利要求 4所述的设备, 其特征在于, 所述处理器, 还 用于若所述第一交换设备与所述第二交换设备间的所述故障链路恢 复正常, 则所述控制设备为所述第一交换设备配置第三流表, 以便所 述第一交换设备根据所述第三流表将业务报文发送至所述第二交换 设备。
6、 根据权利要求 1〜3任一项所述的设备, 其特征在于, 所述处理器, 还用于通过所述至少一个通信接口向所述各个交 换设备发送交换设备状态信息请求, 所述交换设备状态信息请求用于 获取所述各个交换设备的端口信息和所述数据包统计信息; 并通过所 述至少一个通信接口接收所述各个交换设备发送的交换设备状态信 息; 根据所述接收单元提供的所述各个交换设备的状态信息判断所述 各个交换设备中是否有交换设备发生过载; 若所述各个交换设备中第 一交换设备发生过载, 则对与所述第一交换设备连接的第二交换设备 根据所述链路状态信息配置第四流表, 以便所述第二交换设备根据所 述第四流表将发送至所述第一交换设备的业务报文转发至第三交换 设备; 接收所述第三交换设备的数据转发请求, 并根据所述数据转发 请求为所述第三交换设备配置对应所述业务报文转发的第五流表, 以 便所述第三交换设备根据所述第五流表将所述接收到的所述业务报 文转发至其他交换设备, 所述第五流表用于指示所述第三交换设备接 收所述第二交换设备发送的业务报文, 并将所述业务报文转发至所述 其他交换设备。
7、 根据权利要求 6所述的设备, 其特征在于, 所述处理器还用 于若所述第一交换设备发生过载的情况消除, 则所述控制设备为所述 第二交换设备配置第六流表, 并为所述第一交换设备配置第七流表, 以便所述第二交换设备根据所述第六流表将业务报文转发至所述第 一交换设备, 并由所述第一交换设备根据所述第七流表将所述业务报 文转发至所述其他交换设备。
8、 根据权利要求 1〜7任一项所述的设备, 其特征在于, 所述链 路状态信息包括:
链路两端的交换设备的标识, 所述交换设备端口的编号, 所述 交换设备端口的多址接入信道 MAC地址和所述交换设备间链路的连 接状态。
9、 一种交换设备, 其特征在于, 包括: 通过数据总线连接的处 理器和存储器, 以及分别与所述处理器和存储器连接的至少一个通信 接口, 其中,
所述处理器, 用于通过所述至少一个通信接口向控制设备发送 链路状态信息, 以便所述控制设备根据所述链路状态信息为所述各个 交换设备配置业务数据传输链路;
所述处理器, 还用于通过所述至少一个通信接口根据所述控制 设备配置的业务数据传输链路向与所述交换设备转发业务数据。
10、 根据权利要求 9所述的设备, 其特征在于,
所述处理器, 还用于通过所述至少一个通信接口接收所述控制 设备发送的链路检测请求; 并根据所述链路检测请求进行邻近交换设 备探测, 并在获取对端的所述邻近交换设备端口信息后生成所述链路 状态信息。
1 1、 根据权利要求 9所述的设备, 其特征在于,
所述处理器, 还用于启动存活计时器; 并在所述存活计时器超 时后进行邻近交换设备探测, 通过所述至少一个通信接口获取对端的 所述邻近交换设备端口信息后生成所述链路状态信息并对所述存活 计时器复位。
12、 根据权利要求 10或 1 1所述的设备, 其特征在于,
所述处理器, 还用于通过各个端口向所述邻近交换设备发送探 测报文; 并通过所述至少一个通信接口接收所述邻近交换设备根据所 述探测报文响应的所述邻近交换设备端口信息; 根据所述交换设备的 端口信息及所述邻近交换设备端口信息生成所述链路状态信息。
13、 一种链路管理方法, 其特征在于, 包括:
控制设备接收各个交换设备发送的链路状态信息;
所述控制设备根据所述链路状态信息为所述各个交换设备配置 业务数据传输链路。
14、 根据权利要求 13所述的方法, 其特征在于, 所述控制设备 接收各个交换设备发送的链路状态信息之前, 还包括:
所述控制设备向所述各个交换设备发送链路检测请求, 以便所 述各个交换设备根据所述链路检测请求进行邻近交换设备探测, 获取 对端的所述邻近交换设备端口信息后生成所述链路状态信息。
15、 根据权利要求 14所述的方法, 其特征在于, 所述方法还包 括:
所述控制设备启动为所述各个交换设备分别设置链路更新定时 器, 并当任一所述链路更新定时器超时后向所述任一链路更新定时器 对应的交换设备发送所述链路检测请求;
所述控制设备接收到所述各个交换设备发送的链路状态信息后 还包括:
将所述各个交换设备分别对应的所述链路更新定时器复位。
16、 根据权利要求 13〜15 任一项所述的方法, 其特征在于, 所 述控制设备接收各个交换设备发送的链路状态信息后, 还包括:
根据所述链路状态信息判断所述各个交换设备之间是否存在故 障链路;
若所述各个交换设备之间存在故障链路, 则为所述故障链路一 端的第一交换设备根据所述链路状态信息配置第一流表, 以便所述第 一交换设备根据所述第一流表将接收到的业务报文发送至与所述第 一交换设备建立有正常链路的第三交换设备;
接收所述第三交换设备的数据转发请求, 并根据所述数据转发 请求为所述第三交换设备配置第二流表, 以便所述第三交换设备根据 所述第二流表将所述接收到的业务报文转发至所述故障链路另一端 的第二交换设备, 所述第二流表用于指示所述第三交换设备接收所述 第一交换设备与所述第二交换设备之间故障链路传输的所述业务报 文, 并将所述业务报文通过所述第二交换设备与所述第三交换设备连 接的端口输出。
17、 根据权利要求 16所述的方法, 其特征在于, 所述方法还包 括:
若所述第一交换设备与所述第二交换设备间的所述故障链路恢 复正常, 则所述控制设备为所述第一交换设备配置第三流表, 以便所 述第一交换设备根据所述第三流表将业务报文发送至所述第二交换 设备。
1 8、 根据权利要求 13〜15 任一项所述的方法, 其特征在于, 所 述方法还包括:
所述控制设备向所述各个交换设备发送交换设备状态信息请 求, 所述交换设备状态信息请求用于获取所述各个交换设备的端口信 息和所述数据包统计信息;
所述控制设备接收所述各个交换设备发送的交换设备状态信 息, 并根据所述各个交换设备的状态信息判断所述各个交换设备中是 否有交换设备发生过载;
若所述各个交换设备中第一交换设备发生过载, 则对与所述第 一交换设备连接的第二交换设备根据所述链路状态信息配置第四流 表, 以便所述第二交换设备根据所述第四流表将发送至所述第一交换 设备的业务报文转发至第三交换设备;
接收所述第三交换设备的数据转发请求, 并根据数据转发请求 为所述第三交换设备配置对应所述业务报文转发的第五流表, 以便所 述第三交换设备根据所述第五流表将所述接收到的所述业务报文转 发至其他交换设备, 所述第五流表用于指示所述第三交换设备接收所 述第二交换设备发送的业务报文, 并将所述业务报文转发至所述其他 交换设备。
19、 根据权利要求 1 8所述的方法, 其特征在于, 所述方法还包 括:
若所述第一交换设备发生过载的情况消除, 则所述控制设备为 所述第二交换设备配置第六流表, 并为所述第一交换设备配置第七流 表, 以便所述第二交换设备根据所述第六流表将业务报文转发至所述 第一交换设备, 并由所述第一交换设备根据所述第七流表将所述业务 报文转发至所述其他交换设备。
20、 根据权利要求 13〜19任一项所述的方法, 其特征在于, 所 述链路状态信息包括:
链路两端的交换设备的标识, 所述交换设备端口的编号, 所述 交换设备端口的多址接入信道 MAC地址和所述交换设备间链路的连 接状态。
21、 一种链路管理方法, 其特征在于, 包括:
交换设备向控制设备发送链路状态信息, 以便所述控制设备根 据所述链路状态信息为所述各个交换设备配置业务数据传输链路; 所述交换设备根据所述控制设备配置的业务数据传输链路转发 业务数据。
22、 根据权利要求 21所述的方法, 其特征在于, 所述交换设备 向控制设备发送链路状态信息前, 还包括:
所述交换设备接收所述控制设备发送的链路检测请求; 所述交换设备根据所述链路检测请求进行邻近交换设备探测, 获取对端的所述邻近交换设备端口信息后生成所述链路状态信息。
23、 根据权利要求 21所述的方法, 其特征在于, 所述交换设备 向控制设备发送链路状态信息前, 还包括:
所述交换设备启动存活计时器;
所述交换设备在所述存活计时器超时后进行邻近交换设备探 测, 获取对端的所述邻近交换设备端口信息后生成所述链路状态信息 并对所述存活计时器复位。
24、 根据权利要求 22或 23 所述的方法, 其特征在于, 所述根 据所述链路检测请求进行邻近交换设备探测, 获取对端的所述邻近交 换设备端口信息后生成所述链路状态信息, 包括:
所述交换设备通过各个端口向所述邻近交换设备发送探测报 文;
所述交换设备接收所述邻近交换设备根据所述探测报文响应的 所述邻近交换设备端口信息;
根据所述交换设备的端口信息及所述邻近交换设备端口信息生 成所述链路状态信息。
25、 一种通信系统, 其特征在于, 包括: 控制设备和至少两个 交换设备, 其中,
所述控制设备为权利要求 1〜8 所述的任一控制设备, 所述交换 设备为权利要求 9〜12所述的任一交换设备。
PCT/CN2013/070945 2013-01-24 2013-01-24 一种链路管理方法、设备和通信系统 WO2014113957A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201380000151.0A CN104081743A (zh) 2013-01-24 2013-01-24 一种链路管理方法、设备和通信系统
PCT/CN2013/070945 WO2014113957A1 (zh) 2013-01-24 2013-01-24 一种链路管理方法、设备和通信系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/070945 WO2014113957A1 (zh) 2013-01-24 2013-01-24 一种链路管理方法、设备和通信系统

Publications (1)

Publication Number Publication Date
WO2014113957A1 true WO2014113957A1 (zh) 2014-07-31

Family

ID=51226837

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/070945 WO2014113957A1 (zh) 2013-01-24 2013-01-24 一种链路管理方法、设备和通信系统

Country Status (2)

Country Link
CN (1) CN104081743A (zh)
WO (1) WO2014113957A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150193316A1 (en) * 2014-01-06 2015-07-09 International Business Machines Corporation Bus interface optimization by selecting bit-lanes having best performance margins
CN115348153A (zh) * 2022-08-15 2022-11-15 中国联合网络通信集团有限公司 转发设备的控制方法、装置、设备及存储介质
WO2023134416A1 (zh) * 2022-01-14 2023-07-20 华为技术有限公司 一种报文发送方法、确定链路状态的方法、设备及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112422428B (zh) * 2020-11-09 2022-05-17 迈普通信技术股份有限公司 链路状态获取方法、装置、电子设备及可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1655556A (zh) * 2005-03-18 2005-08-17 大连理工大学 一种基于动态聚合树模型的路由方法
CN101841464A (zh) * 2010-03-08 2010-09-22 北京网康科技有限公司 一种网络负载均衡设备及其实现方法
CN102394787A (zh) * 2011-12-14 2012-03-28 重庆邮电大学 基于epa交换机的双链路冗余控制方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1655556A (zh) * 2005-03-18 2005-08-17 大连理工大学 一种基于动态聚合树模型的路由方法
CN101841464A (zh) * 2010-03-08 2010-09-22 北京网康科技有限公司 一种网络负载均衡设备及其实现方法
CN102394787A (zh) * 2011-12-14 2012-03-28 重庆邮电大学 基于epa交换机的双链路冗余控制方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150193316A1 (en) * 2014-01-06 2015-07-09 International Business Machines Corporation Bus interface optimization by selecting bit-lanes having best performance margins
US9459982B2 (en) * 2014-01-06 2016-10-04 International Business Machines Corporation Bus interface optimization by selecting bit-lanes having best performance margins
WO2023134416A1 (zh) * 2022-01-14 2023-07-20 华为技术有限公司 一种报文发送方法、确定链路状态的方法、设备及系统
CN115348153A (zh) * 2022-08-15 2022-11-15 中国联合网络通信集团有限公司 转发设备的控制方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN104081743A (zh) 2014-10-01

Similar Documents

Publication Publication Date Title
EP2985952B1 (en) Method and device for protecting service reliability, and network virtualization system
Song et al. Control path management framework for enhancing software-defined network (SDN) reliability
US10965546B2 (en) Control of network nodes in computer network systems
US9270524B2 (en) Method and device for LACP link switching and data transmission
CN107070689B (zh) 减少使用网络保活消息时的错误警告的方法及装置
WO2013115177A1 (ja) ネットワークシステム、及びトポロジー管理方法
WO2016165463A1 (zh) 一种基于软件定义网络的链路故障上报方法和转发设备
WO2015000362A1 (zh) 一种业务节点配置方法、业务节点池注册器及系统
CN103001887A (zh) 一种链路保活方法、控制器及交换机
JP2006229967A (ja) 高速マルチキャスト・パス切り替え
CN102195857A (zh) 一种网络拓扑结构与节点信息搜集方法
WO2012068996A1 (zh) 链路状态检测方法和装置
EP2922254A1 (en) Method for establishing control channel, forwarding point and controller
KR20140106235A (ko) 오픈플로우 스위치 및 그 패킷 처리 방법
WO2012088910A1 (zh) 连通性故障检测方法和系统
CN107645394B (zh) 一种sdn网络中的交换机配置方法
WO2017157318A1 (zh) 链路发现方法及装置
WO2014113957A1 (zh) 一种链路管理方法、设备和通信系统
CN105530115A (zh) 一种实现操作管理维护功能的方法及装置
WO2015192306A1 (zh) 软件定义网络中的控制设备、系统和传输通道控制方法
JP4532253B2 (ja) フレーム転送装置及びフレームのループ抑止方法
JP6221716B2 (ja) 通信システム及びネットワーク装置
EP2874349B1 (en) Communication path processing method and apparatus
KR20180122513A (ko) Sdn 기반 네트워크 가상화 플랫폼의 네트워크 하이퍼바이저에서 트래픽 엔지니어링 방법 및 프레임워크
CN112910704B (zh) 一种支持动态自适应网络配置的局域网系统、方法和装置

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

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

Country of ref document: EP

Kind code of ref document: A1