CN117749566A

CN117749566A - Fault processing method and device, equipment and medium of MRP ring network

Info

Publication number: CN117749566A
Application number: CN202311819737.1A
Authority: CN
Inventors: 郭继成
Original assignee: Kyland Technology Co Ltd
Current assignee: Kyland Technology Co Ltd
Priority date: 2023-12-27
Filing date: 2023-12-27
Publication date: 2024-03-22

Abstract

The application provides a fault processing method, device, equipment and medium of an MRP ring network, when the MRP ring network is in a ring-closed state, a main port of an MRM in the MRP ring network is in a forwarding state, and a secondary port is in a blocking state, and the method is applied to the MRM and comprises the following steps: in the ring-closed state, when a port offline event occurs in a first MRC of the MRP ring network, receiving a port offline message sent by the first MRC, converting a secondary port of the MRM from a blocking state to a forwarding state according to the port offline message, and sending a topology change message outwards through two ports of the MRM, so that each MRC in the MRP ring network updates respective network topology information according to the topology change message. According to the method and the device, the port uplink and downlink messages sent by the MRC are responded quickly, the convergence time of MRP ring network faults is shortened, and the reliability and stability of system operation in time-sensitive application scenes are guaranteed.

Description

Fault processing method and device, equipment and medium of MRP ring network

Technical Field

The present invention relates to the field of MRP ring technologies, and in particular, to a method, an apparatus, a device, and a medium for fault handling in an MRP ring.

Background

MRP (Media Redundancy Protocol) is a media redundancy protocol, MRP protocol can eliminate loops in a ring network, avoiding broadcast storms; meanwhile, the MRP protocol can provide redundancy of nodes and links, and when single-point faults occur to equipment in the ring network or links among the equipment, the MRP protocol can quickly restore the functions of the network so as to meet the real-time and reliability requirements of industrial scenes. In the MRP redundancy domain, the roles of devices are divided into the following:

MRM (Media Redundancy Manager ): the MRM plays roles of monitoring loops and controlling links in the looped network, and eliminates loops when the loops are closed and restores communication links among nodes when the links in the looped network are failed by blocking ports of self equipment in the looped network or releasing the blocked ports.

MRC (Media Redundancy Client ): the MRC monitors the ring port link status on its own device and notifies the MRM of the link change.

MRA (Media Redundancy Automanager, media redundancy automation manager): in an MRP redundant domain, all devices with MRP capability can be made into MRM or MRC, but in the same time, one device is in the working state of the MRM, management of a ring network cannot be guaranteed when the MRM breaks down, reliability of an MRP protocol is affected, redundancy of an MRM site is provided through an election mechanism of the MRA based on the MRM, after the whole system is started, the MRA in the same MRP redundant domain can conduct automatic election until one unique MRM is elected, other MRA works as the MRC, when the elected MRM breaks down, the MRA which does not break down in the same MRP redundant domain automatically re-elects the MRM, and therefore reliability of the MRP protocol is improved.

In the ring network of the MRP protocol, the MRM periodically sends out an mrp_test (MRP Test) message through two ring ports, and sets the main port to Forwarding state, in which all messages are forwarded, if the MRM receives an mrp_test message sent by itself from any ring port, it indicates that the MRP ring is closed, the MRM sets the secondary port to Blocked state, in which the ports block all messages except Test messages, topologchange messages and LinkUP/linkkown messages. If the MRM does not receive the MRP_test message sent by the MRM within the appointed time, which indicates that the MRP ring is in a ring-on state, namely the ring is disconnected, the MRM can set the secondary port to be in a Forwarding state so as to ensure that the communication of the MRP ring network is not interrupted.

When a Port link down event occurs to one MRC in the MRP ring network, the ring Port on which the Port is down will block the Forwarding of the message, and send the mrp_link down message to the MRM through the ring Port, at this time, the MRM may quickly send the mrp_test message through two ports by shortening the transmission interval of the mrp_test message, so as to quickly confirm the state of the MRP ring network, if it is confirmed that the MRP ring network fails, the Blocked secondary Port is converted from the Blocked state to the Forwarding state, so as to restore the communication of the MRP ring network, and send the mrp_topologchange message through two ring ports thereof, so as to notify the MRP ring network that the network topology of each MRC in the MRP ring network has changed.

The existing fault detection and elimination mode is relatively dependent on the detection time of the MRP_test message and the timing precision of the platform, for example, under a linux platform, the fault detection and elimination time can be as long as 100-200ms, the time can influence the performance of a system for a time-sensitive application scene, and the reliability and stability of the system operation under the time-sensitive application scene can not be ensured.

Disclosure of Invention

In view of this, the present application proposes a method, an apparatus, a device, and a medium for processing a failure of an MRP ring network, which shorten the convergence time of the MRP ring network failure by fast responding to an on-line and off-line message sent by an MRC port, and ensure the reliability and stability of the system operation in a time-sensitive application scenario.

In a first aspect, the present application provides a fault handling method for an MRP ring network, where when the MRP ring network is in a ring closed state, a primary port of an MRM in the MRP ring network is in a forwarding state, and a secondary port is in a blocking state, and the fault handling method is applied to the MRM, and the method includes:

in the ring-closed state, when a port offline event occurs in a first MRC of the MRP ring network, receiving a port offline message sent by the first MRC, converting a secondary port of the MRM from a blocking state to a forwarding state according to the port offline message, and sending a topology change message outwards through two ports of the MRM, so that each MRC in the MRP ring network updates respective network topology information according to the topology change message.

From above, in the fault handling method of the MRP ring network provided by the present application, when the MRP ring network is in a normal ring closed state, the main port of the MRM in the MRP ring network is in Forwarding state, all messages are forwarded in the state, and the secondary port is in Blocked state, and in the state, the ports block all messages except Test messages, topologyChange messages and LinkUP/linkudn messages, so as to eliminate loops and avoid generating broadcast storm. When a Port link down event occurs to an MRC in an MRP ring network in a ring closing state, the MRM directly trusts an MRP_LinkDOWN message sent by the MRC, does not spend time to send a test message and wait for whether to receive the test message, directly converts a secondary Port from a Blocked state to a Forwarding state according to the MRP_LinkDOWN message sent by the MRC, and simultaneously sends an MRP_TopologicChange message outwards through a main Port and the secondary Port of the MRP ring network to inform each MRC in the MRP ring network that the network topology where the MRC is located is changed so that each MRC in the MRP ring network updates the network topology information according to the topology change message. By trust and quick response to the MRP_LinkDOWN message sent by the MRC, the link state change in the MRP ring network can be rapidly processed, and the convergence time of the MRP ring network faults is shortened.

Optionally, the method further comprises:

in the ring opening state, when a port on-line event occurs to the first MRC of the MRP ring network, receiving a port on-line message sent by the first MRC, converting a secondary port of the MRM from a forwarding state to a blocking state according to the port on-line message, and sending a topology change message outwards through two ports of the MRM, so that each MRC in the MRP ring network updates respective network topology information according to the topology change message.

When the MRC in the MRP ring network detects that the Port with the fault is restored in the ring opening state, namely when the MRC has a Port link up event, the MRM directly trusts the MRP_link up message sent by the MRC, does not take time to send a test message and wait for whether to receive the test message, directly converts the secondary Port from the Forwarding state to the Blocked state according to the MRP_link up message sent by the MRC, and simultaneously sends the MRP_Topologchange message outwards through the primary Port and the secondary Port of the MRP ring network, and informs each MRC in the MRP ring network of the change of the network topology where the MRP ring network is located, so that each MRC in the MRP ring network updates respective network topology information according to the topology change message, and the link state change in the MRP ring network is processed rapidly, and the convergence time of the MRP fault is shortened.

Optionally, in the closed state, after the port offline event occurs in the first MRC of the MRP ring network, the method further includes: converting the ring-closed state recorded by the MRM into a ring-open state; in the ring-open state, when the port on-line event occurs in the first MRC of the MRP ring network, the method further includes: and converting the ring-opening state recorded by the MRM into a ring-closing state.

From above, after the MRC of the MRP ring network has the port offline event, the ring-closed state recorded by the MRM can be converted into the ring-open state; after the MRC of the MRP ring network has the port on-line event, the ring-opening state recorded by the MRM can be converted into the ring-closing state.

Optionally, the receiving the port offline message sent by the first MRC includes:

when detecting that a port offline event occurs to a certain ring port of the first MRC, receiving the port offline message sent by the first MRC through another ring port; and detecting a certain ring port with the port offline event through the test message periodically sent by the MRM.

From the above, when the MRC generates the port offline event, the port offline message can be sent to the MRM through the other ring port thereof, so that the MRM converts the state of the next port according to the received port offline message, thereby eliminating the link communication failure caused by the port offline. The MRM can also periodically send out test messages to realize port fault detection in the MRP ring network.

Optionally, the receiving the port online message sent by the first MRC includes:

when a certain ring port of the first MRC, which is subjected to the port offline event, is detected to be restored, the port online message is sent through any ring port of the first MRC, and the certain ring port subjected to the port restoration is detected through the test message periodically sent by the MRM.

From the above, when the MRC generates the port on-line event, the MRM may send the port on-line message to the MRM through any ring port thereof, so that the MRM may switch the state of the next port according to the received port on-line message, so as to eliminate the loop.

In a second aspect, the present application provides a fault handling method for an MRP ring network, where when the MRP ring network is in a ring closed state, a primary port of an MRM in the MRP ring network is in a forwarding state, and a secondary port is in a blocking state, and the fault handling method is applied to a first MRC where a port offline event/port online event occurs, where the method includes:

when a port offline event/port online event occurs to a certain ring port of the MRP, sending a port offline message/port online message to the MRP, so that the MRM converts a secondary port from a blocking state to a forwarding state according to the port offline message, or converts the secondary port from the forwarding state to the blocking state according to the port online message, and sends a topology change message outwards;

And receiving the topology change message, and updating the network topology information of the topology change message according to the topology change message.

In the fault processing method of the MRP ring network, when the MRC in the MRP ring network detects that a Port LinkDown or Port LinkUP event occurs in a certain ring Port of the MRP ring network in a ring closing state, a corresponding MRP_LinkDOWN message or MRP_LinkUP message is actively sent to the MRM, so that the MRM correspondingly converts the state of the secondary Port by directly trusting the MRP_LinkDOWN message or the MRP_LinkUP message, and simultaneously sends the MRP_TopologChange message outwards through the primary Port and the secondary Port of the MRP ring network, and the MRC in the MRP ring network is informed of change of network topology where the MRC is located, so that each MRC in the MRP ring network updates network topology information according to the topology change message. By trust and quick response to the MRP_LinkDOWN message sent by the MRC, the link state change in the MRP ring network can be rapidly processed, and the convergence time of the MRP ring network faults is shortened.

In a third aspect, the present application provides a fault handling device for an MRP ring network, where when the MRP ring network is in a ring closed state, a primary port of an MRM in the MRP ring network is in a forwarding state, and a secondary port is in a blocking state, where the fault handling device is applied to a first MRC in the MRP ring network, and includes:

The detection module is used for sending port offline messages/port online messages to the MRP ring network when detecting that a port offline event/port online event occurs to a certain ring port of the first MRC, so that the MRM converts a secondary port from a blocking state to a forwarding state according to the port offline messages, or converts the secondary port from the forwarding state to the blocking state according to the port online messages, and sends topology change messages outwards;

the topology updating module is used for receiving the topology change message and updating the network topology information of the first MRC according to the topology change message;

the first MRC is a node in the MRP ring network, wherein the node is used for generating a port offline event/a port online event.

In a fourth aspect, the present application provides a fault handling device for an MRP ring network, where when the MRP ring network is in a ring closed state, a primary port of an MRM in the MRP ring network is in a forwarding state, and a secondary port is in a blocking state, where the fault handling device is applied to the MRM in the MRP ring network, and includes:

and the processing module is used for receiving a port offline message sent by a first MRC when the port offline event occurs to the first MRC of the MRP ring network in the ring closure state, converting a secondary port of the MRM from the blocking state to the forwarding state according to the port offline message, and sending a topology change message outwards through two ports of the MRM so that each MRC in the MRP ring network updates the network topology information according to the topology change message.

In a fifth aspect, the present application provides a computing device comprising:

a processor;

a memory for storing one or more programs;

and when the one or more programs are executed by the processor, the processor is enabled to realize the fault processing method of the MRP ring network.

In a sixth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a computer, implements a fault handling method for an MRP ring network as described above.

These and other aspects of the application will be apparent from and elucidated with reference to the embodiment(s) described hereinafter.

Drawings

Fig. 1 is a flowchart of a fault handling method of an MRP ring network provided in an embodiment of the present application;

fig. 2 is a schematic structural diagram of an MRP ring network when a port offline event occurs according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of an MRP ring network when an online event occurs in a port according to an embodiment of the present application;

fig. 4 is a structural diagram of a fault handling device of an MRP ring network provided in an embodiment of the present application;

fig. 5 is a block diagram of another fault handling device of an MRP ring network according to an embodiment of the present application;

Fig. 6 is a block diagram of a computing device according to an embodiment of the present application.

It should be understood that in the foregoing structural schematic diagrams, the sizes and forms of the respective block diagrams are for reference only and should not constitute an exclusive interpretation of the embodiments of the present application. The relative positions and inclusion relationships between the blocks presented by the structural diagrams are merely illustrative of structural relationships between the blocks, and are not limiting of the physical connection of the embodiments of the present application.

Detailed Description

The technical scheme provided by the application is further described below by referring to the accompanying drawings and examples. It should be understood that the system structures and service scenarios provided in the embodiments of the present application are mainly for illustrating possible implementations of the technical solutions of the present application, and should not be construed as the only limitation of the technical solutions of the present application. As one of ordinary skill in the art can know, with the evolution of the system structure and the appearance of new service scenarios, the technical scheme provided in the application is applicable to similar technical problems.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. If there is a discrepancy, the meaning described in the present specification or the meaning obtained from the content described in the present specification is used. In addition, the terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the present application.

The embodiment of the application provides a fault processing method of an MRP ring network, which shortens the convergence time of the MRP ring network fault by fast responding to the port uplink and downlink messages sent by an MRC, ensures the reliability and stability of the system operation in a time-sensitive application scene by enabling the fault recovery time to reach 10-20 ms.

As shown in fig. 1, an embodiment of the present application provides a fault handling method of an MRP ring network, where the method may be applied to an MRM, and includes:

s110: when the MRP ring network is in a ring-closed state, the main port of the MRM in the MRP ring network is in a forwarding state, and the secondary port is in a blocking state.

The MRM (Media Redundancy Manager ) plays a role of monitoring loops and controlling links in the ring network, and eliminates loops when the loops are closed and restores communication links among nodes when the links in the ring network are failed by blocking ports of self equipment in the ring network or releasing the blocked ports. In this step, the MRM may periodically send an mrp_test packet to the outside through its two ring ports (primary port and secondary port), and set the primary port to Forwarding state, if the MRM receives the mrp_test packet sent by itself from any ring port, it indicates that the MRP ring is closed, and the MRM will set the secondary port to Blocked state to eliminate the loop. If the MRM does not receive the MRP_test message sent by the MRM within the appointed time, which indicates that the MRP ring is in a ring-on state, namely the ring is disconnected, the MRM can set the secondary port to be in a Forwarding state so as to ensure that the communication of the MRP ring network is not interrupted, and simultaneously, the MRP_Topologchange message is sent outwards through the primary port and the secondary port of the MRP ring network to inform each MRC in the MRP ring network that the network topology where the MRC is located is changed.

