CN106559331B - Message transmission method, device and network system in MSTP (Multi-service transport platform) network - Google Patents
Message transmission method, device and network system in MSTP (Multi-service transport platform) network Download PDFInfo
- Publication number
- CN106559331B CN106559331B CN201510640877.1A CN201510640877A CN106559331B CN 106559331 B CN106559331 B CN 106559331B CN 201510640877 A CN201510640877 A CN 201510640877A CN 106559331 B CN106559331 B CN 106559331B
- Authority
- CN
- China
- Prior art keywords
- root bridge
- port
- root
- mode
- mstp
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
Abstract
A message transmission method, device and system in an MSTP network. The first root bridge sets a root protection function at a second port of the first root bridge, wherein the root protection function is used for indicating the opening state and the blocking state of the second port, and the second port is used for transmitting a message to first network equipment; the first root bridge detects whether a first port receives a message from a second root bridge; the method includes switching the MSTP mode of operation of the first root bridge to a non-MSTP mode when the first port fails to receive a message from the second root bridge within a predetermined time, the first root bridge and the second root bridge are not in the same MST domain, and the second port is placed in the blocking state. By adopting the scheme, when the link between the main root bridge and the standby root bridge fails, root protection can be realized for the non-0 instance, so that double traffic is avoided.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, and a network system for packet transmission in a Multiple Spanning Tree Protocol (MSTP) network.
Background
Spanning Tree Protocol (STP) completes Spanning Tree calculation by transmitting a Protocol message of a Bridge Protocol Data Unit (BPDU) between switches according to information contained in the BPDU, thereby achieving a function of eliminating a two-layer network loop. When the network fails, the spanning tree protocol recalculates the chokepoints and releases the redundant links to restore network traffic.
When the network structure changes, the Rapid Spanning Tree Protocol (RSTP) can converge the network more quickly, thereby solving the problem of time delay. The RSTP sets two roles of a replacement port and a backup port for fast switching for the bridge port and the designated port, and the replacement port and the backup port enter a forwarding state without time delay when the bridge port and the designated port fail.
MSTP defines the concept of Multiple Spanning Tree (MST) regions, which divides a switching network into Multiple MST regions, typically, a region-wide switch is divided into the same MST region. In the MST domain, instances (instances) are divided according to different Virtual Local Area Networks (VLANs), and a spanning tree is calculated for each Instance. Therefore, Multiple Spanning trees can be formed in each domain, each Spanning Tree is called a Multiple Spanning Tree Instance (MSTI), a VLAN mapping table is set to link the VLAN and the MSTI, different MSTIs can forward the flow of the VLAN in the Instance according to the calculated Spanning Tree topology, and load balancing of Multiple VLAN data can be achieved through different topologies of the Spanning trees.
In the MSTP networking, the problem of double flow is avoided by configuring a main root bridge and a standby root bridge and configuring a root protection mode on the standby root bridge. However, in some practical application scenarios, this root protection approach cannot solve the problem of duplicate traffic existing in non-0 instances.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method, an apparatus, and a system for packet transmission in an MSTP network, so as to solve a problem that when a link between a primary root bridge and a standby root bridge fails, root protection for a non-0 instance cannot be effective, resulting in duplicate traffic.
The technical scheme provided by the embodiment of the invention is as follows.
In a first aspect, a method for transmitting a packet in an MSTP network is provided, where the method is applied to a network including a first root bridge and a second root bridge, a first port of the first root bridge is connected to the second root bridge through a link, the first root bridge and the second root bridge operate in an MSTP mode, a downstream of the first root bridge and the second root bridge includes a first network device, the first network device is configured to receive the packet from the first root bridge and the second root bridge, the first root bridge sets a root protection function at a second port of the first root bridge, the root protection function is configured to indicate an open state and a blocked state of the second port, and the second port is configured to transmit the packet to the first network device; the method comprises the following steps:
the first root bridge detecting whether the first port receives a message from the second root bridge;
when the first port fails to receive a message from the second root bridge within a predetermined time, the first root bridge and the second root bridge are not in the same MST domain, and the second port is placed in the blocking state, the first root bridge switches the running MSTP mode to a non-MSTP mode.
In a first possible implementation manner of the first aspect, the non-MSTP mode is an RSTP mode or an STP mode.
With reference to the foregoing first aspect, or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the root protection function is configured to indicate an open state and a blocking state of the second port, and includes:
and when the priority of the BPDU message received by the second port is higher than that of the BPDU message stored by the first root bridge, the second port is placed in the blocking state.
In a third possible implementation manner of the first aspect, the first network device runs an RSTP mode or an STP mode.
In a fourth possible implementation manner of the first aspect, the first network device runs the MSTP mode, and the first network device and the first root bridge are not in the same MST domain or the first network device and the second root bridge are not in the same MST domain.
In a second aspect, a first root bridge device is provided, where a first port of the first root bridge device is connected to a second root bridge device through a link, the first root bridge device and the second root bridge device operate in an MSTP mode, a first network device is included downstream of the first root bridge device and the second root bridge device, and the first network device is configured to receive packets from the first root bridge device and the second root bridge device, respectively, where the first root bridge device includes:
a setting unit, configured to set a root protection function at a second port of the first root bridge device, where the root protection function is used to indicate an open state and a blocking state of the second port, and the second port is used to transmit the packet to the first network device;
a detecting unit, configured to detect whether the first port receives a message from the second bridge device;
a switching unit, configured to switch the MSTP mode in which the first root bridge device operates to a non-MSTP mode when the first port fails to receive a message from the second root bridge device within a predetermined time, the first root bridge device and the second root bridge device are not in the same MST domain, and the second port is placed in the blocking state
In a first possible implementation manner of the second aspect, the non-MSTP mode is an RSTP mode or an STP mode.
With reference to the second aspect, or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the root protection function is configured to indicate an open state and a blocking state of the second port, and includes:
and when the priority of the BPDU message received by the second port is higher than that of the BPDU message stored by the first root bridge device, the second port is placed in the blocking state.
In a third possible implementation manner of the second aspect, the first network device runs an RSTP mode or an STP mode.
In a fourth possible implementation manner of the second aspect, the first network device runs the MSTP mode, and the first network device and the first root bridge device are not in the same MST domain or the first network device and the second root bridge device are not in the same MST domain.
In a third aspect, a network system is provided, where the network system includes the first root bridge device in the second aspect or any one of the possible implementation manners of the second aspect.
In a possible implementation manner of the first, second or third aspect, the first bridge is used as a standby root bridge, and the second bridge is used as a main root bridge. Optionally, the main root bridge and the standby root bridge are interchangeable. That is, the first bridge acts as the primary root bridge and the second bridge acts as the backup root bridge.
According to the technical scheme of the embodiment of the invention, when the link between the main root bridge and the standby root bridge fails, the working mode of the standby root bridge is switched from the MSTP mode to the non-MSTP mode, so that root protection is realized on a non-0 instance, and double traffic is avoided.
Drawings
Fig. 1 is a flowchart of a message transmission method in an MSTP network according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a first scenario structure according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a second scenario structure according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a third scenario according to the embodiment of the present invention;
FIG. 5 is a diagram illustrating a fourth scenario structure according to an embodiment of the present invention;
FIG. 6 is a schematic structural diagram of a first root bridge device according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a hardware structure of a first root bridge device according to an embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a message transmission method, a message transmission device and a message transmission system in an MSTP (multi-spanning tree protocol) network, which are used for realizing root protection on a non-0 instance and avoiding duplicate traffic when a link between a main root bridge and a standby root bridge fails.
The following are detailed descriptions of the respective embodiments.
In order to make the objects, features and advantages of the present invention more obvious and understandable, the technical solutions in the embodiments of the present invention will be clearly described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the embodiments described below are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "comprising" and "having" are not exclusive. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may include other steps or elements not expressly listed.
Fig. 1 is a flowchart of a message transmission method in an MSTP network according to an embodiment of the present invention. As shown in fig. 1, the message transmission method in the MSTP network is applied to a network including a first root bridge and a second root bridge. And the first port of the first root bridge is connected with the second root bridge through a link, and the first root bridge and the second root bridge operate in an MSTP mode. The downstream of the first root bridge and the second root bridge comprises a first network device, and the first network device is used for receiving messages from the first root bridge and the second root bridge respectively.
In this embodiment, the second bridge acts as the primary root bridge. Alternatively, the master root bridge is a switch or a router.
The first root bridge is used as a standby root bridge, and optionally, the standby root bridge is a switch or a router. The standby root bridge comprises a first port, and the first port is connected with the main root bridge through a link. The message may be a data traffic corresponding to a service. The main root bridge and the standby root bridge respectively receive data traffic and forward the data traffic through first network equipment in the downstream of the main root bridge and the standby root bridge. The first network device may receive data traffic from the primary root bridge, and the first network device may also receive data traffic from the backup root bridge. Optionally, the first network device may be a switch or a router. The working mode of the main root bridge and the standby root bridge adopts an MSTP mode, namely MSTP is operated on the main root bridge and the standby root bridge. The main root bridge and the standby root bridge are respectively configured with an example 0 and a non-0 example. Therein, instance 0 is mandatory. In addition to instance 0, each switch can be configured with 64 non-0 instances at most, and users can allocate 1-4096 VLANs to different instances (instance 0-instance 64) according to requirements.
For example, referring to fig. 2, PE1 is a primary root bridge and may correspond to the second root bridge in the method of the embodiments, and PE2 is a backup root bridge and may correspond to the first root bridge in the method of the embodiments. Alternatively, PE1 and PE2 are switches or routers. PE1 receives data traffic through port P0 and PE2 through port P12, respectively, and forwards the data traffic through S1 in the downstream of PE1 and PE 2. Of these, port P0 and port P12 are non-MSTP ports for receiving data traffic. S1 corresponds to the first network device in the method of the embodiment. S1 may receive data traffic from PE1 through port P5, and S1 may also receive data traffic from PE2 through port P7. S1 sends out data traffic through port P6. Alternatively, S1 may be a switch or a router. The operation mode of PE1 and PE2 adopts MSTP mode. PE1 and PE2 configure instance 0 and non-0 instances, respectively. The port P1 of the PE1 and the port P11 of the PE2 are connected by a link, and a root protection function is configured at the port P10 of the PE 2. The root protection function is to indicate an open state and a blocked state of the second port. Specifically, PE2 may block port P10 by calling the Root-protection function of STP, RSTP, or MSTP. The Root-protection function specifically refers to: for a specific port with Root-protection set, its port role can only be maintained as the specific port. Once a BPDU message with a higher priority than the BPDU message stored by the first root bridge is received on such a port, the status of the port is set to discard (blocking) status, and the message is not forwarded. For example, when the priority of the BPDU message received by the port P10 is higher than that of the BPDU message stored in the PE2, the port P10 is set to the Discarding state.
Optionally, downstream of PE1 and PE2 may include S2 and S3. The operation modes of S2 and S3 adopt an MSTP mode. S2 and S3 configure instance 0 and non-0 instances, respectively. Alternatively, S2 and S3 may be switches or routers. S2 is connected to port P2 of PE1 via port P3 and to port P5 of S1 via port P4. S3 is connected to port P10 of PE2 via port P9 and to port P7 of S1 via port P8.
For example, referring to fig. 2, a root protection function is configured at port P10 of PE2, and the root protection function is automatically configured by PE2 through MSTP computation. Under normal operating conditions, port P10 can receive BPDU messages with higher priority. When the priority of the BPDU message received by the port P10 is higher than that of the BPDU message stored by the PE2, the port P10 is placed in the Discarding state, thereby causing the root protection to be effective. According to the MSTP calculation, both instance 0 and instance 1 of PE2 are blocked at port P7 of S1. Accordingly, the data traffic of the traffic corresponding to example 0 and example 1, respectively, is blocked at port P7 of S1. Therefore, S1 only receives data traffic from the PE 1. In the embodiment of the present invention, the example 1 in the non-0 example is used for description, and it should be understood that the scenario shown in the embodiment of the present invention may also be applied to other non-0 examples, and the kind of the applied non-0 example is not limited to 1.
For example, fig. 3 is a diagram of another scene structure in the embodiment. Referring to fig. 3, assume that PE1 fails, resulting in PE1 failing to receive data traffic from the outside and failing to forward data traffic to S1. This will result in S1 not receiving data traffic from PE 1. Meanwhile, as the PE1 fails, the port P10 with root protection function on the PE2 cannot receive the BPDU message with higher priority from the PE 1. Thus, port P10 is in an open state and the root protection fails. At this time, the port P10 can forward data traffic downward, so the S1 device only receives data traffic from the PE 2.
For example, fig. 4 is a diagram of another scene structure in the embodiment. Referring to fig. 4, port P1 of PE1 and port P11 of PE2 are connected by a link, and a root protection function is configured at port P10 of PE 2. PE1 and PE2 run MSTP mode. Because of the presence of the link, PE1 and PE2 may be considered to be disposed in the same MST domain. The MST domain is composed of a plurality of switches in the switching network and network segments among the switches. These switches all have MSTP enabled, have the same domain identification, the same VLAN to spanning tree mapping configuration, and the same MSTP revision level configuration, and are physically link connected. S1, which is located downstream of PE1 and PE2, is set to run RSTP mode, STP mode, or MSTP mode. Wherein when the S1 runs the MSTP mode, the S1 and the PE1 are not in the same MST domain, or the S1 and the PE2 are not in the same MST domain. When the link fails, PE1 and PE2 are partitioned into two MST domains, MST1 and MST 2. For example 0, since example 0 can be propagated in different MST domains, the port P10 with root protection function on the PE2 can receive a BPDU message with higher priority, the port P10 is in a blocking state, and root protection is effective. Therefore, the data traffic of the traffic corresponding to the example 0 is blocked at the port P10, and the S1 receives only the data traffic from the PE 1. For the non-0 example, example 1 is taken as an example. Since instance 1 cannot propagate in different MST domains, port P10 with root protection function on PE2 cannot receive BPDU message with higher priority, port P10 is in open state, and root protection fails. Therefore, the data traffic of the service corresponding to the example 1 is not blocked at the port P10, and the port P10 can forward the data traffic of the service corresponding to the example 1 downwards. Thus, for example 1, S1 is able to receive data traffic from PE1 and PE2, resulting in duplicate traffic.
In order to avoid the generation of the duplicate traffic, referring to the flowchart shown in fig. 1, a first root bridge sets a root protection function at a second port of the first root bridge, where the root protection function is used to indicate an open state and a blocking state of the second port, and the second port is used to transmit the packet to the first network device, and the first root bridge may perform the following steps:
s102, the first root bridge detects whether the first port receives a message from the second root bridge;
s104, when the first port fails to receive the message from the second root bridge within the preset time, the first root bridge and the second root bridge are not in the same MST domain, and the second port is placed in the blocking state, the first root bridge switches the running MSTP mode into the non-MSTP mode.
In an embodiment, the first root bridge sets a root protection function at the second port of the first root bridge, the root protection function being used to indicate the open state and the blocking state of the second port. Specifically, the first Root bridge may block the second port by calling a Root-protection function of STP, RSTP, or MSTP. The Root-protection function specifically refers to: for a specific port with Root-protection set, its port role can only be maintained as the specific port. Once a BPDU message with a higher priority than the BPDU message stored by the first root bridge is received at such a port, the port status is set to discard (blocking) status, and the message is not forwarded. For example, when the priority of the BPDU message received by the second port is higher than the priority of the BPDU message stored by the first root bridge, the second port is placed in the Discarding state. The second port is configured to transmit the packet to the first network device. The message may be a data traffic corresponding to a service. The first root bridge receives data traffic from outside and transmits the data traffic to the first network device through a second port.
In an embodiment, the first port of the first root bridge is connected to the second root bridge by a link, and the first root bridge and the second root bridge operate MSTP mode. And when the link fails, the first root bridge acquires the information that the link fails. Specifically, the first root bridge determines whether the link fails by detecting whether the first port receives a message from the second root bridge. And when the first port fails to receive the message from the second root bridge within the preset time, the link is failed.
In an embodiment, when the first port fails to receive a message from the second root bridge within a predetermined time, it is determined that a link fails, and the first root bridge obtains information that the link fails. Then, when it is determined that the first and second bridges are not in the same MST domain and the second port is placed in the blocking state, the first bridge switches the running MSTP mode to a non-MSTP mode. Alternatively, the switching process may be automatically performed by the first root bridge. When the working mode of the first root bridge is switched from the MSTP mode to the non-MSTP mode, for instance 0, the second port with the root protection function on the first root bridge can receive the BPDU message with the priority higher than that of the BPDU message stored by the first root bridge, and the second port is in a blocking state, so that the root protection takes effect. Thus, the data traffic of the traffic corresponding to instance 0 is blocked at the second port, and the first network device receives only data traffic from the second root bridge. For the non-0 example, the working mode of the first root bridge is changed into a non-MSTP mode, so that the working mode of the first root bridge is no longer in the MSTP mode, and the load balancing function is lost. Thus, the state of all non-0 instances inherits the state of instance 0. That is, the blocking point for instance 0 is on the root protection port since the root protection is in effect for instance 0; the non-0 instance inherits the blocking state of instance 0 so that the root protection also takes effect on non-0 instances, resulting in the blocking point for non-0 instances also being on the root protection port. The operating mode of the first root bridge is changed to a non-MSTP mode. For the non-0 example, the second port with the root protection function on the first root bridge can receive the BPDU message with higher priority, and the second port is in a blocking state, so that the root protection takes effect. Therefore, the data traffic of the service corresponding to the non-0 instance is blocked at the second port, and the first network device only receives the data traffic from the second root bridge. When the link between the main root bridge and the standby root bridge fails, root protection is realized for the non-0 instance, and double traffic is avoided.
Optionally, the main root bridge and the standby root bridge are interchangeable. That is, the first bridge serves as a primary root bridge, the second bridge serves as a backup root bridge, and the second bridge is provided with root protection.
For example, referring to fig. 5, port P11 of PE2 is connected to PE1 via a link, and PE1 and PE2 operate MSTP mode. When port P11 fails to receive the message from PE1 within a predetermined time, it indicates that the link has failed. PE2 obtains information that the link failed. And the PE2 determines that the PE2 and the PE1 are not in the same MST domain according to the information that the link fails, and switches the working mode of the PE2 from the MSTP mode to the non-MSTP mode when the port P10 is placed in the blocking state. When the working mode of PE2 is switched from MSTP mode to non-MSTP mode, for instance 0, port P10 with root protection function on PE2 can receive BPDU message with higher priority, port P10 is in blocking state, and root protection takes effect. Therefore, the data traffic of the traffic corresponding to the example 0 is blocked at the port P10, and the S1 receives only the data traffic from the PE 1. For non-0 examples, such as example 1. Since the operation mode of PE2 changes to non-MSTP mode, the operation mode of PE2 is no longer MSTP mode, and the load balancing function is lost. Thus, the state of instance 1 inherits the state of instance 0. That is, the blocking point for instance 0 is on the root protection port since the root protection is in effect for instance 0; instance 1 inherits the blocking state of instance 0 so that the root protection also takes effect on non-0 instances, resulting in the blocking point for non-0 instances also being on the root protection port. The operating mode of PE2 becomes a non-MSTP mode. For example 1, a port P10 with root protection function on PE2 can receive a BPDU message with higher priority than the BPDU message stored by the first root bridge, and port P10 is in a blocking state, and root protection is effective. Therefore, the data traffic of the service corresponding to the example 1 is blocked at the port P10, and the S1 only receives the data traffic from the PE 1. When the link between the main root bridge and the standby root bridge fails, root protection is realized for the non-0 instance, and double traffic is avoided.
In the prior art, when a link between a main root bridge and a standby root bridge fails, data traffic of a service corresponding to a non-0 instance is not blocked at a second port having a root protection function, and at this time, the second port can forward the data traffic of the service corresponding to the non-0 instance downwards. Thus, for the non-0 instance, the first network device can receive data traffic from the first and second root bridges, resulting in duplicate traffic.
The method for transmitting a message in a multiple spanning tree protocol MSTP network provided by this embodiment. And the standby root bridge acquires the information that the link fails. And according to the information that the link fails, determining that the first root bridge and the second root bridge are not in the same MST domain, and when the second port is placed in the blocking state, switching the running MSTP mode of the first root bridge into a non-MSTP mode. Thereby ensuring that non-0 instances inherit the blocking state of instance 0 and avoiding the generation of duplicate traffic.
Optionally, the non-MSTP mode is an RSTP mode or an STP mode.
For example, when the operating mode of the first root bridge is switched from the MSTP mode to the RSTP mode or the STP mode, the instance 0 and the non-0 instances are not distinguished in the RSTP mode or the STP mode, and the states of all the non-0 instances inherit the state of the instance 0. That is, the blocking point for instance 0 is on the root protection port since the root protection is in effect for instance 0; the non-0 instance inherits the blocking state of instance 0 so that the root protection also takes effect on non-0 instances, resulting in the blocking point for non-0 instances also being on the root protection port.
Optionally, the root protection function is configured to indicate an open state and a blocking state of the second port, and includes: and when the priority of the BPDU message received by the second port is higher than that of the BPDU message stored by the first root bridge, the second port is placed in the blocking state.
For example, a root protection function is configured at the second port of the first root bridge. The root protection function is to indicate an open state and a blocked state of the second port. Once the second port receives a BPDU message with a higher priority than the BPDU message stored by the first root bridge, the port status is set to the blocking status, and the message is not forwarded.
Optionally, the first network device operates in an RSTP mode or an STP mode.
Optionally, the first network device operates in the MSTP mode, and the first network device and the first root bridge are not in the same MST domain or the first network device and the second root bridge are not in the same MST domain.
For example, the first network device may receive data traffic from the primary root bridge, and the first network device may also receive data traffic from the standby root bridge. Optionally, the first network device may be a switch or a router. The operating mode of the first network device may adopt an MSTP mode, an RSTP mode, or an STP mode, and when the operating mode of the first network device adopts the MSTP mode, the first network device and the standby root bridge or the primary root bridge are not in the same MST domain. Specifically, the main root bridge and the standby root bridge are connected by a link, and when the link has no fault, the main root bridge and the standby root bridge are in the same MST domain, so that when the operating mode of the first network device adopts the MSTP mode, the first network device and the standby root bridge or the main root bridge are not in the same MST domain. Thereby causing the primary root bridge and the standby root bridge to not be in the same MST domain when the link fails.
According to the scheme of the embodiment, the standby root bridge acquires the information that the link fails, and switches the working mode of the standby root bridge from the MSTP mode to the non-MSTP mode when the main root bridge and the standby root bridge are not in the same MST domain and the port with the root protection function is in the blocking state according to the information that the link fails. Thereby ensuring that non-0 instances inherit the blocking state of instance 0 and avoiding the generation of duplicate traffic.
Fig. 6 is a schematic structural diagram of a first root bridge device 600 according to an embodiment of the present invention. The first root bridge device shown in fig. 6 may perform the corresponding steps performed by the first root bridge in the method of the above-described embodiment. And the first port of the first bridge device is connected with the second bridge device through a link. The first and second root bridge devices operate in MSTP mode. The first root bridge device and the second root bridge device include a first network device downstream. The first network device is configured to receive packets from the first root bridge device and the second root bridge device, respectively. Optionally, the first root bridge device is a switch or a router. As shown in fig. 6, the first root bridge device 600 includes a setting unit 602, a detecting unit 604 and a switching unit 606:
the setting unit 602 is configured to set a root protection function at a second port of the first root bridge device, where the root protection function is configured to indicate an open state and a blocking state of the second port, and the second port is configured to transmit the packet to the first network device;
the detecting unit 604 is configured to detect whether the first port receives a message from the second root bridge device;
the switching unit 606 is configured to switch the MSTP mode in which the first root bridge device operates to the non-MSTP mode when the first port fails to receive the message from the second root bridge device within a predetermined time, the first root bridge device and the second root bridge device are not in the same MST domain, and the second port is placed in the blocking state.
Optionally, the non-MSTP mode is an RSTP mode or an STP mode.
Optionally, the root protection function is configured to indicate an open state and a blocking state of the second port, and includes: and when the priority of the BPDU message received by the second port is higher than that of the BPDU message stored by the first root bridge device, the second port is placed in the blocking state.
Optionally, the first network device operates in an RSTP mode or an STP mode.
Optionally, the first network device operates the MSTP mode, and the first network device and the first root bridge device are not in the same MST domain or the first network device and the second root bridge device are not in the same MST domain.
The first root bridge device shown in fig. 6 may perform the corresponding steps performed by the first root bridge in the method of the above-described embodiment. The method and the device solve the problem that when a link between a root bridge and a standby root bridge fails, root protection for a non-0 instance cannot be effective, and double traffic is caused.
Fig. 7 is a schematic diagram of a hardware structure of a first root bridge device 700 according to an embodiment of the present invention. The first root bridge device shown in fig. 7 may perform the corresponding steps performed by the first root bridge in the method of the above-described embodiment. Optionally, the first root bridge device is a switch or a router.
As shown in fig. 7, the first bridge device 700 includes a processor 701, a memory 702, an interface 703 and a bus 704, where the interface 703 may be implemented in a wireless or wired manner, specifically, may be an element such as a network card, and the processor 701, the memory 702 and the interface 703 are connected by the bus 704.
The memory 702 stores program codes and transmits the program codes to the processor 701.
The interface 703 includes a first port and a second port. The first port is connected to a second bridge device via a link. The first and second root bridge devices operate in MSTP mode. A first network device is included downstream of the first and second bridge devices. The first network device is configured to receive packets from the first root bridge device and the second root bridge device, respectively.
The processor 701 is configured to set a root protection function at a second port of the first root bridge device, where the root protection function is configured to indicate an open state and a blocking state of the second port, and the second port is configured to transmit the packet to the first network device;
the processor 701 is further configured to detect whether the first port receives a message from the second root bridge device;
the processor 701 is further configured to switch the MSTP mode in which the first root bridge device operates to a non-MSTP mode when the first port fails to receive a message from the second root bridge device within a predetermined time, the first root bridge device and the second root bridge device are not in the same multiple spanning tree MST domain, and the second port is placed in the blocking state.
Optionally, the non-MSTP mode is an RSTP mode or an STP mode.
Optionally, the root protection function is configured to indicate an open state and a blocking state of the second port, and includes: the second port is placed in the blocking state when the priority of the BPDU messages received by the second port is higher than the priority of the BPDU messages stored in the memory 702.
Optionally, the first network device operates in an RSTP mode or an STP mode.
Optionally, the first network device operates the MSTP mode, and the first network device and the first root bridge device are not in the same MST domain or the first network device and the second root bridge device are not in the same MST domain.
The first root bridge device shown in fig. 7 may perform the corresponding steps performed by the first root bridge in the method of the above-described embodiment. The method and the device solve the problem that when a link between a root bridge and a standby root bridge fails, root protection for a non-0 instance cannot be effective, and double traffic is caused.
In addition, the embodiment of the invention also provides a system for MSTP root protection damage. The system may include the first root bridge device provided in the embodiment corresponding to fig. 6 or fig. 7, which is not described herein again.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a Random Access Memory (RAM), a Read-only memory (ROM), an Erasable programmable Read-only memory (EPROM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (9)
1. A message transmission method in a Multiple Spanning Tree Protocol (MSTP) network is characterized in that the method is applied to a network comprising a first root bridge and a second root bridge, a first port of the first root bridge is connected with the second root bridge through a link, the first root bridge and the second root bridge operate in an MSTP mode, a first network device is arranged at the downstream of the first root bridge and the second root bridge, the first network device is used for receiving messages from the first root bridge and the second root bridge, the first root bridge is provided with a root protection function at a second port of the first root bridge, the root protection function is used for indicating an open state and a blocking state of the second port, and the second port is used for transmitting the messages to the first network device; the method comprises the following steps:
the first root bridge detecting whether the first port receives a message from the second root bridge;
switching the MSTP mode of operation of the first root bridge to a non-MSTP mode when the first port fails to receive a message from the second root bridge within a predetermined time, the first root bridge and the second root bridge are not in the same multiple spanning tree MST domain, and the second port is placed in the blocking state;
wherein the root protection function is configured to indicate an open state and a blocked state of the second port, and includes: and when the priority of the BPDU message received by the second port is higher than that of the BPDU message stored by the first root bridge, the second port is set in the blocking state.
2. The method of claim 1,
the non-MSTP mode is a Rapid Spanning Tree Protocol (RSTP) mode or a Spanning Tree Protocol (STP) mode.
3. The method of claim 1,
the first network device operates in an RSTP mode or an STP mode.
4. The method of claim 1, wherein the first network device runs the MSTP mode,
the first network device and the first root bridge are not in the same MST domain or the first network device and the second root bridge are not in the same MST domain.
5. A first root bridge device, a first port of the first root bridge device being connected to a second root bridge device by a link, the first root bridge device and the second root bridge device operating in MSTP mode, a first network device being included downstream of the first root bridge device and the second root bridge device, the first network device being configured to receive packets from the first root bridge device and the second root bridge device, respectively, the first root bridge device comprising:
a setting unit, configured to set a root protection function at a second port of the first root bridge device, where the root protection function is configured to indicate an open state and a blocking state of the second port, and the second port is configured to transmit the packet to the first network device, where the root protection function is configured to indicate the open state and the blocking state of the second port, and includes: when the priority of a Bridge Protocol Data Unit (BPDU) message received by the second port is higher than that of a BPDU message stored by the first root bridge device, the second port is placed in the blocking state;
a detecting unit, configured to detect whether the first port receives a message from the second bridge device;
a switching unit, configured to switch the MSTP mode in which the first root bridge device operates to a non-MSTP mode when the first port fails to receive a message from the second root bridge device within a predetermined time, the first root bridge device and the second root bridge device are not in the same multiple spanning tree MST domain, and the second port is placed in the blocking state.
6. A first root bridge apparatus according to claim 5,
the non-MSTP mode is a Rapid Spanning Tree Protocol (RSTP) mode or a Spanning Tree Protocol (STP) mode.
7. A first root bridge apparatus according to claim 5,
the first network device operates in an RSTP mode or an STP mode.
8. A first root bridge apparatus according to claim 5,
the first network device operates the MSTP mode, and the first network device and the first root bridge device are not in the same MST domain or the first network device and the second root bridge device are not in the same MST domain.
9. A network system, characterized in that it comprises a first root bridge device according to any of claims 5 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510640877.1A CN106559331B (en) | 2015-09-30 | 2015-09-30 | Message transmission method, device and network system in MSTP (Multi-service transport platform) network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510640877.1A CN106559331B (en) | 2015-09-30 | 2015-09-30 | Message transmission method, device and network system in MSTP (Multi-service transport platform) network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106559331A CN106559331A (en) | 2017-04-05 |
| CN106559331B true CN106559331B (en) | 2020-01-21 |
Family
ID=58417773
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510640877.1A Active CN106559331B (en) | 2015-09-30 | 2015-09-30 | Message transmission method, device and network system in MSTP (Multi-service transport platform) network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106559331B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111464436B (en) * | 2020-04-03 | 2022-02-01 | 中电科航空电子有限公司 | Method for solving single-port loop of RSTP (remote station transfer protocol) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101296150A (en) * | 2007-04-29 | 2008-10-29 | 中兴通讯股份有限公司 | Method and device for implementing service intercommunication by ZESR and STP mixed networking |
| CN101567892A (en) * | 2009-06-04 | 2009-10-28 | 华为技术有限公司 | Method and device for realizing MSTP multiprocess |
| CN102724096A (en) * | 2012-06-26 | 2012-10-10 | 华为技术有限公司 | Mixed ring network protection method and network equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4397292B2 (en) * | 2004-07-09 | 2010-01-13 | 富士通株式会社 | Control packet loop prevention method and bridge device using the same |
-
2015
- 2015-09-30 CN CN201510640877.1A patent/CN106559331B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101296150A (en) * | 2007-04-29 | 2008-10-29 | 中兴通讯股份有限公司 | Method and device for implementing service intercommunication by ZESR and STP mixed networking |
| CN101567892A (en) * | 2009-06-04 | 2009-10-28 | 华为技术有限公司 | Method and device for realizing MSTP multiprocess |
| CN102724096A (en) * | 2012-06-26 | 2012-10-10 | 华为技术有限公司 | Mixed ring network protection method and network equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106559331A (en) | 2017-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10594512B2 (en) | Access network dual path connectivity | |
| EP1994694B1 (en) | System and method for preventing loops in the presence of control plane failures | |
| US9608903B2 (en) | Systems and methods for recovery from network changes | |
| US8619785B2 (en) | Pre-computing alternate forwarding state in a routed ethernet mesh network | |
| US8743677B2 (en) | VPLS N-PE redundancy with STP isolation | |
| CN101557343B (en) | Detecting and protecting method of double-layer loop in VRRP topological network | |
| EP2689561B1 (en) | Directing traffic in an edge network element operable to perform layer 2 data forwarding and supporting any of various spanning tree protocols | |
| CN104980372A (en) | Relay System And Switching Device | |
| CN104753828A (en) | SDN controller, data central system and route connection method | |
| WO2013112472A1 (en) | Redundant network connections | |
| US9641396B2 (en) | Packet processing method and system | |
| CN112491700A (en) | Network path adjusting method, system, device, electronic equipment and storage medium | |
| US20140092725A1 (en) | Method and first network node for managing an ethernet network | |
| US9413642B2 (en) | Failover procedure for networks | |
| CN111092822A (en) | Method for balancing pw linear protection forwarding load of vpls | |
| CN112995002B (en) | Switch ring network design method, switch and storage medium | |
| CN106559331B (en) | Message transmission method, device and network system in MSTP (Multi-service transport platform) network | |
| JP4467500B2 (en) | Network relay device | |
| US8514746B1 (en) | Priority inversion with spanning tree protocol to trigger path switching | |
| CN107995111B (en) | Service forwarding method, link change notification method, convergence device and access device | |
| CN109347734A (en) | A kind of file transmitting method, device, the network equipment and computer-readable medium | |
| WO2016061943A1 (en) | Method and apparatus for implementing spanning tree protocol protection switching, and computer storage medium | |
| US10673687B2 (en) | Monitoring apparatus, relay apparatus, RPL decision method, and non-transitory computer readable medium storing program | |
| US9160626B2 (en) | Method and apparatus for object grouping and state modeling for application instances | |
| WO2018006711A1 (en) | Service processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |