CN1997002B - multiple spanning tree protocol compatible method, system and related switch - Google Patents

Abstract

The invention provides a method, a system and a related exchanger compatible with a multiple spanning tree protocol.A checking module is provided between an IEEE standard multiple spanning tree module and an Ethernet driver module, and the checking module is used for executing a receiving checking program and a transmitting checking program. The checking module, the IEEE standard multiple spanning tree module and the Ethernet driver module are arranged in the exchanger. Receiving the bridge protocol data unit by the checking module, executing a receiving checking program to the bridge protocol data unit when the bridge protocol data unit is from the Ethernet driver module, and executing a transmitting checking program to the bridge protocol data unit when the bridge protocol data unit is from the IEEE standard multiple spanning tree module. The invention can ensure the compatible operation of the data packet among different switches.

Description

Multiple spanning tree protocol compatible method, system and related switch

technical field

The present invention relates to a method for operating multiple spanning tree protocols (multiple spanning tree protocol, MSTP), in particular to a method suitable for operation between different MSTPs.

Background technique

The commonly known spanning tree protocol (STP) refers to a link management protocol based on the IEEE802.1 standard, and its function is to control the status of each bridge device in the network. The use of the expanded tree protocol can reduce the situation of repeated or redundant network paths (path), and effectively avoid unnecessary loops (loop). The data transmitted in the network is carried out in the form of packets, and the device for filtering and transferring packets in different local area networks (LAN) in the network is a switch.

Due to the rapid development of network technology, when a physical local area network is divided into multiple virtual local area networks (virtual LAN, VLAN), the single expansion tree protocol often cannot properly calculate the network topology (topology) that meets each virtual local area network. Therefore, the Multiple Spanning Tree Protocol (MSTP) came into being, that is to say, the multiple topology of the network can be calculated by using the MSTP. The Multiple Spanning Tree Protocol operates in units of regions, and switches in the same region have the same multiple spanning tree setting parameters. Once a zone is formed, the zone will be treated as an integrated large switch to switches outside the zone.

However, the Multiple Spanning Tree Protocol may be formulated based on different standards. For example, IEEE 802.1 standard and Cisco standard (Cisco standard). Therefore, switches conforming to the IEEE 802.1 standard and switches conforming to the Cisco standard may not be compatible with each other. Please refer to Fig. 1a-Fig. 1c, assume that there are switches 100, 102 and 104 in the network environment, switch 102 is a Cisco switch (conforming to Cisco standard multiple spanning tree protocol), and switch 104 is a standard switch (conforming to IEEE standard multiple spanning tree protocol). Spanning Tree Protocol). If the Cisco switch 102 and the standard switch 104 are set to the same area, the ideal state should form an area as shown in 108, and the Cisco switch 102 and the standard switch 104 should form a virtual switch 106, such as Figure 1b shows. However, because the Cisco switch 102 and the standard switch 104 are not compatible, after actual operation, as shown in FIG. 1c, the Cisco switch 102 forms an area 110, and the standard switch 104 forms an area 112. .

Therefore, a method or system for compatible operation of switches conforming to different MSTPs is an important subject in future network application technologies.

Contents of the invention

In view of this, the present invention is based on the difference of different multiple spanning tree protocols, and checks the received bridge protocol data unit (bridge protocol data unit, BPDU), so that the data packet is transmitted in the Ethernet driver module ( LLC layer&Ethernet driver module) and IEEE standard multiple spanning tree module (MST module) are checked to ensure that data packets can be compatible between different switches.

In order to achieve the above object, the present invention provides a method compatible with multiple spanning tree protocols. First, a verification module is provided between the standard multi-spanning tree module and the Ethernet driver module, so as to avoid changing to the existing multi-spanning tree module. Verification module It is used to execute the receiving inspection program and the transmission inspection program. The inspection module, standard multiple spanning tree module and Ethernet driver module are set in a switch.

The verification module is used for receiving the bridging PDU and verifying the adjustment. A receipt check is performed on the bridging PDU when it is from the Ethernet driver module, and a delivery check is performed on the bridging PDU when it is from a standard MPDU.

The receiving inspection procedure includes the following steps. Firstly, the type of bridging protocol data unit is judged, that is, it is judged whether the bridging protocol data unit conforms to the multi-spanning tree format of the switch itself or a known compatible multi-spanning tree format according to the difference in the format of the bridging protocol data unit. . The multiple spanning tree of the switch itself may be an IEEE standard multiple spanning tree protocol, and the known compatible multiple spanning tree may be a Cisco standard multiple spanning tree protocol.

For example, the bridge protocol data unit conforms to the multiple spanning tree format of the switch itself or is an unknown format. Confirm whether the multiple spanning tree protocol record of the communication port where the switch receives the bridging protocol data unit complies. If not, adjust the protocol record of the communication port and update the recorded identification code information of the communication port (MST setting identification code field). The identification code information is used to record important setting check information of the MST protocol, and can be obtained from the bridging protocol data unit.

For example, the bridging protocol data unit conforms to the known compatible multiple spanning tree format. Verify that the regional configuration settings of the bridge protocol data unit are consistent with the configuration settings of the multi-spanning tree of the switch itself, such as confirming the configuration name field (Configuration Name) and MSTI information (MSTI message) in the bridge protocol data unit Whether the quantity is the same as the configuration name of the multi-spanning tree of the switch itself and the quantity of eligible expansion trees. When it is determined that the bridge protocol data unit is consistent with the area configuration setting of the multiple spanning tree of the switch itself, update the identification code information of the communication port to the identification code information (MST setting identification code field) in the bridge protocol data unit and confirm Whether the multiple spanning tree protocol record of the communication port that the switch receives the bridging protocol data unit complies with. If not, adjust the protocol record of the communication port.

When it is determined that the bridging protocol data unit is different from the switch's mspanning tree format but conforms to a known compatible mspanning tree format, the bridging protocol data unit format is recapsulated and converted into the switch's own mspanning tree format. The protocol operation is performed by the multiple spanning tree module of the switch.

The transmission checking procedure includes the following steps. Firstly, it is judged whether the MSTP record of the communication port where the switch transmits the bridging PDU is a known compatible MSTP.

If the protocol record of the communication port conforms to the known and compatible multiple spanning tree protocol, the bridging protocol data unit format is re-encapsulated and converted into the known and compatible multiple spanning tree format. Hand over to the Ethernet driver module of the switch for packet transmission.

In addition, the present invention also proposes a multiple spanning tree protocol compatible system, which includes a verification module, and the verification module includes a protocol identification module, an area verification module and a packet conversion module. The verification module is arranged between the standard MST module and the Ethernet driver module of the switch, and is used for executing the aforementioned reception verification program and transmission verification program. The protocol identification module, area verification module and packet conversion module are used to provide inspection functions and data records required for receiving inspection procedures and transmission inspection procedures. The verification module, the standard multiple spanning tree module and the Ethernet driver module are arranged in a switch.

The protocol identification module includes the bridge protocol data unit type discrimination function and the multiple spanning tree protocol record of the communication port, which is used for the receiving inspection program and the transmission inspection program. The area verification module includes the bridge protocol data unit area verification function and the communication port identification code information record , for use in the receiving inspection program. The packet conversion module includes the bridging protocol data unit re-encapsulation function, which is used in the receiving inspection program and the transmission inspection program, and converts the packet into a known multiple spanning tree format.

In addition, the present invention also proposes a switch, which includes the above-mentioned multiple spanning tree protocol compatible system.

Through the invention, it can ensure the compatible operation of the data package among different switches.

The detailed features and advantages of the present invention will be described in detail in the implementation manner, and its content is enough to make any person familiar with the related art understand the technology of the present invention and implement it accordingly, and any advantages and objectives related to the present invention can be easily read from this description The content disclosed, the scope of the patent application and the drawings are understood.

The above description about the content of the present invention and the following description of the implementation are used to demonstrate and explain the principle of the present invention, and provide further explanation of the patent application scope of the present invention.

Description of drawings

Figures 1a-1c show how current switches that comply with different MSP standards operate.

Fig. 2 shows a schematic diagram of the exchanger disclosed in the present invention.

Fig. 3a shows a flow chart of the execution of the acceptance verification procedure in the method disclosed in the present invention.

FIG. 3b shows a flow chart of the execution of the transmission verification program in the method disclosed in the present invention.

Fig. 4a shows the field format of the bridging PDU conforming to the IEEE standard multiple spanning tree protocol.

Figure 4b shows the field format of the bridging PDU according to the Cisco standard multiple spanning tree protocol.

FIG. 4c shows the format of the set identifier field of the bridging PDU conforming to the IEEE standard MSTP.

FIG. 4d shows the format of the setting identifier field of the bridging PDU conforming to the Cisco standard MSTP.

Fig. 4e shows the format of the MSTI information field of the bridging PDU conforming to the IEEE standard multiple spanning tree protocol.

Figure 4f shows the format of the MSTI information field of a bridging PDU conforming to the Cisco standard Multiple Spanning Tree Protocol.

Figure 5a shows a schematic diagram of an embodiment of the method disclosed in the present invention.

Figure 5b shows a schematic diagram of another embodiment of the method disclosed in the present invention.

Symbol Description:

100-exchange;

102-Cisco switch;

104-IEEE standard switch;

106-a virtual switch formed by multiple spanning trees;

108, 110, 112-areas formed by multiple spanning trees;

20 - exchanger;

200-inspection module;

202-IEEE standard multiple spanning tree module;

204-Ethernet driver module;

210 - acceptance inspection procedure;

212-transmit inspection procedure;

230-protocol identification module;

240-area verification module;

250-packet conversion module;

400, 402-the third version length (Version 3 Length) field;

410-MST extended information length field;

412, 420-MST setting identification code;

414, 422-CIST bridge identification code;

404, 406-MSTI information;

430, 440-the configuration setting name (Configuration Name) of the multi-spanning tree setting identification code;

450-MSTI expansion tree number;

452, 460-area root identification code;

454-MSTI bridge identification code;

456-MSTI communication port identification code;

462-MSTI bridge priority;

464-MSTI communication port priority;

500, 510-reinforced type exchanger (according to the method proposed by the present invention);

502-other switches (supporting other multiple spanning trees);

504-Cisco switch (support Cisco standard multiple spanning tree);

506, 516-areas formed by multiple spanning trees;

512-Area formed by Cisco standard multiple spanning tree;

514-IEEE standard multiple spanning tree formed area.

Detailed ways

Regarding the characteristics and implementation of the present invention, the best embodiment will be described in detail as follows with reference to the drawings, please refer to FIG. 2 . FIG. 2 is a schematic diagram showing the exchanger disclosed in the present invention. In one embodiment, the present invention provides a switch 20, which is manufactured in a method compatible with Multiple Spanning Tree Protocol. The multiple spanning tree protocol of the switch itself takes the IEEE standard multiple spanning tree module as an example, and the known compatible multiple spanning tree protocol of the switch takes the Cisco standard multiple spanning tree module as an example.

First, a verification module 200 is provided between the IEEE standard multiple spanning tree module (MST module) 202 and the Ethernet driver module (LLC Layer & Ethernet Driver Module) 204, and the verification module 200 is used to execute the receiving verification program 210 and the transmission verification program 212. The verification module 200 includes a protocol identification module 230 , an area verification module 240 and a packet conversion module 250 . The verification module 200 , the IEEE standard multiple spanning tree module 202 and the Ethernet driver module 204 are disposed in the switch 20 .

The checking module 200 is used for receiving the bridging PDU and checking and adjusting it. The receipt check procedure 210 is performed on the bridging PDU when it comes from the Ethernet driver module 204, and the delivery check procedure is performed on the bridging PDU when it comes from the IEEE standard multiple spanning tree module 202 212.

A schematic flow chart of the details of the receiving inspection program 210 is shown in FIG. 3a. Firstly, when the Ethernet driver module 204 receives the bridging PDU (step S300 ), the bridging PDU type judgment function of the protocol identification module 230 is used to determine the type (step S302 ).

When judging that the bridging protocol data unit conforms to the IEEE standard multiple spanning tree format, check whether the switch receives the multiple spanning tree protocol record of the communication port of the bridging protocol data unit and is set to Cisco standard multiple spanning tree (step S304). The record is the Cisco standard MST, then the protocol record is set to the IEEE standard MST (step S306) and clears the identification code information record of the communication port (step S308).

When it is judged that the bridge protocol data unit conforms to the Cisco standard multiple spanning tree format, the region identification is performed through the region verification function of the bridge protocol data unit of the region verification module 240 (step S310 ). When verifying that the bridge PDU has the same area configuration as the multiple spanning tree of the switch, record the setting identification code 412 (see FIG. 4b) in the bridging PDU in the communication port receiving the bridging PDU The identification code information is being recorded (step S312), and the protocol record of the communication port is set as the Cisco standard multiple spanning tree (step S314).

Finally, if the bridging PDU is in the Cisco standard MST format, the bridging PDU is converted into the IEEE standard MST format through the bridging PDU re-encapsulation function of the packet conversion module 250 (step S316). Then, the IEEE standard multiple spanning tree module 202 is notified of the receipt of the bridging protocol data unit (step S318).

For the bridging PDU type discrimination function of the protocol identification module 230 , please refer to FIG. 4 a - FIG. 4 b . Fig. 4a shows the format field of the bridging PDU conforming to the IEEE standard MSP, and Fig. 4b shows the format field of the bridging PDU conforming to the Cisco standard MTP. It can be determined as the Cisco MST format under the following conditions, that is, the value of the Version 3 Length field 400 in the bridging protocol data unit is 0, and the MST Extended Length in the bridging protocol data unit The value of field 410 is greater than or equal to 64, the total length of the bridge protocol data unit minus 38 must be greater than or equal to the value of the length field 410 of the multiple spanning tree extension information, the total length of the bridge protocol data unit minus 103 must be a multiple of 26, and the multi-generation The value of the length field 410 of the tree extension information minus 64 must be a multiple of 26.

Please also refer to FIG. 4 c - FIG. 4 d for the bridging PDU area verification function of the area verification module 240 . FIG. 4 c shows the format of the configuration identifier field 420 conforming to the IEEE standard MSTP, and FIG. 4 d shows the format of the configuration identifier field 412 conforming to the Cisco standard MSTP. It can be judged that the regional configuration setting of the IEEE standard and the Cisco standard MST is the same under the following conditions, that is, the configuration name (ConfigurationName) field 430 of the identification code field 412 and the MSTI information (MSTI message) included in the bridging protocol data unit The quantity is consistent with the configuration name of the multi-spanning tree of the switch itself and the quantity of eligible expansion trees.

For the bridging PDU re-encapsulation function of the packet conversion module 250, please refer to FIGS. 4a-4b, 4e-4f. Figure 4a shows the bridge protocol data unit format field conforming to the IEEE standard multiple spanning tree protocol, Figure 4b shows the bridge protocol data unit format field conforming to the Cisco standard multiple spanning tree protocol, and Figure 4e shows the bridge protocol data unit format field conforming to the IEEE standard multiple spanning tree protocol The format of the MSTI information field (Message) 406, FIG. 4d shows the format of the MSTI information field 404 conforming to the Cisco standard MSTP. The Cisco standard multiple spanning tree packet format (Figure 4b) is converted to the IEEE standard multiple spanning tree packet format (Figure 4a), that is, the value of the extended information length field 410 (64+26*N) is converted into the third version of the length field 402 value (64 +16*N), copy the area configuration identification code data of the multi-spanning tree protocol of the switch itself to become the data in the setting identification code field 420, and directly set the corresponding field data in the other fields. The Cisco MSTI information field format (Figure 4f) is converted to the IEEE standard MSTI information field format (Figure 4e), that is, the second byte of the Regional Root Identity (Regional Root Identity) 452 is replaced with the MSTI expansion tree number 450 and then set as a region Root identification code (Regional RootIdentity) 460 field data, the first byte of MSTI bridge identification code (Bridge Identity) 454 is set to MSTI bridge priority (Bridge Priority) 462 field data, MSTI communication port identification code (Port Identity) ) The first byte of 456 is set to MSTI communication port priority (Port Priority) 464 field data, and the remaining fields are directly set to corresponding field data.

A schematic diagram of the detailed flow of the transmission inspection program 212 is shown in FIG. 3b. First, when the IEEE standard multiple spanning tree module 202 sends a bridging protocol data unit (step S320). The format is determined by the communication port MSTP record data of the protocol identification module 230 (step S322).

When it is determined that the protocol record of the communication port to send the bridging PDU is a Cisco standard MST, the bridging PDU is converted into the Cisco standard MST format ( Step S324). Finally, notify the Ethernet driver module 204 to transmit the bridging PDU (step S318).

For the bridging PDU re-encapsulation function of the packet conversion module 250, please refer to FIGS. 4a-4b, 4e-4f. Figure 4a shows the bridge protocol data unit format field conforming to the IEEE standard multiple spanning tree protocol, Figure 4b shows the bridge protocol data unit format field conforming to the Cisco standard multiple spanning tree protocol, and Figure 4e shows the bridge protocol data unit format field conforming to the IEEE standard multiple spanning tree protocol The format of the MSTI information field 406, FIG. 4f shows the format of the MSTI information field 404 conforming to the Cisco standard Multiple Spanning Tree Protocol. The IEEE standard multiple spanning tree packet format (Figure 4a) is converted to the Cisco standard multiple spanning tree packet format (Figure 4b), that is, the value of the length field 402 of the third version (64+16*N) is converted into the value of the extended information length field 410 (64 +26*N), and the value of the length field 400 of the third version is set to 0, and the identification code information record of the communication port that the copy switch intends to send the packet becomes the data set in the identification code field 412, and the remaining fields directly set the corresponding field data. The IEEE standard MSTI information field format (Fig. 4e) is converted into the Cisco MSTI information field format (Fig. 4f). into the value of the MSTI expansion tree number 450 field, the first byte of the CIST bridge identification code (Bridge Identity) 422 is replaced with the MSTI bridge priority 462 and then becomes the data of the MSTI bridge identification code 454, and the MSTI communication port priority 464 and The communication port number of the communication port to which the switch wants to send the packet constitutes the MSTI communication port identification code 456, and the other fields are directly set with corresponding field data.

Please refer to FIG. 2 again. FIG. 2 is a schematic diagram showing the switch disclosed by the present invention. In one embodiment, the present invention proposes a system compatible with multiple spanning tree protocols, including a verification module 200 , and the verification module 200 includes a protocol identification module 230 , an area verification module 240 and a packet conversion module 250 . The verification module 200 is disposed between the standard MST module 202 and the Ethernet driver module 204 , and is used for executing the reception verification program 210 and the transmission verification program 212 . The verification module 200 , the standard MST module 202 and the Ethernet driver module 204 are disposed in the switch 20 .

The protocol identification module 230 includes a bridging PDU type discrimination function and a communication port MSTP record for use in receiving and transmitting verification procedures. The bridging PDU type discrimination function of the protocol identification module 230 is the same as the above-mentioned method steps, which will not be repeated here.

The area verification function of the bridge protocol data unit and the information record of the communication port identification code of the area verification module 240 are used for receiving and checking procedures. The area verification module 240 includes the method steps of the bridging PDU area verification function described above, which will not be repeated here.

The packet conversion module 250 includes a bridging PDU re-encapsulation function, which is used for receiving and transmitting verification procedures. The bridging protocol data unit re-encapsulation function of the packet conversion module 250 includes converting the IEEE standard multiple spanning tree format into the Cisco standard multiple spanning tree format and converting the Cisco standard multiple spanning tree format into the IEEE standard multiple spanning tree format, as described above The method steps are not repeated here.

Please refer to Fig. 5a-Fig. 5b, assuming that there are three switches 500, 502 and 504 in the network, the switch 500 is a switch (hereinafter referred to as an enhanced switch) made by applying the method proposed by the present invention, the switch 502 is a switch (hereinafter referred to as other switches) that is general or conforms to other multiple spanning tree protocols, and switch 504 is a switch (hereinafter referred to as a Cisco switch) that conforms to the Cisco standard multiple spanning tree protocol. When the enhanced switch 500 is set to the same area, the enhanced switch 500 and the Cisco switch 504 can form an area 506, which is consistent with the ideal situation.

When the network system is more complex, as shown in Figure 5b, the switch 510 is an enhanced switch, the area 514 is formed by multiple Cisco switches, and the area 516 is formed by multiple standard switches (conforming to the IEEE standard multiple spanning tree protocol) As a result, a new multiple spanning tree area 516 can be formed because the enhanced switches 510 are connected in the middle.

Although the present invention has been disclosed above with preferred embodiments, it is not intended to limit the present invention. Anyone skilled in the art can make some changes and modifications without departing from the spirit and scope of the present invention. Therefore, this The scope of protection of an invention shall be determined by the scope of the patent application.

Claims (19)

1. A method compatible with Multiple Spanning Tree Protocol, characterized in that comprising the following steps: Provide a verification module between a standard multiple spanning tree module and an Ethernet driver module, the verification module is used to execute a reception verification program and a transmission verification program, the verification module, the standard multi-spanning tree module and the Ethernet network The driver module is set in a switch; receiving a bridging protocol data unit; and When the bridging protocol data unit comes from the above-mentioned Ethernet driver module, execute the above-mentioned receiving inspection program for the bridging protocol data unit; when the bridging protocol data unit comes from the above-mentioned standard multiple spanning tree module, execute the above-mentioned Send inspection program. 2. the method compatible with Multiple Spanning Tree Protocol as claimed in claim 1, is characterized in that, above-mentioned acceptance inspection program comprises the following steps: Discriminate the type of the bridging protocol data unit; When it is determined that the bridging protocol data unit complies with a first multiple spanning tree protocol, it is determined whether a communication port in the switch is recorded as a second multiple spanning tree protocol; When the above-mentioned communication port is recorded as the above-mentioned second multiple spanning tree protocol, setting the above-mentioned communication port to conform to the above-mentioned first multiple spanning tree protocol; When determining that the bridging protocol data unit conforms to the second multiple spanning tree protocol, identifying whether the bridging protocol data unit is the same as the multiple spanning tree area configuration of the switch; When the bridging protocol data unit is the same as the multiple spanning tree area configuration of the switch, setting the communication port record to conform to the second multiple spanning tree protocol; and When it is determined that the bridging protocol data unit conforms to the second multiple spanning tree protocol, encapsulating the bridging protocol data unit to conform to the format of the first multiple spanning tree protocol. 3. the method compatible with Multiple Spanning Tree Protocol as claimed in claim 2, is characterized in that, the kind of above-mentioned discriminating above-mentioned bridging protocol data unit is to finish by following any one of steps: Judging whether the value of a third version length field in the bridging PDU is 0; Determine whether the value of the multi-spanning tree extension information length field in the bridging protocol data unit is greater than or equal to 64; Whether the total length of the bridge protocol data unit minus 38 is greater than or equal to the value of the length field of the multiple spanning tree extension information; Whether the total length of the bridging PDU minus 103 is a multiple of 26; and Whether the value of the above-mentioned multiple spanning tree extension information length field minus 64 is a multiple of 26. 4. The method compatible with multiple spanning tree protocols as claimed in claim 2 is characterized in that, after the above-mentioned communication port is set to conform to the step of the first multiple spanning tree protocol, it also includes clearing an identification code information, The identification code information is used to represent information related to the first multiple spanning tree protocol transmission data, and the identification code information is recorded in the communication port of the receiving bridge protocol data unit. 5. The method compatible with multiple spanning tree protocols as claimed in claim 2, characterized in that, before the above-mentioned communication port is set to conform to the step of the second multiple spanning tree protocol, it also includes recording an identification code information, The identification code information is used to represent information related to the second MSTP transmission data, and the identification code information is recorded in the communication port of the receiving bridge PDU. 6. the multiple spanning tree protocol compatible method as claimed in claim 2, is characterized in that, whether above-mentioned identification above-mentioned bridging protocol data unit and the multiple spanning tree area of above-mentioned switch are identical step, is to finish by following any one of steps: identifying whether the configuration name field in said bridge PDU is identical to the configuration name field of said switch; and It is identified whether the number of MSTI information in the bridging PDU is the same as the number of qualified expansion trees established by the switch. 7. The multiple spanning tree protocol compatible method according to claim 2, wherein the first multiple spanning tree protocol is IEEE standard multiple spanning tree protocol, which is the multiple spanning tree protocol of the switch itself. 8. The method for compatibility with multiple spanning tree protocols according to claim 2, wherein the second multiple spanning tree protocol is a Cisco standard multiple spanning tree protocol, which is a known compatible multiple spanning tree protocol for switches. 9. the multiple spanning tree protocol compatible method as claimed in claim 1 is characterized in that, above-mentioned transmission checking program comprises the following steps: judging whether a communication port record in the switch conforms to the second multiple spanning tree protocol; and When the communication port conforms to the second multiple spanning tree protocol, encapsulating the bridging protocol data unit conforms to the second multiple spanning tree protocol. 10. A multiple spanning tree protocol compatible system, characterized in that it comprises: An inspection module, which is arranged between a standard multiple spanning tree module and an Ethernet driver module, the above inspection module is used to execute a receiving inspection program and a transmission inspection program, the above inspection module, the above standard multiple spanning tree module and the above The Ethernet driver module is set in a switch; Among them, the above-mentioned inspection modules include: A protocol identification module, which is used to provide the bridge protocol data unit type discrimination function and the multiple spanning tree protocol record of the communication port; An area verification module, which is used to provide the bridge protocol data unit area verification function and the identification code information record of the communication port; and A packet conversion module, which is used to provide the re-encapsulation function of bridging protocol data units in different formats; Wherein, when the verification module executes the receiving verification program and the transmitting verification program, the required functions and parameters are provided by the above-mentioned protocol identification module, the above-mentioned area verification module and the above-mentioned packet conversion module. 11. The system compatible with Multiple Spanning Tree Protocol as claimed in claim 10, characterized in that, when the above-mentioned verification module is executing the above-mentioned reception verification program, it is also used to: Discriminate the type of the bridging protocol data unit; When it is determined that the bridging protocol data unit complies with a first multiple spanning tree protocol, it is determined whether a communication port in the switch is recorded as a second multiple spanning tree protocol; When the above-mentioned communication port record conforms to the above-mentioned second multiple spanning tree protocol, setting the above-mentioned communication port to conform to the above-mentioned first multiple spanning tree protocol; When determining that the bridging protocol data unit conforms to the second multiple spanning tree protocol, identifying whether the bridging protocol data unit is the same as the multiple spanning tree area configuration of the switch; When the bridging protocol data unit is the same as the multiple spanning tree area configuration of the switch, setting the communication port record to conform to the second multiple spanning tree protocol; and When it is determined that the bridging protocol data unit conforms to the second multiple spanning tree protocol, encapsulating the bridging protocol data unit to conform to the first multiple spanning tree protocol format. 12. The system compatible with Multiple Spanning Tree Protocol as claimed in claim 11, characterized in that, the above-mentioned discrimination of the type of the above-mentioned bridging protocol data unit is a function provided by the protocol identification module, and is completed by any one of the following conditions: Whether the value of a third version length field in the bridging PDU is 0; Whether the value of the multi-spanning tree extension information length field in the bridge protocol data unit is greater than or equal to 64; Whether the length of the bridge protocol data unit minus 38 is greater than or equal to the value of the length field of the multiple spanning tree extension information; Whether the above bridging PDU length minus 103 is a multiple of 26; and Whether the value of the above-mentioned multiple spanning tree extension information length field minus 64 is a multiple of 26. 13. the multiple spanning tree protocol compatible system as claimed in claim 11, is characterized in that, after the communication port record provided by the above-mentioned protocol identification module is set to meet the above-mentioned first multiple spanning tree protocol, it is also used to clear a Identification code information, where the identification code information is used to represent information related to the first multiple spanning tree protocol transmission data, and the identification code information is recorded in the communication port of the receiving bridge protocol data unit. 14. the multiple spanning tree protocol compatible system as claimed in claim 11, is characterized in that, before the communication port record provided by the above-mentioned protocol identification module is set to meet the above-mentioned second multiple spanning tree protocol, it is also used to record a Identification code information, where the identification code information is used to represent information related to the second MSTP transmission data, and the identification code information is recorded in the communication port of the receiving bridging protocol data unit. 15. The system compatible with Multiple Spanning Tree Protocol as claimed in claim 11, characterized in that, the above-mentioned identifying whether the multiple spanning tree area configurations of the above-mentioned bridging protocol data unit and the above-mentioned switch are the same is the function provided by the area inspection module , is fulfilled by any of the following conditions: whether the configuration name field in said bridging PDU is the same as the configuration name field of said switch; and Whether the quantity of MSTI information in the bridging PDU is the same as the quantity of eligible expansion trees established by the switch. 16. The system compatible with multiple spanning tree protocols according to claim 11, wherein the first multiple spanning tree protocol is IEEE standard multiple spanning tree protocol, which is the multiple spanning tree protocol of the switch itself. 17. The system compatible with multiple spanning tree protocols according to claim 11, wherein the second multiple spanning tree protocol is a Cisco standard multiple spanning tree protocol, which is a known compatible multiple spanning tree protocol for switches. 18. The system compatible with Multiple Spanning Tree Protocol as claimed in claim 10, characterized in that, when the above-mentioned inspection module is executing the above-mentioned transmission inspection program, it is also used to: judging whether a communication port record in the switch conforms to the second multiple spanning tree protocol; and When the communication port conforms to the second multiple spanning tree protocol, encapsulating the bridging protocol data unit conforms to the second multiple spanning tree protocol. 19. A switch, characterized in that the switch comprises the Multiple Spanning Tree Protocol compatible system according to any one of claims 10 to 18.

Images