S120: in the ring-closed state, when a port offline event occurs in a first MRC of the MRP ring network, receiving a port offline message sent by the first MRC, converting a secondary port of the MRM from a blocking state to a forwarding state according to the port offline message, and sending a topology change message outwards through two ports of the MRM, so that each MRC in the MRP ring network updates respective network topology information according to the topology change message.

In the ring closed state, each MRC in the MRP ring network confirms whether the ring port is normal or not by detecting the ring port link state on the device itself, when detecting that the ring port link fails, the ring port with failure is blocked, and the MRP_LinkDOWN message is sent through the other ring port. After the MRM confirms that the MRC has a Port LinkDown event, the MRM does not take time to send an MRP_test message and wait to receive the MRP_test message by directly trusting the MRP_LinkDOWN message sent by the MRC, but directly converts the secondary Port from the Blocked state to the Forwarding state according to the MRP_LinkDOWN message sent by the MRC, and simultaneously sends an MRP_TopologicChange message outwards through the primary Port and the secondary Port of the MRC, and notifies each MRC in the MRP ring network that the network topology of the MRC is changed, and converts the recorded ring-closure state of the MRC into the ring-closure state.

After receiving the mrp_topiogy change message, each MRC in the MRP ring network clears its local network topology information, such as FDB (Filtering Database ), so as to relearn the MAC address after topology change.

When a port offline event occurs in the first MRC, it is indicated that a port in the MRP ring network where a certain MRC exists is in a blocking state, so that the state of a secondary port of the MRM needs to be converted from the blocking state to a forwarding state, so as to ensure that all the MRCs in the MRP ring network can forward or receive a message as much as possible.

S130: in the ring opening state, when a port on-line event occurs to a first MRC of an MRP ring network, receiving a port on-line message sent by the first MRC, converting a secondary port of the MRM from a forwarding state to a blocking state according to the port on-line message, and sending a topology change message outwards through two ports of the MRM, so that each MRC in the MRP ring network updates respective network topology information according to the topology change message.

In the ring-open state, when the ring Port fault recovery of the fault is detected through the periodic Test message, the state of the ring Port is changed from the blocking state to the Forwarding state, at this time, any Port of the MRC can forward the message, after confirming that the Port link up event occurs in the MRC, the MRM directly trusts the MRP_link up message sent by the MRC, does not take time to send the MRP_test message and wait to receive the MRP_test message, and directly converts the next Port from the Forwarding state to the blocking state according to the MRP_link up message sent by the MRC, and simultaneously sends the MRP_TopologicChange message outwards through the main Port and the secondary Port of the MRC to inform the MRP ring network that the network topology of each MRC in the MRP ring network has changed, and converts the recorded ring-open state into the ring-closed state.

The fault handling method of the embodiments of the present application will be described in the following by referring to the schematic diagrams of the MRP ring network structures shown in fig. 2 to 3.

Fig. 2 is a schematic structural diagram of an MRP ring network when an event of port offline occurs, where according to the embodiment of the present application, as shown in fig. 2, the MRP ring network includes an MRM and a plurality of MRCs, when the MRP ring network is in a ring closed state, a primary port of the MRM is in a Forwarding state, a secondary port is set in a Blocked state, and a communication link of the MRP ring network may be an MRM primary port-MRC 1-MRC2-MRC3-MRC4.

