WO2022267938A1 - 故障处理方法、堆叠设备及存储介质 - Google Patents

故障处理方法、堆叠设备及存储介质 Download PDF

Info

Publication number
WO2022267938A1
WO2022267938A1 PCT/CN2022/098777 CN2022098777W WO2022267938A1 WO 2022267938 A1 WO2022267938 A1 WO 2022267938A1 CN 2022098777 W CN2022098777 W CN 2022098777W WO 2022267938 A1 WO2022267938 A1 WO 2022267938A1
Authority
WO
WIPO (PCT)
Prior art keywords
stack
port
stack port
state
stacking
Prior art date
Application number
PCT/CN2022/098777
Other languages
English (en)
French (fr)
Inventor
林宁
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2022267938A1 publication Critical patent/WO2022267938A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/10—Packet switching elements characterised by the switching fabric construction
    • H04L49/111—Switch interfaces, e.g. port details
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/30—Peripheral units, e.g. input or output ports
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Definitions

  • the embodiments of the present application relate to the communication field, and in particular to a fault handling method, a stacking device, and a storage medium.
  • a stack port of a switch stack system is a bridge between stack devices in the switch stack system.
  • the stacking port selected by the stacking system generally requires high reliability. If the stacking port of the stacking system fails, the inter-device traffic of the entire stacking system will be seriously affected, thereby affecting the reliability and stability of the network. To ensure the reliability of stack ports, generally, multiple stack ports are bundled into an aggregation group. If a stack port fails, other stack ports can maintain the normal operation of the stack system.
  • Link aggregation control protocol Link Aggregation Control Protocol, LACP
  • LACP Link Aggregation Control Protocol
  • the embodiment of the present application provides a fault handling method, which is applied to a stacking device, including: if it is determined that a stacking port fails, setting the spanning tree state of the stacking port to a blocked state; judging whether the stacking port returns to normal; The tree state is set to forwarding state.
  • An embodiment of the present application provides a stacking device, including: a first judging module, a second judging module, and a processing module; the first judging module is used to judge whether a stack port fails; The spanning tree state of the stacking port is set to a blocking state; the second judging module is used to judge whether the stacking port is back to normal; the processing module is also used to set the spanning tree state of the stacking port to a forwarding state if it is determined that the stacking port is back to normal.
  • An embodiment of the present application provides a stacking device, including: at least one processor; and a memory connected to the at least one processor in communication; wherein, the memory stores instructions that can be executed by at least one processor, and the instructions are processed by at least one executed by a processor, so that at least one processor can execute the fault handling method mentioned in the foregoing implementation manner.
  • An embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, implements the fault handling method mentioned in the foregoing implementation manner.
  • Fig. 1 is the flowchart of the fault processing method in the embodiment of the present application.
  • Fig. 2 is a schematic diagram of another fault handling method in the embodiment of the present application.
  • Fig. 3 is a schematic diagram of another fault handling method in the embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of the stacking system when all stacking ports of the stacking system communicate normally in the embodiment of the present application;
  • Fig. 5 is a schematic structural diagram of a stacking system when a communication abnormal state occurs between port A2 and port B2 in the embodiment of the present application;
  • FIG. 6 is a schematic structural diagram of a stacking device in an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a stacking device in an embodiment of the present application.
  • the fault handling method shown in FIG. 1 is executed by a stacking device in a stacking system, such as a switch, and includes the following steps.
  • Step 101 If it is determined that the stack port is faulty, set the spanning tree state of the stack port to a blocking state.
  • Step 102 If it is determined that the stack port returns to normal, set the spanning tree state of the stack port to the forwarding state.
  • the stacking device sets the spanning tree state of the stacking port to a blocked (block) state when the stacking port fails.
  • the spanning tree state of a stack port is blocked, the stack port is not removed from the link bundle, but the stack port no longer forwards service forwarding packets.
  • the stack system will automatically select other stack ports whose spanning tree status is forwarding. Since the failed stack port has not been removed from the link bundle, after the failed stack port returns to normal, set the spanning tree state of the stack port to forward (forward) state, so that the stack port can start forwarding Packets are forwarded by the service, and the normal communication of the stack link where the stack port is located is restored.
  • forward forward
  • the step of setting the spanning tree state of the stack port to the blocking state if it is determined that the stack port fails it further includes: judging whether the stack port has received a heartbeat message or a response sent by the peer device If it is determined that no heartbeat message or response message is received, it is determined that the stack port is faulty.
  • the stack device and the peer device detect faults by exchanging heartbeat packets.
  • One of the stack device and the peer device (hereinafter referred to as the sender) sends a heartbeat message to the other party (hereinafter referred to as the receiver). If the communication between the two is normal, the receiver sends a response after receiving the heartbeat message. message to the sender. After receiving the heartbeat message, the receiver determines that the stack port of the receiver is normal. After receiving the response packet, the sender determines that the stack port of the sender is normal. If the communication between the two is abnormal, the receiver cannot receive the heartbeat message, nor can it send a response message to the sender. The receiver does not receive the heartbeat packet, and it is determined that the stack port of the receiver is faulty. The sender does not receive the response packet, and it is determined that the stack port of the sender is faulty.
  • judging whether the stack port is faulty includes: judging whether the stack port has received the response message sent by the peer device; file to determine that the stack port is faulty. If the stack device is the receiver and the peer device is the sender, determine whether the stack port is faulty, including: judging whether the stack port has received the heartbeat message sent by the peer device; if it is determined that the heartbeat message has not been received, determine the stack port error occured.
  • heartbeat packets are used to determine whether a stack port is faulty, so that when a stack port on either side of the stack system fails, the faulty stack port corresponds to the faulty stack port on the other side of the stack system. All stack ports can be discovered, and their spanning tree status is set to block status in time. Since the spanning tree status of the faulty stack port on both sides of the stack system is set to block state, the stack system can bypass the faulty stack port when sending service forwarding packets, and avoid removing only one side of the stack. A situation where a port causes a large amount of packet loss. In addition, since faults are detected by exchanging heartbeat messages between the stacking device and the peer device, the sending frequency of heartbeat messages can reach millisecond level. Compared with the dynamic link bundling method that detects stack system abnormalities through second-level LACP packets, it detects stack system faults faster, reduces a large number of packet loss situations, and reduces the time consumed by stack system recovery.
  • the fault handling method further includes: determining that the time period for which the heartbeat message or the response message is not received is longer than a preset time period.
  • the stacking device does not receive a heartbeat packet or response packet for a preset period of time, it sets the spanning tree state of the stack port to the block state, which can reduce the need to set the non-faulty stack port to block state due to the transmission of individual heartbeat packets.
  • the block state causes the resources of the stack port to be wasted.
  • the preset duration can be determined according to the sending frequency of the heartbeat message between the stacking device and the peer device. For example, if the sending frequency of the heartbeat message is X milliseconds/time, the preset duration The duration can be set to aX milliseconds; wherein, a is a positive integer. This embodiment does not limit the specific value of the preset duration.
  • preset duration set by the stacking device and the preset duration set by the peer device may be the same or different, which is not limited in this embodiment.
  • the stack port before setting the spanning tree state of the stack port to the forwarding state if it is determined that the stack port returns to normal, it further includes: judging whether the stack port has received a heartbeat message or a response sent by the peer device message; if it is determined that a heartbeat message or a response message is received, it is determined that the stack port returns to normal.
  • the sender in the stack system continues to send heartbeat packets to the stack port set as block. Because the stacking system sets the block state for the faulty stack port, when the spanning tree state of the stack port is in the block state, the service forwarding packets through the stack port are blocked, but the heartbeat packets are not blocked. Therefore, the sender of the stack system It will not fail to send heartbeat packets because the stack port is set to block state. If the failure of the stack port is not rectified, the receiver still cannot receive the heartbeat message, and the sender cannot get the receiver's response message. Therefore, when the stack port failure persists, the stack ports of the sender and receiver of the stack system continue to maintain the spanning tree state as block.
  • the receiver can receive the heartbeat message sent by the sender and send a response message to the sender. After receiving the heartbeat message, the receiver can set the spanning tree state of the stack port that has received the heartbeat message to the forward state. The sender can also receive the heartbeat message of the receiver's response. After receiving the response message responded by the receiver, the sender can set the spanning tree state of its own stack port that has received the response message to the forward state. The spanning tree status of the stack ports on both sides of the stack system is set to the forward state, and the stack port of the stack system automatically returns to the normal state.
  • judging whether the stack port is back to normal includes: judging whether the stack port has received the response message sent by the peer device; , and make sure that the stack port returns to normal. If the stack device is the receiver and the peer device is the sender, judge whether the stack port is back to normal, including: judging whether the stack port has received the heartbeat message sent by the peer device; normal.
  • the fault handling method further includes: determining that the number of times the heartbeat message or the response message has been received continuously is greater than a preset number of times.
  • the stacking device sets the spanning tree state of the stacking port to the forward state after continuously receiving the preset number of heartbeat packets or response packets. A condition in which the spanning tree state causes a system panic.
  • the preset number of times can be determined according to the number of stacking devices in the stacking system, for example, the preset number of times can be set to 2, or other positive integers greater than 1. This embodiment does not limit the specific value of the preset times.
  • the preset times set by the stacking device and the preset times set by the peer device may be the same or different, which is not limited in this embodiment.
  • the heartbeat message carries the authentication information of the peer device, or the response message carries the authentication information in the heartbeat message sent by the stacking device.
  • the stack device carries the authentication information of the stack device in the heartbeat message when sending the heartbeat message. After receiving the heartbeat message, the peer device feeds back a response message to the stack device, and the response message carries the authentication information in the heartbeat message of the stack device. If the stack device is the receiver and the peer device is the sender, the peer device carries the authentication information of the peer device in the heartbeat message when it sends the heartbeat message. After receiving the heartbeat message, the stacking device feeds back a response message to the peer device, and the response message carries the authentication information in the heartbeat message of the peer device.
  • the authentication information includes a serial number and/or a time stamp.
  • the serial number is the serial number of the stacking device
  • the time stamp is the time stamp of the stacking device.
  • the serial number is the serial number of the peer device
  • the timestamp is the timestamp of the peer device.
  • the authentication information may also be other unique authentication information of the stacking device or the peer device, and this embodiment does not serve as a limitation.
  • the fault handling method performed by the stacking device includes the following steps.
  • Step 201 Periodically send heartbeat messages to the stack port of the peer device.
  • the stacking device periodically sends a heartbeat message to the peer device through its own stacking port.
  • the heartbeat message may include authentication information of the stack device.
  • Step 202 Determine whether its own stack port has received the response message sent by the peer device.
  • the peer device can receive the heartbeat message. After receiving the heartbeat message, the peer device sends a response message to the stack port of the stack device through the stack port of the peer device. If the stack port of the stack device or the stack port of the peer device fails, the communication is abnormal, and the peer device cannot receive heartbeat packets. The peer device cannot send response packets to the stack port of the stack device. Therefore, if the own stack port receives the response message, it means that neither the stack port of the stack device nor the stack port of the peer device is faulty, and the spanning tree state of the stack port of the stack device is not changed, and step 202 is continued. If the stacking port of itself does not receive a response message, it means that the stacking port of the stacking device or the stacking port of the peer device is faulty, and step 203 is performed.
  • the response message carries the authentication information in the heartbeat message.
  • Step 203 Determine that the stack port is faulty.
  • Step 204 Set the spanning tree state of the stack port to a blocking state.
  • the peer device cannot receive the heartbeat message, the peer device determines that the stack port of the peer device is faulty, and the spanning tree state of the stack port of the peer device is set to a blocking state.
  • Step 205 Periodically send heartbeat messages to the stack port of the peer device.
  • Step 206 Judging whether its own stack port has received the response message sent by the peer device.
  • the stack device still cannot receive the response message; if the fault of the stack port of the stack device or the stack port of the peer device is eliminated, the communication is normal , the peer device can receive the heartbeat message. After receiving the heartbeat message, the peer device sends a response message to the stack port of the stack device through the stack port of the peer device. Therefore, if the own stack port receives the response message, it means that the failure of the stack port of the stack device or the stack port of the peer device has been eliminated, and the spanning tree state of the stack port of the stack device is changed, and step 207 is executed. If the self-stacking port does not receive the response message, it means that the fault of the stacking port of the stacking device or the stacking port of the peer device has not been eliminated, and proceed to step 206 .
  • Step 207 Determine that the stack port returns to normal.
  • Step 208 Set the spanning tree state of the stack port to the forwarding state.
  • step 201 After setting the spanning tree state of the stack port to the forwarding state, return to step 201 .
  • the peer device determines that the fault of the stack port of the peer device is eliminated and returns to normal, and the spanning tree state of the stack port of the peer device is set to the forwarding state.
  • the fault handling method performed by the stacking device includes the following steps.
  • Step 301 Judging whether its own stack port has received a heartbeat message sent by the peer device.
  • the peer device periodically sends heartbeat packets to the stack device through the stack port of the peer device. If neither the stacking port of the stacking device nor the stacking port of the peer device is faulty, the communication is normal, and the stacking device can receive heartbeat packets. If the stacking port of the stacking device or the stacking port of the peer device fails, communication is abnormal, and the stacking device cannot receive heartbeat packets. Therefore, if the stacking port of the stacking device receives the heartbeat message, it means that neither the stacking port of the stacking device nor the stacking port of the peer device is faulty, and the spanning tree status of the stacking port of the stacking device is not changed, and step 301 is continued. If the stacking port of the stacking device does not receive the heartbeat message, it means that the stacking port of the stacking device or the stacking port of the peer device is faulty, and step 302 is performed.
  • the response message carries the authentication information in the heartbeat message.
  • Step 302 Determine that the stack port is faulty.
  • Step 303 Set the spanning tree state of the stack port to a blocking state.
  • the peer device cannot receive the response message, the peer device determines that the stack port of the peer device is faulty, and the spanning tree state of the stack port of the peer device is set to a blocking state. After the stack port of the peer device is set to the blocked state, it continues to periodically send heartbeat packets to the stack device.
  • Step 304 Judging whether its own stack port has received the heartbeat message sent by the peer device.
  • the stack device still cannot receive heartbeat packets; , the stack device can receive heartbeat packets. Therefore, if the own stack port receives the heartbeat message, it means that the failure of the stack port of the stack device or the stack port of the peer device has been eliminated, and the spanning tree state of the stack port of the stack device is changed, and step 305 is executed. If the stacking port of itself does not receive the heartbeat message, it means that the fault of the stacking port of the stacking device or the stacking port of the peer device has not been eliminated, and proceeds to step 304 .
  • Step 305 Determine that the stack port returns to normal.
  • Step 306 Set the spanning tree state of the stack port to the forwarding state.
  • step 301 After the spanning tree state of the stack port is set to the forwarding state, return to step 301 .
  • the peer device determines that the fault of the stack port of the peer device is eliminated and returns to normal, and the spanning tree state of the stack port of the peer device is set to the forwarding state.
  • the fault handling method mentioned in this embodiment is described below by taking the stacking device and the peer device as switches as examples.
  • a stack system includes a switch A401 and a switch B402, and the switch A401 is a stack master device.
  • Switch A401 uses port A1 as a stack port to connect to port B1 of switch B402, and switch A401 uses port A2 as a stack port to connect to port B2 of the switch, so that switch A401 and switch B402 perform stack communication.
  • the switch A401 is a stacking device, and the switch B402 is a peer device, or, the switch A401 is a peer device, and the switch B402 is a stacking device.
  • the sending period of the heartbeat message is 50 milliseconds, the preset duration is 150 milliseconds, the preset number of times is 2, and the authentication information is timestamp information.
  • FIG. 4 If the stack ports of the stack system communicate normally, the structural diagram of the stack system is shown in Figure 4. Port A1 of switch A401 communicates with port B1 of switch B402, and port A2 of switch A401 communicates with port B2 of switch B402. Heartbeat packets are exchanged between switch A401 and switch B402.
  • FIG. 5 a schematic structural diagram of the stacking system is shown in FIG. 5 .
  • the switch A401 sends a heartbeat message to the switch B402 every 50 ms, and the heartbeat message carries the time stamp information of the switch A401. Due to abnormal communication between the port A2 of the switch A401 and the port B2 of the switch B402, the port B2 of the switch B402 cannot receive the heartbeat message of the switch A401. If the port B2 of the switch B402 does not receive the heartbeat message of the switch A401 within 3 cycles (150 milliseconds), set the spanning tree state of the port B2 of the switch B402 to block state.
  • the switch A401 does not receive the response message of the time stamp information of the A device carried by the switch B402 on the port A2 within 3 cycles (150 milliseconds), and immediately sets the spanning tree state of the port A2 port of the switch A401 to the block state.
  • the spanning tree states of port A2 of switch A401 and port B2 of switch B402 are all set to block state. These two stack ports will no longer forward service packets, and the stack system formed by switch A401 and switch B402 will forward service packets across stacked devices through the remaining connection line between port A1 and port B1.
  • the switch A401 continues to send a heartbeat message every 50 ms to the port A2 that has been set in the block state.
  • the spanning tree state of port A2 of switch A401 and port B2 of switch B402 is set to block state, the block state does not affect the forwarding of heartbeat packets, so the action of switch A401 sending heartbeat packets to port A2 is not affected. If the abnormal fault state between port A2 and port B2 is not eliminated, port B2 of switch B402 cannot receive a heartbeat message, and port A2 of switch A401 cannot receive a response message from switch B402. Therefore, during the failure continuation phase, the spanning tree states of port A2 of switch A401 and port B2 of switch B402 continue to be in block state.
  • the switch B402 can receive the heartbeat message of the switch A401 at the port B2 immediately, and Reply the response message from port B2 to switch A401.
  • Switch A401 receives a response message with correct time stamp information from switch B402 at port A2.
  • the switch B402 sends the response message to the switch A401, waits for 50ms, and receives a heartbeat message from the switch A401 at the port B2, then the switch B402 sets the spanning tree state of the port B2 to the forward state.
  • Switch A401 can set the spanning tree state of port A2 to forward state after receiving the response message with correct time stamp information sent by switch B402 from port A2. So far, the spanning tree states of port A2 of switch A401 and port B2 of switch B402 are both set to the forward state, and the link between port A2 and port B2 of the stack system formed by switch A401 and switch B402 automatically returns to normal state.
  • the fault handling method mentioned in this embodiment can quickly detect the status of abnormal link
  • the setting of the spanning tree state will not affect the sending process of the heartbeat message. Therefore, the stack system can still send the heartbeat message normally, but the heartbeat message will not be sent by the stack system when the stack port is abnormal. Received by the receiving side.
  • the heartbeat packets will immediately resume sending and receiving normally, and both sides of the stack system will automatically set the tree formation status of the stack ports that have been rectified to forward according to the receiving status of the heartbeat packets, so as to recover This stack port works normally in the stack system.
  • the stacking system can quickly eliminate the abnormal stacking port so that it will no longer have a serious impact on the stacking system, and can quickly restore the fault without human intervention when the fault is restored. Indicates the normal working status of a stack port in a stack system. Therefore, adopting the fault handling method mentioned in this embodiment can greatly enhance the stacking system's automatic troubleshooting and automatic recovery processing of stack port link faults, and effectively enhance the reliability, maintainability and stability of network devices.
  • step division of the above various methods is only for the sake of clarity of description. During implementation, it can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. ; Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but not changing the core design of the algorithm and process are all within the scope of protection of this patent.
  • the embodiment of the present application also provides a stacking device, as shown in FIG. 6 , including: a first judging module 601 , a second judging module 602 and a processing module 603 .
  • the first judging module 601 is used to judge whether the stacking port fails;
  • the processing module 603 is used to set the spanning tree state of the stacking port to a blocking state if it is determined that the stacking port is faulty;
  • the second judging module 602 is used to judge whether the stacking port is restored Normal;
  • the processing module 603 is further configured to set the spanning tree state of the stack port to the forwarding state if it is determined that the stack port returns to normal.
  • this embodiment is a device implementation manner corresponding to the above-mentioned method embodiment, and this embodiment can be implemented in cooperation with the above-mentioned method embodiment.
  • the relevant technical details mentioned in the foregoing method embodiments are still valid in this embodiment, and will not be repeated here in order to reduce repetition.
  • the relevant technical details mentioned in this embodiment can also be applied to the above method embodiments.
  • modules involved in this embodiment are logical modules.
  • a logical unit can be a physical unit, or a part of a physical unit, or multiple physical units. Combination of units.
  • units that are not closely related to solving the technical problem proposed in the present application are not introduced in this embodiment, but this does not mean that there are no other units in this embodiment.
  • the embodiment of the present application also provides a stacking device, as shown in FIG. 7 , including: at least one processor 701; and a memory 702 communicated with at least one processor 701; Instructions to be executed, the instructions are executed by at least one processor 701, so that at least one processor 701 can execute the foregoing method embodiments.
  • the memory 702 and the processor 701 are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors 701 and various circuits of the memory 702 together.
  • the bus may also connect together various other circuits such as peripherals, voltage regulators, and power management circuits, all of which are well known in the art and therefore will not be further described herein.
  • the bus interface provides an interface between the bus and the transceivers.
  • a transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing means for communicating with various other devices over a transmission medium.
  • the data processed by the processor 701 is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 701 .
  • the processor 701 is responsible for managing the bus and general processing, and may also provide various functions including timing, peripheral interface, voltage regulation, power management and other control functions. And the memory 702 may be used to store data used by the processor 701 when performing operations.
  • the embodiment of the present application also provides a computer-readable storage medium storing a computer program.
  • the above method embodiments are implemented when the computer program is executed by the processor.
  • the program is stored in a storage medium, and includes several instructions to make a device ( It may be a single-chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc., which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

一种故障处理方法、堆叠设备及存储介质。故障处理方法应用于堆叠设备，包括：若确定堆叠端口出现故障，将堆叠端口的生成树状态设置为阻塞状态；若确定堆叠端口恢复正常，将堆叠端口的生成树状态设置为转发状态。

Description

故障处理方法、堆叠设备及存储介质
交叉引用
本申请基于申请号为“202110686363.5”、申请日为2021年06月21日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请实施例涉及通信领域，特别涉及一种故障处理方法、堆叠设备及存储介质。
背景技术
一般情况下，交换机堆叠系统的堆叠端口是交换机堆叠系统内的堆叠设备之间的桥梁。堆叠系统选择的堆叠端口，一般要求具备较高的可靠性。若堆叠系统的堆叠端口出现故障，整个堆叠系统跨设备的流量将会出现比较严重的影响，从而影响网络的可靠性和稳定性。为了保证堆叠端口的可靠性，一般情况下，会将多个堆叠端口捆绑成一个聚合组。若某个堆叠端口出现故障，其他堆叠端口还可以维持堆叠系统的正常运转。
目前，堆叠系统的堆叠端口的故障防护方法是：
1、使用动态链路捆绑的链路聚合控制协议(Link Aggregation Control Protocol，LACP)进行处理，在感知堆叠端口出现故障的时刻，通过运算LACP协议将其隔离。
2、使用静态链路捆绑，在感知堆叠端口出现故障的时候，直接通过底层芯片处理，将堆叠口移除。
由此可见，目前的技术中，为了保证堆叠系统的稳定性，可以采用动态和静态两种方式对故障堆叠口进行隔离和移除。然而，无论采用动态链路捆绑或 静态链路捆绑的方式，堆叠端口一旦被移除，则再无恢复的可能性，导致堆叠系统可能出现单纤运行的危险状态。
发明内容
本申请实施例提供了一种故障处理方法，应用于堆叠设备，包括：若确定堆叠端口出现故障，将堆叠端口的生成树状态设置为阻塞状态；判断堆叠端口是否恢复正常；将堆叠端口的生成树状态设置为转发状态。
本申请实施例提供了一种堆叠设备，包括：第一判断模块、第二判断模块和处理模块；第一判断模块用于判断堆叠端口是否出现故障；处理模块用于若确定堆叠端口出现故障，将堆叠端口的生成树状态设置为阻塞状态；第二判断模块用于判断堆叠端口是否恢复正常；处理模块还用于若确定堆叠端口恢复正常，将堆叠端口的生成树状态设置为转发状态。
本申请实施例提供了一种堆叠设备，包括：至少一个处理器；以及，与至少一个处理器通信连接的存储器；其中，存储器存储有可被至少一个处理器执行的指令，指令被至少一个处理器执行，以使至少一个处理器能够执行上述实施方式提及的故障处理方法。
本申请实施例提供了一种计算机可读存储介质，存储有计算机程序，计算机程序被处理器执行时，实现上述实施方式提及的故障处理方法。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定，附图中具有相同参考数字标号的元件表示为类似的元件，除非有特别申明，附图中的图不构成比例限制。
图1是本申请实施例中的故障处理方法的流程图；
图2是本申请实施例中的另一故障处理方法的示意图；
图3是本申请实施例中的又一故障处理方法的示意图；
图4是本申请实施例中堆叠系统的堆叠端口均正常通信时堆叠系统的结构示意图；
图5是本申请实施例中端口A2和端口B2之间出现通信异常状态时堆叠系 统的结构示意图；
图6是本申请实施例中的堆叠设备的结构示意图；
图7是本申请实施例中的堆叠设备的结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各实施例进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施例中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施例的种种变化和修改，也可以实现本申请所要求保护的技术方案。以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
在本申请公开的描述中，需要理解的是，术语“第一”、“第二”等仅用于描述目的，而不能理解为指示或暗示相对重要性。此外，在本申请公开的描述中，除非另有说明，“多个”的含义是两个或两个以上。
本申请实施例中，如图1所示的故障处理方法，由堆叠系统中的堆叠设备执行，如交换机，包括如下步骤。
步骤101：若确定堆叠端口出现故障，将堆叠端口的生成树状态设置为阻塞状态。
步骤102：若确定堆叠端口恢复正常，将堆叠端口的生成树状态设置为转发状态。
本申请实施例中，堆叠设备在堆叠端口出现故障的情况下，将该堆叠端口的生成树状态设置为阻塞(block)状态。堆叠端口的生成树状态为阻塞状态时，并未将该堆叠端口从链路捆绑中移除，但该堆叠端口不再转发业务转发报文。堆叠系统将自动选择其他生成树状态为转发状态的堆叠端口。由于出现故障的堆叠端口并未从链路捆绑中移除，在出现故障的堆叠端口恢复正常后，将该堆叠端口的生成树状态设置为转发(forward)状态，即可使得该堆叠端口开始转发业务转发报文，恢复该堆叠端口所在的堆叠链路的正常通信。相对于在堆叠端口出现故障后直接移除该堆叠端口，在出现故障的堆叠端口恢复正常后将出 现故障的堆叠端口恢复转发状态，继续转发业务转发报文，降低了堆叠系统出现单线运行的危险状态的概率。
在一个实施例中，在所述若确定堆叠端口出现故障，将所述堆叠端口的生成树状态设置为阻塞状态之前，还包括：判断堆叠端口是否接收到对端设备发送的心跳报文或响应报文；若确定未接收到心跳报文或响应报文，确定堆叠端口出现故障。
具体地，堆叠设备和对端设备之间通过心跳报文交互的方式检测故障。堆叠设备和对端设备中的一方(以下称为发送方)向另一方(以下称为接收方)发送心跳报文，若两者间通信正常，接收方在接收到心跳报文后，发送响应报文给发送方。接收方接收到心跳报文，确定接收方的堆叠端口正常。发送方接收到响应报文，确定发送方的堆叠端口正常。若两者间通信异常，接收方无法接收到心跳报文，也无法发送响应报文给发送方。接收方未接收到心跳报文，确定接收方的堆叠端口出现故障。发送方未接收到响应报文，确定发送方的堆叠端口出现故障。
通过上述内容可知，若堆叠设备为发送方，对端设备为接收方，判断堆叠端口是否出现故障，包括：判断堆叠端口是否接收到对端设备发送的响应报文；若确定未接收到响应报文，确定堆叠端口出现故障。若堆叠设备为接收方，对端设备为发送方，判断堆叠端口是否出现故障，包括：判断堆叠端口是否接收到对端设备发送的心跳报文；若确定未接收到心跳报文，确定堆叠端口出现故障。
值得一提的是，通过心跳报文判断堆叠端口是否出现故障，使得堆叠系统的任意一侧的堆叠端口出现故障时，出现故障的堆叠端口和堆叠系统另一侧的与出现故障的堆叠端口对应的堆叠端口都可以被发现，并及时将其生成树状态设置为block状态。由于堆叠系统两侧的出现故障的堆叠端口的生成树状态均被设置为block状态，使得堆叠系统在发送业务转发报文时，可以绕开出现故障的堆叠端口，避免只移除一侧的堆叠端口导致大量丢包的情况。此外，由于堆叠设备和对端设备之间通过心跳报文交互的方式检测故障，心跳报文的发送频率可以达到毫秒级。相对于通过秒级的LACP报文感知堆叠系统异常的动态 链路捆绑方法，感知堆叠系统的故障的速度更快，减少了大量丢包的情况，减少了堆叠系统恢复所消耗的时间。
需要说明的是，本领域技术人员可以理解，除通过心跳报文检测故障以外，还可以通过其他方式检测堆叠端口是否发生故障，本实施例不一一列举。
可选择的，在确定未接收到心跳报文或响应报文之后，在确定堆叠端口出现故障之前，故障处理方法还包括：确定未接收到心跳报文或响应报文的时长大于预设时长。堆叠设备在预设时长未接收到心跳报文或响应报文后，再将堆叠端口的生成树状态设置为block状态，可以减少由于个别心跳报文传输出差导致将未出现故障的堆叠端口设置为block状态，造成浪费该堆叠端口的资源的情况。
需要说明的是，本领域技术人员可以理解，预设时长可以根据堆叠设备和对端设备之间的心跳报文的发送频率确定，例如，心跳报文的发送频率为X毫秒/次，则预设时长可以设置为aX毫秒；其中，a为正整数。本实施例不限制预设时长的具体取值。
需要说明的是，本领域技术人员可以理解，堆叠设备设置的预设时长和对端设备设置的预设时长可以相同，也可以不同，本实施例不做限制。
可选择的，在所述若确定所述堆叠端口恢复正常，将所述堆叠端口的生成树状态设置为转发状态之前，还包括：判断堆叠端口是否接收到对端设备发送的心跳报文或响应报文；若确定接收到心跳报文或响应报文，确定堆叠端口恢复正常。
具体地，堆叠系统中的发送方继续往设置为block的堆叠端口发送心跳报文。由于堆叠系统将此故障堆叠端口设置了block状态，堆叠端口的生成树状态为block状态时，屏蔽通过此堆叠端口的业务转发报文，但并不会屏蔽心跳报文，故堆叠系统的发送方不会因为该堆叠端口被设置了block状态而无法发送心跳报文。若堆叠端口的故障未得到排除，接收方仍然无法接收到此心跳报文，而发送方也无法得到接收方的响应报文。因此，在堆叠端口故障持续阶段，堆叠系统的发送方和接收方的堆叠端口继续保持生成树状态为block状态。若 堆叠端口故障得到排除，接收方可以接收到发送方发送的心跳报文，并发送响应报文至发送方。接收方接收到心跳报文后，可以将自身接收到心跳报文的堆叠端口的生成树状态设置为forward状态。发送方也能够接收到接收方的回应的心跳报文。发送方接收到接收方回应的响应报文后，可以将自身的接收到响应报文的堆叠端口的生成树状态设置为forward状态。堆叠系统两侧的堆叠端口的生成树状态均设置为forward状态，堆叠系统的此堆叠端口自动恢复正常状态。
通过上述内容可知，若堆叠设备为发送方，对端设备为接收方，判断堆叠端口是否恢复正常，包括：判断堆叠端口是否接收到对端设备发送的响应报文；若确定接收到响应报文，确定堆叠端口恢复正常。若堆叠设备为接收方，对端设备为发送方，判断堆叠端口是否恢复正常，包括：判断堆叠端口是否接收到对端设备发送的心跳报文；若确定接收到心跳报文，确定堆叠端口恢复正常。
可选择的，在确定接收到心跳报文或响应报文之后，在确定堆叠端口恢复正常之前，故障处理方法还包括：确定连续接收到心跳报文或响应报文的次数大于预设次数。堆叠设备在连续接收到预设次数的心跳报文或响应报文后，再将堆叠端口的生成树状态设置为forward状态，可以避免出现故障的堆叠端口未完全排除故障时，频繁改变堆叠端口的生成树状态造成系统紊乱的情况。
需要说明的是，本领域技术人员可以理解，预设次数可以根据堆叠系统中的堆叠设备数量等确定，例如，预设次数可以设置为2，或者其他大于1的正整数。本实施例不限制预设次数的具体取值。
需要说明的是，本领域技术人员可以理解，堆叠设备设置的预设次数和对端设备设置的预设次数可以相同，也可以不同，本实施例不做限制。
在一个实施例中，心跳报文携带有对端设备的认证信息，或者，响应报文携带有堆叠设备发送的心跳报文中的认证信息。
具体地，若堆叠设备为发送方，对端设备为接收方，堆叠设备在发送心跳报文时，在心跳报文中携带堆叠设备的认证信息。对端设备在接收到心跳报文后，反馈响应报文至堆叠设备，响应报文中携带有堆叠设备的心跳报文中的认 证信息。若堆叠设备为接收方，对端设备为发送方，对端设备在发送心跳报文时，在该心跳报文中携带对端设备的认证信息。堆叠设备在接收到心跳报文后，反馈响应报文至对端设备，响应报文中携带有对端设备的心跳报文中的认证信息。在心跳报文和响应报文中携带认证信息，避免堆叠系统中其他堆叠端口的心跳报文或响应报文无法送至该堆叠设备的该堆叠端口，导致堆叠设备误判断堆叠设备的状态，提高了堆叠系统的可靠性。
可选择的，认证信息包括序列号和/或时间戳。具体地，若堆叠设备为发送方，序列号为堆叠设备的序列号，时间戳为堆叠设备的时间戳。若堆叠设备为接收方，序列号为对端设备的序列号，时间戳为对端设备的时间戳。
需要说明的是，本领域技术人员可以理解，认证信息还可以堆叠设备或对端设备的其他独有的认证信息，本实施例不起限定作用。
以上各实施例可以相互结合相互引用，例如下面是各实施例结合后的例子，然并不以此为限；各实施例在不矛盾的前提下可以任意结合成为一个新的实施例。
如图2所示，以堆叠设备为心跳报文的发送方为例，堆叠设备执行的故障处理方法包括以下步骤。
步骤201：周期性发送心跳报文至对端设备的堆叠端口。
具体地，堆叠设备通过自身的堆叠端口周期性地向对端设备发送心跳报文。
可选择的，该心跳报文可包含堆叠设备的认证信息。
步骤202：判断自身的堆叠端口是否接收到对端设备发送的响应报文。
具体地，若堆叠设备的堆叠端口和对端设备的堆叠端口均未出现故障，通信正常，对端设备可以接收到心跳报文。对端设备在接收到心跳报文后，通过对端设备的堆叠端口向堆叠设备的堆叠端口发送响应报文。若堆叠设备的堆叠端口或对端设备的堆叠端口出现故障，通信异常，对端设备无法接收到心跳报文。对端设备无法向堆叠设备的堆叠端口发送响应报文。因此，若自身的堆叠端口接收到响应报文，说明堆叠设备的堆叠端口和对端设备的堆叠端口均未出现故障，不改变堆叠设备的堆叠端口的生成树状态，继续执行步骤202。若自身的堆叠端口未接收到响应报文，说明堆叠设备的堆叠端口或对端设备的堆叠 端口出现故障，执行步骤203。
可选择的，响应报文中携带心跳报文中的认证信息。
步骤203：确定堆叠端口出现故障。
步骤204：将堆叠端口的生成树状态设置为阻塞状态。
相应地，对端设备无法接收到心跳报文，对端设备确定对端设备的堆叠端口出现故障，对端设备的堆叠端口的生成树状态设置为阻塞状态。
步骤205：周期性发送心跳报文至对端设备的堆叠端口。
步骤206：判断自身的堆叠端口是否接收到对端设备发送的响应报文。
具体地，若堆叠设备的堆叠端口或对端设备的堆叠端口的故障未消除，堆叠设备仍然无法接收到响应报文，若堆叠设备的堆叠端口或对端设备的堆叠端口的故障消除，通信正常，对端设备可以接收到心跳报文。对端设备在接收到心跳报文后，通过对端设备的堆叠端口向堆叠设备的堆叠端口发送响应报文。因此，若自身的堆叠端口接收到响应报文，说明堆叠设备的堆叠端口或对端设备的堆叠端口的故障已消除，改变堆叠设备的堆叠端口的生成树状态，执行步骤207。若自身的堆叠端口未接收到响应报文，说明堆叠设备的堆叠端口或对端设备的堆叠端口的故障未消除，继续执行步骤206。
步骤207：确定堆叠端口恢复正常。
步骤208：将堆叠端口的生成树状态设置为转发状态。
具体地，在将堆叠端口的生成树状态设置为转发状态后，返回执行步骤201。
相应地，对端设备接收到心跳报文，对端设备确定对端设备的堆叠端口故障消除，恢复正常，对端设备的堆叠端口的生成树状态设置为转发状态。
如图3所示，以堆叠设备为心跳报文的接收方为例，堆叠设备执行的故障处理方法包括以下步骤。
步骤301：判断自身的堆叠端口是否接收到对端设备发送的心跳报文。
具体地，对端设备通过对端设备的堆叠端口周期性地向堆叠设备发送心跳报文。若堆叠设备的堆叠端口和对端设备的堆叠端口均未出现故障，通信正常，堆叠设备可以接收到心跳报文。若堆叠设备的堆叠端口或对端设备的堆叠端口出现故障，通信异常，堆叠设备无法接收到心跳报文。因此，若堆叠设备的堆 叠端口接收到心跳报文，说明堆叠设备的堆叠端口和对端设备的堆叠端口均未出现故障，不改变堆叠设备的堆叠端口的生成树状态，继续执行步骤301。若堆叠设备的堆叠端口未接收到心跳报文，说明堆叠设备的堆叠端口或对端设备的堆叠端口出现故障，执行步骤302。
可选择的，响应报文中携带心跳报文中的认证信息。
步骤302：确定堆叠端口出现故障。
步骤303：将堆叠端口的生成树状态设置为阻塞状态。
相应地，对端设备无法接收到响应报文，对端设备确定对端设备的堆叠端口出现故障，对端设备的堆叠端口的生成树状态设置为阻塞状态。对端设备的堆叠端口设置为阻塞状态后，继续周期性地向堆叠设备发送心跳报文。
步骤304：判断自身的堆叠端口是否接收到对端设备发送的心跳报文。
具体地，若堆叠设备的堆叠端口或对端设备的堆叠端口的故障未消除，堆叠设备仍然无法接收到心跳报文，若堆叠设备的堆叠端口或对端设备的堆叠端口的故障消除，通信正常，堆叠设备可以接收到心跳报文。因此，若自身的堆叠端口接收到心跳报文，说明堆叠设备的堆叠端口或对端设备的堆叠端口的故障已消除，改变堆叠设备的堆叠端口的生成树状态，执行步骤305。若自身的堆叠端口未接收到心跳报文，说明堆叠设备的堆叠端口或对端设备的堆叠端口的故障未消除，继续执行步骤304。
步骤305：确定堆叠端口恢复正常。
步骤306：将堆叠端口的生成树状态设置为转发状态。
具体地，在将堆叠端口的生成树状态设置为转发状态后，返回执行步骤301。
相应地，对端设备接收到响应报文，对端设备确定对端设备的堆叠端口故障消除，恢复正常，对端设备的堆叠端口的生成树状态设置为转发状态。
以下以堆叠设备和对端设备均为交换机为例，对本实施例提及的故障处理方法进行举例说明。
例如，堆叠系统包括交换机A401和交换机B402，交换机A401是堆叠主设备。交换机A401使用端口A1作为堆叠端口连接交换机B402的端口B1，交换机A401使用端口A2作为堆叠端口连接交换机的端口B2，以使交换机A401 和交换机B402进行堆叠通信。交换机A401为堆叠设备，交换机B402为对端设备，或者，交换机A401为对端设备，交换机B402为堆叠设备。心跳报文的发送周期为50毫秒，预设时长为150毫秒，预设次数为2次，认证信息为时间戳信息。
若堆叠系统的堆叠端口均正常通信，堆叠系统的结构示意图如图4所示。交换机A401的端口A1和交换机B402的端口B1通信，交换机A401的端口A2和交换机B402的端口B2通信。交换机A401和交换机B402之间交互心跳报文。
若交换机A401的端口A2和交换机B402的端口B2之间出现通信异常状态，堆叠系统的结构示意图如图5所示。交换机A401每50ms向交换机B402发送心跳报文，携心跳报文携带交换机A401的时间戳信息。由于交换机A401的端口A2和交换机B402的端口B2之间出现通信异常，交换机B402的端口B2无法收到交换机A401的心跳报文。若3个周期(150毫秒)内，交换机B402的端口B2持续未收到交换机A401的心跳报文，将交换机B402的端口B2的生成树状态设置为block状态。交换机A401在3个周期(150毫秒)内，未在端口A2上收到交换机B402携带的A设备时间戳信息的响应报文，立刻将交换机A401的端口A2端口的生成树状态设置为block状态。交换机A401的端口A2和交换机B402的端口B2的生成树状态全部被设置为block状态。这两个堆叠口不会再转发业务报文，交换机A401与交换机B402构成的堆叠系统将通过剩下的端口A1和端口B1的连接线路转发跨堆叠设备的业务报文。交换机A401继续往已经设置block状态的端口A2持续每50ms发送心跳报文。虽然交换机A401的端口A2和交换机B402的端口B2的生成树状态设置为block状态，但block状态不影响心跳报文的转发，故交换机A401向端口A2发送心跳报文的动作未受到影响。若端口A2和端口B2之间的异常故障状态未得到排除，交换机B402的端口B2无法收到心跳报文，而交换机A401的端口A2也无法得到交换机B402的响应报文。因此，在故障持续阶段，交换机A401的端口A2和交换机B402的端口B2的生成树状态继续保持为block状态。
若交换机A401的端口A2和交换机B402的端口B2持续通信异常被排除，由于端口A2和端口B2之间异常故障状态已经得到排除，交换机B402立刻可 以在端口B2接收到交换机A401的心跳报文，并且将响应报文从端口B2回复给交换机A401。交换机A401在端口A2收到交换机B402回应的带有正确时间戳信息的响应报文。交换机B402将响应报发送给交换机A401后，再等待50ms，又在端口B2收到一次交换机A401的心跳报文，则交换机B402将端口B2的生成树状态设置为forward状态。交换机A401从端口A2接收到交换机B402发送的带有正确时间戳信息的响应报文后，即可将端口A2的生成树状态设置为forward状态。至此，交换机A401的端口A2和交换机B402的端口B2的生成树状态均设置为forward状态，交换机A401和交换机B402构成的堆叠系统的端口A2和端口B2之间的链路自动恢复正常状态。
通过上述内容可知，本实施例提及的故障处理方法，利用堆叠系统两侧进行带有认证信息的心跳报文交互，可以快速探测到堆叠端口出现链路转发异常的状态，并且通过对心跳报文的接收状态的判定，可以将异常的堆叠端口的生成树状态设置为block状态，从堆叠系统中移除出现故障的堆叠端口，从而达到快速排除故障堆叠端口的效果，防止网络出现大量丢包。而生成树状态的设置，并不会影响此心跳报文的发送流程，因此，堆叠系统还可以正常的发送此心跳报文，只不过在堆叠端口异常期间，此心跳报文不会被堆叠系统的接收侧收到。而在故障被排除之后，心跳报文会立刻恢复正常收发，而堆叠系统的两侧会根据心跳报文的接收状态，自动将已经排除故障的堆叠端口的成树状态设置为forward，以重新恢复此堆叠端口在堆叠系统中的正常工作。
通过本实施例提及的故障处理方法，堆叠系统既可以快速的排除异常堆叠端口，使其不再对堆叠系统造成严重影响，又可以在故障恢复的时候，无需人为干预，即可快速恢复此堆叠端口在堆叠系统中的正常工作状态。因此，采用本实施例提及的故障处理方法可以大大增强堆叠系统对堆叠口链路故障的自动排障处理和自动恢复处理，有效的增强了网络设备的可靠性可维护性和稳定性。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本申请实施例还提供一种堆叠设备，如图6所示，包括：第一判断模块601、第二判断模块602和处理模块603。第一判断模块601用于判断堆叠端口是否出现故障；处理模块603用于若确定堆叠端口出现故障，将堆叠端口的生成树状态设置为阻塞状态；第二判断模块602用于判断堆叠端口是否恢复正常；处理模块603还用于若确定堆叠端口恢复正常，将堆叠端口的生成树状态设置为转发状态。
不难发现，本实施例为与上述方法实施例相对应的装置实施方式，本实施例可与上述方法实施例互相配合实施。上述方法实施例中提到的相关技术细节在本实施例中依然有效，为了减少重复，这里不再赘述。相应地，本实施例中提到的相关技术细节也可应用在上述方法实施例中。
值得一提的是，本实施例中所涉及到的各模块均为逻辑模块，在实际应用中，一个逻辑单元可以是一个物理单元，也可以是一个物理单元的一部分，还可以以多个物理单元的组合实现。此外，为了突出本申请的创新部分，本实施例中并没有将与解决本申请所提出的技术问题关系不太密切的单元引入，但这并不表明本实施例中不存在其它的单元。
本申请实施例还提供一种堆叠设备，如图7所示，包括：至少一个处理器701；以及与至少一个处理器701通信连接的存储器702；其中，存储器存储有可被至少一个处理器701执行的指令，指令被至少一个处理器701执行，以使至少一个处理器701能够执行上述方法实施例。
其中，存储器702和处理器701采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器701和存储器702的各种电路连接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器701处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传送给处理器701。
处理器701负责管理总线和通常的处理，还可以提供各种功能，包括定时， 外围接口，电压调节、电源管理以及其他控制功能。而存储器702可以被用于存储处理器701在执行操作时所使用的数据。
本申请实施例还提供一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施例。
即，本领域技术人员可以理解，实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述各实施方式是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (10)

  1. 一种故障处理方法，应用于堆叠设备，包括：
    若确定堆叠端口出现故障，将所述堆叠端口的生成树状态设置为阻塞状态；
    若确定所述堆叠端口恢复正常，将所述堆叠端口的生成树状态设置为转发状态。
  2. 根据权利要求1所述的故障处理方法，其中，在所述若确定堆叠端口出现故障，将所述堆叠端口的生成树状态设置为阻塞状态之前，还包括：
    判断所述堆叠端口是否接收到对端设备发送的心跳报文或响应报文；
    若确定未接收到所述心跳报文或所述响应报文，确定所述堆叠端口出现故障。
  3. 根据权利要求2所述的故障处理方法，其中，在确定未接收到所述心跳报文或所述响应报文之后，在所述确定所述堆叠端口出现故障之前，所述故障处理方法还包括：
    确定未接收到所述心跳报文或所述响应报文的时长大于预设时长。
  4. 根据权利要求2或3所述的故障处理方法，其中，在所述若确定所述堆叠端口恢复正常，将所述堆叠端口的生成树状态设置为转发状态之前，还包括：
    判断所述堆叠端口是否接收到对端设备发送的心跳报文或所述响应报文；
    若确定接收到所述心跳报文或所述响应报文，确定所述堆叠端口恢复正常。
  5. 根据权利要求4所述的故障处理方法，其中，在确定接收到所述心跳报文或所述响应报文之后，在所述确定所述堆叠端口恢复正常之前，所述故障处理方法还包括：
    确定连续接收到所述心跳报文或所述响应报文的次数大于预设次数。
  6. 根据权利要求2至5中任一项所述的故障处理方法，其中，所述心跳报文携带有所述对端设备的认证信息，或者，所述响应报文携带有所述堆叠设备发送的心跳报文中的认证信息。
  7. 根据权利要求6所述的故障处理方法，其中，所述认证信息包括序列号和/或时间戳。
  8. 一种堆叠设备，包括：第一判断模块、第二判断模块和处理模块；
    所述第一判断模块用于判断堆叠端口是否出现故障；
    所述处理模块用于若确定堆叠端口出现故障，将所述堆叠端口的生成树状态设置为阻塞状态；
    所述第二判断模块用于判断所述堆叠端口是否恢复正常；
    所述处理模块还用于若确定所述堆叠端口恢复正常，将所述堆叠端口的生成树状态设置为转发状态。
  9. 一种堆叠设备，包括：至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至7中任一项所述的故障处理方法。
  10. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时，实现如权利要求1至7中任一项所述的故障处理方法。
PCT/CN2022/098777 2021-06-21 2022-06-14 故障处理方法、堆叠设备及存储介质 WO2022267938A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110686363.5A CN115514623A (zh) 2021-06-21 2021-06-21 故障处理方法、堆叠设备及存储介质
CN202110686363.5 2021-06-21

Publications (1)

Publication Number Publication Date
WO2022267938A1 true WO2022267938A1 (zh) 2022-12-29

Family

ID=84499575

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/098777 WO2022267938A1 (zh) 2021-06-21 2022-06-14 故障处理方法、堆叠设备及存储介质

Country Status (2)

Country Link
CN (1) CN115514623A (zh)
WO (1) WO2022267938A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116915584A (zh) * 2023-09-08 2023-10-20 新华三技术有限公司 一种在网计算异常处理方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060047851A1 (en) * 2004-08-25 2006-03-02 Cisco Technoloy, Inc. Computer network with point-to-point pseudowire redundancy
CN102164056A (zh) * 2011-03-17 2011-08-24 杭州华三通信技术有限公司 堆叠链路聚合故障检测方法和堆叠设备
CN110505104A (zh) * 2019-09-20 2019-11-26 新华三信息安全技术有限公司 一种故障处理方法、装置、网络设备及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060047851A1 (en) * 2004-08-25 2006-03-02 Cisco Technoloy, Inc. Computer network with point-to-point pseudowire redundancy
CN102164056A (zh) * 2011-03-17 2011-08-24 杭州华三通信技术有限公司 堆叠链路聚合故障检测方法和堆叠设备
CN110505104A (zh) * 2019-09-20 2019-11-26 新华三信息安全技术有限公司 一种故障处理方法、装置、网络设备及存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116915584A (zh) * 2023-09-08 2023-10-20 新华三技术有限公司 一种在网计算异常处理方法及装置
CN116915584B (zh) * 2023-09-08 2023-12-08 新华三技术有限公司 一种在网计算异常处理方法及装置

Also Published As

Publication number Publication date
CN115514623A (zh) 2022-12-23

Similar Documents

Publication Publication Date Title
US7440397B2 (en) Protection that automatic and speedily restore of Ethernet ring network
US6658595B1 (en) Method and system for asymmetrically maintaining system operability
US20070047436A1 (en) Network relay device and control method
US9237092B2 (en) Method, apparatus, and system for updating ring network topology information
CN102255751A (zh) 一种堆叠冲突的处理方法和设备
CN111385107B (zh) 一种服务器的主备切换处理方法及装置
WO2022267938A1 (zh) 故障处理方法、堆叠设备及存储介质
CN100466583C (zh) 基于rrpp的快速环网防攻击的方法、装置和系统
CN112491700A (zh) 网络路径调整方法、系统、装置、电子设备及存储介质
EP2426855B1 (en) Address refresh method and system
US11258666B2 (en) Method, device, and system for implementing MUX machine
CN101599906B (zh) 端口状态设置的方法及装置
CN104994173A (zh) 一种消息处理方法和系统
WO2011150780A1 (zh) 触发路由切换的方法和服务运营商侧运营商边缘设备
CN112104548A (zh) 通信方法及装置
CN114884803B (zh) 多重冗余状态的处理方法、装置、设备和介质
CN109120558B (zh) 一种单板端口故障自动排除方法及系统
CN111224803B (zh) 一种堆叠系统中多主检测方法及堆叠系统
JP6134720B2 (ja) 接続方法
CN115152192B (zh) Pce受控网络可靠性
CN110138636B (zh) 动态线性保护方法及装置
CN115102897B (zh) 一种基于链路聚合的堆叠分裂保护方法
CN112653596B (zh) 一种路由信息下发、网关设备切换的方法及装置
CN113411254B (zh) 一种链路处理方法及装置
CN112953789B (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: 22827434

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE