Method for processing failure in MRP (Media Redundancy Protocol) looped network and MRP looped network

Abstract

The invention relates to a method for processing a failure in an MRP (Media Redundancy Protocol) looped network and an MRP looped network. The MRP looped network comprises a media redundancy management (MRM) node, a plurality of media redundancy client (MRC) nodes and a link connecting the nodes. The method for processing the failure in the MRP looped network comprises the steps: after the MRC nodes, a link among the MRC nodes or links between the MRM node and the MRC nodes generate the failures, the MRM node also generates a failure; after the failures generated by the MRC nodes, THE link among the MRC nodes or THE links between the MRM node and the MRC nodes are recovered, the failure of the MRM node is recovered and the MRM node is re-started; and the MRM node sends a topological state changing frame in a process of restarting. In the process of re-starting the MRM node, the topological state changing frame is sent to ensure that the MRC nodes can be used for emptying operations of a filter data base (FDB), through address learning and service forwarding, and the communication is carried out through the recovered failure links again, the MRC nodes can carry out normal communication under the condition of generating multiple failures.

Description

technical field [0001] The present invention relates to the technical field of MRP ring network, in particular, relates to a method for dealing with faults in the MRP ring network and the corresponding MRP ring network. Background technique [0002] MRP (Media Redundancy Protocol, Media Redundancy Protocol) is designed for faults in a single switch or a single switch link in a ring network. [0003] The MRP ring network consists of one MRM and multiple MRCs. Both MRM and MRC have the function of switches. Various Ethernet services can enter the MRP ring network through MRM or MRC connections. [0004] Such as figure 1 As shown, the composition of the MRP ring network includes: an MRM node 101, a plurality of MRC nodes 102, terminal nodes 103 connected to the ring network and link cables 104 connecting the nodes, wherein: [0005] The MRM node 101 is a media redundancy management node. In the normal working state of each ring network, there must be one and only one ...

AI Technical Summary

Problems solved by technology

[0086] Step 605, because the internal FDBs of MRC 0 and MRC 1 have not been cleared (because NO_TC = 1, MRM has not sent a topology state change frame to let each node clear the filter database FDB), the previous service forwarding path via MRM is still reserved (ie Figure 7 links 706, 707, and 708), while the secondary port of MRM is already in the BLOCKED 704 state, and services cannot pass through (as shown by the dotted link 707); therefore, although the physical connection of the ring has been restored, MRC 0 and MRC 1 However, there is still no communication between them, such as Figure 7 shown

Images