When a Port link event occurs in a link between MRC2 and MRC3 of the MRP ring network, the Port faults detected by the periodic test messages sent by the MRM by the MRC2 and the MRC3 can be detected, the ring Port connected with the faulty link is set to be in a Blocked state, and an mrp_linkdown message is sent to the MRM by the other ring Port, at this time, the MRM can directly trust the mrp_linkdown message sent by the MRC2 and the MRC3, and convert the secondary Port from the Blocked state to the Forwarding state according to the mrp_linkdown message sent by the MRC2 and the MRC3, and simultaneously send an mrp_topiogy change message outwards through the primary Port and the secondary Port of the MRC, so as to inform each MRC in the MRP ring network that the topology of the MRC is changed, and convert the recorded ring closed state (chk_rc) into a ring open state (chk_ro). The communication link of the MRP ring network can be MRC2-MRC1-MRM main port-MRM secondary port-MRC 4-MRC3.

After each MRC in the MRP ring network receives the MRP_TopologyChange message, network topology information before Port LinkDown occurs on a link between MRC2 and MRC3 recorded in a local FDB is cleared, so that topology connection relations after topology change can be learned again.

Fig. 3 is a schematic diagram of an MRP ring network structure when an on-line event occurs on a Port provided in an embodiment of the present application, according to the embodiment of the present application, after a failure link between MRC2 and MRC3 of the MRP ring network is restored, that is, after a Port link event occurs on the failure link between MRC2 and MRC3, both the MRC2 and the MRC3 can restore the Port detected according to a test packet periodically sent by the MRM, at this time, if a secondary Port of the MRM is still in a Forwarding state, a ring network storm may occur, so after the MRC2 and the MRC3 send an mrp_link up packet to the MRM through any ring Port thereof, at this time, the MRM can switch the Port from the Forwarding state to a blocking state according to the mrp_link up packet sent by the MRC2 and the MRC3, thereby avoiding that the mrp_link state is changed to the ring network topology of the MRM through the primary Port and the secondary Port thereof, and the topology of the MRC is changed to the topology of the MRC (change topology is recorded by the MRC). At this time, MRC2 and MRC3 may update their respective network topology information according to the received mrp_topologychange message, and the communication link of the MRP ring network is restored to MRM primary ports-MRC 1-MRC2-MRC3-MRC4.

After each MRC in the MRP ring network receives the MRP_TopologyChange message, network topology information before Port Link occurs on a link between MRC2 and MRC3 recorded by a local FDB is cleared, so that topology connection relations after topology change can be learned again.

In summary, according to the fault processing method for the MRP ring network provided by the embodiment of the present application, the MRM in the MRP ring network directly trusts the mrp_linkup/LinkDown message sent by the MRC in the MRP ring network, so that it does not take time to send the test message and wait for whether to receive the test message, but directly converts the state of the next port according to the mrp_linkup/LinkDown message sent by the MRC, and sends the mrp_topiogically change message to the outside, so that the network topology where each MRC in the MRP ring network is located is notified to change, so that the link state change in the MRP ring network can be rapidly processed, and the convergence time of the MRP ring network fault is shortened.

As shown in fig. 4, an embodiment of the present application provides a fault handling device for an MRP ring network, which may be used to implement any step of a fault handling method for an MRP ring network and optional embodiments thereof as shown in fig. 1-3. Referring to fig. 4, the device is applied to an MRM in an MRP ring network, and includes a setting module 210 and a processing module 220.

The setting module 210 is configured to set a primary port of an MRM in the MRP ring network to a Forwarding state and a secondary port to a Blocked state when the MRP ring network is in a ring closed state; the processing module 220 is configured to receive an mrp_linkdown message sent by an MRC when a Port link down event occurs in the MRC of the MRP ring, convert a secondary Port of the MRM from a Blocked state to a Forwarding state according to the mrp_linkdown message, and send an mrp_topolgy change message to the outside through two ports of the MRM, so that each MRC in the MRP ring updates its own network topology information according to the mrp_topolgy change message, and convert the ring closed state recorded by the MRM to a ring open state.

In some embodiments, the processing module 220 is further configured to receive an mrp_linkup message sent by an MRC when a Port link event occurs in the MRC of the MRP ring, convert a secondary Port of the MRM from a Forwarding state to a Blocked state according to the mrp_linkup message, and send an mrp_topiogy change message to the outside through two ports of the MRM, so that each MRC in the MRP ring updates its own network topology information according to the mrp_topiogy change message, and convert the ring open state recorded by the MRM to a ring closed state.

It should be understood that the apparatus or module in the embodiments of the present application may be implemented by software, for example, by a computer program or instruction having the functions described above, and the corresponding computer program or instruction may be stored in a memory inside the terminal, and the processor reads the corresponding computer program or instruction inside the memory to implement the functions described above. Alternatively, the apparatus or module of the embodiments of the present application may be implemented by hardware. Still further, an apparatus or module in an embodiment of the present application may also be implemented by a combination of a processor and software modules.

It should be understood that, for details of processing of the apparatus or the module in the embodiments of the present application, reference may be made to the embodiments shown in fig. 1 to 3 and related expressions of related extended embodiments, and the embodiments of the present application will not be repeated here.

As shown in fig. 5, another fault handling apparatus for an MRP ring network is provided in the embodiments of the present application, where the fault handling apparatus may be used to implement any step of the fault handling method for an MRP ring network and optional embodiments thereof shown in fig. 1-3. Referring to fig. 5, the device is applied to MRC in an MRP ring network, and includes a detection module 310 and a topology updating module 320.

The detection module 310 is configured to send an mrp_linkdown message/an mrp_linkup message to the MRP when a Port link event/a Port link up occurs at a certain ring Port of the MRC, so that the MRM converts a secondary Port from a Blocked state to a Forwarding state according to the mrp_linkdown message, or converts a secondary Port from a Forwarding state to a Blocked state according to the mrp_linkup message, and sends an mrp_toplogychange message; the topology updating module 320 is configured to receive the mrp_topologychange message, and update its own network topology information according to the mrp_topologychange message.

Fig. 6 is a block diagram of a computing device 500 provided in an embodiment of the present application. The computing device 500 includes: processor 510, memory 520, communication interface 530, bus 540.

It should be appreciated that the communication interface 530 in the computing device 500 shown in fig. 6 may be used to communicate with other devices.

Wherein the processor 510 may be coupled to a memory 520. The memory 520 may be used to store the program codes and data. Accordingly, the memory 520 may be a storage unit internal to the processor 510, an external storage unit independent of the processor 510, or a component including a storage unit internal to the processor 510 and an external storage unit independent of the processor 510.

Optionally, computing device 500 may also include a bus 540. The memory 520 and the communication interface 530 may be connected to the processor 510 via a bus 540. Bus 540 may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The bus 540 may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, only one line is shown in fig. 6, but not only one bus or one type of bus.

It should be appreciated that in embodiments of the present application, the processor 510 may employ a central processing unit (central processing unit, CPU). The processor may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate arrays (field programmable gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. Or the processor 510 may employ one or more integrated circuits for executing associated programs to carry out the techniques provided in embodiments of the present application.

The memory 520 may include read only memory and random access memory, and provides instructions and data to the processor 510. A portion of the processor 510 may also include non-volatile random access memory. For example, processor 510 may also store information of the device type.

When the computing device 500 is running, the processor 510 executes computer-executable instructions in the memory 520 to perform the operational steps of the method described above.

It should be understood that the computing device 500 according to the embodiments of the present application may correspond to a respective subject performing the methods according to the embodiments of the present application, and that the above-described other operations and/or functions of the respective modules in the computing device 500 are respectively for implementing the respective flows of the methods of the embodiments, and are not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Embodiments of the present application also provide a computer-readable storage medium having stored thereon a computer program for performing the above-described method when executed by a processor, the method comprising at least one of the aspects described in the above-described embodiments.

Any combination of one or more computer readable media may be employed as the computer storage media of the embodiments herein. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

It should be noted that the embodiments described in this application are only some embodiments of the present application, and not all embodiments. The components of the embodiments of the present application, as generally described and illustrated in the figures, may be arranged and designed in a wide variety of different configurations. Thus, the above detailed description of the embodiments of the present application, provided in the accompanying drawings, is not intended to limit the scope of the application as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, are intended to be within the scope of the present application.

The terms first, second, third, etc. or module a, module B, module C, etc. in the description and in the claims, etc. are used solely for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order, as may be appreciated, if permitted, to interchange particular orders or precedence orders to enable embodiments of the present application described herein to be implemented in orders other than those illustrated or described herein.

In the above description, reference numerals indicating steps are not necessarily meant to be performed as such, but intermediate steps or replaced by other steps may be included, and the order of the steps may be interchanged or performed simultaneously where permitted.

The term "comprising" as used in the description and claims should not be interpreted as being limited to what is listed thereafter; it does not exclude other elements or steps. Thus, it should be interpreted as specifying the presence of the stated features, integers, steps or components as referred to, but does not preclude the presence or addition of one or more other features, integers, steps or components, or groups thereof. Thus, the expression "a device comprising means a and B" should not be limited to a device consisting of only components a and B.

Reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, in the various embodiments of the application, where no special description or logic conflicts exist, the terms and/or descriptions between the different embodiments are consistent and may be mutually referenced, the technical features of the different embodiments may be combined to form a new embodiment according to their inherent logic relationships.

Note that the above is only the preferred embodiments of the present application and the technical principles applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the present application has been described in connection with the above embodiments, the present invention is not limited to the above embodiments, but may include many other equivalent embodiments without departing from the spirit of the present invention, and the present invention is also within the scope of protection.

Claims

1. The fault processing method of the MRP ring network is characterized in that when the MRP ring network is in a ring closed state, a main port of an MRM in the MRP ring network is in a forwarding state, and a secondary port is in a blocking state, and the fault processing method is applied to the MRM, and comprises the following steps:

2. The method as recited in claim 1, further comprising:

3. The method according to claim 2, characterized in that:

in the ring closed state, when the first MRC of the MRP ring network has a port offline event, the method further includes: converting the ring-closed state recorded by the MRM into a ring-open state;

in the ring-open state, when the port on-line event occurs in the first MRC of the MRP ring network, the method further includes: and converting the ring-opening state recorded by the MRM into a ring-closing state.

4. The method of claim 1, wherein the receiving the port offline message sent by the first MRC comprises:

5. The method of claim 2, wherein the receiving the port upload message sent by the first MRC comprises:

6. The fault processing method of MRP ring network, when MRP ring network is in ring closed state, the main port of MRM in MRP ring network is in forwarding state, secondary port is in blocking state, characterized in that, the method is applied in the first MRC where port off-line event/port on-line event occurs, the method includes:

7. The utility model provides a fault handling device of MRP looped netowrk, is applied in the MRP looped netowrk, and when MRP looped netowrk was the ring closure state, MRM's in the MRP looped netowrk main port was in the forwarding state, and the secondary port is in blocking state, and its characterized in that, this device is applied in first MRC, includes:

8. The utility model provides a fault handling device of MRP looped netowrk, is applied in the MRP looped netowrk, and when MRP looped netowrk was the ring closure state, the main port of MRM in the MRP looped netowrk was in the forwarding state, and the secondary port is in the blocking state, and its characterized in that, this device is applied in the MRM, includes:

9. A computing device, comprising:

a processor;

a memory for storing one or more programs;

the one or more programs, when executed by the processor, cause the processor to implement a method of fault handling for an MRP ring network as claimed in any one of claims 1 to 6.

10. A computer readable storage medium, having stored thereon a computer program which, when executed by a computer, implements a method of fault handling of an MRP ring network according to any of claims 1 to 6.