CN1997002B - Compatible method, system and related switch for multi-fold expansion tree protocol - Google Patents
Compatible method, system and related switch for multi-fold expansion tree protocol Download PDFInfo
- Publication number
- CN1997002B CN1997002B CN200610000387A CN200610000387A CN1997002B CN 1997002 B CN1997002 B CN 1997002B CN 200610000387 A CN200610000387 A CN 200610000387A CN 200610000387 A CN200610000387 A CN 200610000387A CN 1997002 B CN1997002 B CN 1997002B
- Authority
- CN
- China
- Prior art keywords
- mentioned
- spanning tree
- multiple spanning
- data unit
- protocol data
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Small-Scale Networks (AREA)
Abstract
This invention provides one method, system and relative exchanger for multiple agreement tree capacity, which comprises the following steps: firstly providing test module in IEEE standard of multipleextensive tree module and Ethernet network drive program module, wherein, the test module is to execute receive test program and to send test program; the test module, the extensive tree module and program module are set in the exchanger; the test module is to receive bridge agreement data unit.
Description
Technical field
(multiple spanning tree protocol, MSTP) Yun Zuo method is particularly relevant for a kind of method that operates between different Multiple Spanning Tree Protocols that is applicable to the invention relates to a kind of Multiple Spanning Tree Protocol.
Background technology
(spanning tree protocol STP), is meant the binding management agreement of framework on the IEEE802.1 standard to the expansion tree protocol of general common name, and its function is the state of each bridge joint (bridge) device in the keyholed back plate network (network).Use the expansion tree protocol can reduce the situation that network path (path) repeats or goes to live in the household of one's in-laws on getting married and go, and avoid unnecessary loop (loop) effectively.The data of being transmitted in network are to carry out in the mode of package (packet), and in network different local LAN (local area network, LAN) device that filters and produce package is interchanger (switch).
Because the fast development of network technology, when an entity LAN is divided into a plurality of Virtual Local Area Networks (virtual LAN, VLAN) time, single expansion tree protocol often can't calculate network topology (topology) demand that meets each Virtual Local Area Network appositely, therefore Multiple Spanning Tree Protocol (MSTP) just arises at the historic moment, and that is to say to use the multiple topology (multipletopology) that Multiple Spanning Tree Protocol can calculate network.Multiple Spanning Tree Protocol is be that unit operates with zone (region), and the interior interchanger of same area has identical multiple spanning tree setup parameter (parameter).After forming the zone, for an extra-regional interchanger, it is general this zone can be considered as integrated large-scale interchanger.
Yet, form because Multiple Spanning Tree Protocol may be formulated based on different standard (standard).For example, IEEE 802.1 standards and Cisco's standard (Cisco standard).Therefore, meet the interchanger of ieee standard Multiple Spanning Tree Protocol (IEEE 802.1 standard) and meet between the interchanger of Cisco's Multiple Spanning Tree Protocol (Cisco standard), and may not necessarily compatiblely operate.Please refer to Fig. 1 a-Fig. 1 c, suppose to exist in the network environment interchanger 100,102 and 104, interchanger 102 is Cisco's interchanger (meeting Cisco's standard Multiple Spanning Tree Protocol), and interchanger 104 is standard interchanger (meeting the ieee standard Multiple Spanning Tree Protocol).If when Cisco's interchanger 102 and standard interchanger 104 were set at the same area, perfect condition should form a zone shown in 108, and Cisco's interchanger 102 and standard interchanger 104 should form a Virtual switch 106, shown in Fig. 1 b.Yet, because Cisco's interchanger 102 and standard interchanger 104 and incompatible, just so form after the actual operation shown in Fig. 1 c, Cisco's interchanger 102 forms zone 110, standard interchanger 104 forms zone 112, both can't synthesize a zone.
Therefore, making method or system that the interchanger that meets different Multiple Spanning Tree Protocols can compatible running, is the important topic in the future network application technology.
Summary of the invention
In view of this, the present invention is the difference based on different Multiple Spanning Tree Protocols, (bridge protocol data unit BPDU) tests, and makes Ethernet driver module (the LLC layer﹠amp of data packet at interchanger for the Bridge Protocol Data Unit that is received; Ethernet driver module) and between ieee standard multiple spanning tree module (MST module) test, can compatible running between different interchangers to guarantee data packet.
For reaching above-mentioned purpose, the invention provides a kind of method of Multiple Spanning Tree Protocol compatibility, at first providing inspection module between standard multiple spanning tree module and Ethernet driver module, avoid changing existing multiple spanning tree module. inspection module is in order to carry out the acceptance inspection program and to transmit check problem. and inspection module, standard multiple spanning tree module and Ethernet driver module are arranged in the interchanger.
Inspection module is in order to receive Bridge Protocol Data Unit and check adjustment.When Bridge Protocol Data Unit during from the Ethernet driver module, carry out the acceptance inspection program for Bridge Protocol Data Unit, and, carry out the transmission check problem for Bridge Protocol Data Unit when Bridge Protocol Data Unit during from standard multiple spanning tree module.
The acceptance inspection program comprises the following steps, at first differentiate the kind of Bridge Protocol Data Unit, promptly distinguish according to the difference of Bridge Protocol Data Unit form whether this Bridge Protocol Data Unit meets multiple spanning tree form of interchanger own or known compatible multiple spanning tree form.The multiple spanning tree of interchanger own can be the ieee standard Multiple Spanning Tree Protocol, and known compatible multiple spanning tree can be Cisco's standard Multiple Spanning Tree Protocol.
Meet the multiple spanning tree form of interchanger own or be unknown form as Bridge Protocol Data Unit.Whether the Multiple Spanning Tree Protocol record that the affirmation interchanger receives the communication port of this Bridge Protocol Data Unit meets.As do not meet, then adjust the agreement record of this communication port and upgrade this communication port record identification code information (MST setting identification code field).Wherein this information of identification code is the important setting cross-check information that is used for writing down Multiple Spanning Tree Protocol, can be by obtaining in the Bridge Protocol Data Unit.
Meet known compatible multiple spanning tree form as Bridge Protocol Data Unit.Whether whether the regional configuration and setting of verifying this Bridge Protocol Data Unit is consistent with the configuration and setting of the multiple spanning tree of interchanger own, identical with the configuration title and the qualified expansion tree quantity of the multiple spanning tree of interchanger own as confirming configuration name field (Configuration Name) and MSTI information (MSTI message) quantity in the Bridge Protocol Data Unit.When definite Bridge Protocol Data Unit was consistent with the regional configuration and setting of the multiple spanning tree of interchanger own, the information of identification code that upgrades this communication port was the information of identification code (MST setting identification code field) in the Bridge Protocol Data Unit and confirms whether the Multiple Spanning Tree Protocol record that interchanger receives the communication port of this Bridge Protocol Data Unit meets.As do not meet, then adjust the agreement record of this communication port.
When judging that Bridge Protocol Data Unit is different with the multiple spanning tree form of interchanger own, but when meeting known compatible multiple spanning tree form, the Bridge Protocol Data Unit form is encapsulated again the form that is converted to the multiple spanning tree of interchanger own.Transfer to the multiple spanning tree module of interchanger and carry out the agreement running.
The transmission check problem comprises the following steps, differentiates at first whether the Multiple Spanning Tree Protocol record that interchanger transmits the communication port of this Bridge Protocol Data Unit is known compatible Multiple Spanning Tree Protocol.
Agreement record as this communication port meets known compatible Multiple Spanning Tree Protocol, the Bridge Protocol Data Unit form is encapsulated again be converted to known compatible multiple spanning tree form.The Ethernet driver module of transferring to interchanger carries out package and transmits.
In addition, the present invention also proposes a kind of system of Multiple Spanning Tree Protocol compatibility, comprises inspection module, and this inspection module comprises agreement identification module, area validation module and package modular converter.Inspection module is arranged between the standard multiple spanning tree module and Ethernet driver module of interchanger, and it is in order to carry out aforesaid acceptance inspection program and to transmit check problem.Agreement identification module, area validation module and package modular converter are in order to provide checking function and data record required when carrying out the acceptance inspection program and transmitting check problem.Inspection module, standard multiple spanning tree module and Ethernet driver module are arranged in the interchanger.
The agreement identification module comprises Bridge Protocol Data Unit kind discrimination function and communication port Multiple Spanning Tree Protocol record, to use when carrying out the acceptance inspection program and transmitting check problem. the area validation module comprises Bridge Protocol Data Unit area validation function and communication port information of identification code record, using when carrying out the acceptance inspection program. the package modular converter comprises Bridge Protocol Data Unit encapsulation function again, use when carrying out the acceptance inspection program and transmitting check problem, the conversion package is known multiple spanning tree form.
In addition, the present invention also proposes a kind of interchanger, and this interchanger comprises the system of above-mentioned Multiple Spanning Tree Protocol compatibility.
By the present invention, can guarantee data packet compatible running between different interchangers.
Detailed features of the present invention and advantage will be described in detail in execution mode, its content is enough to make any related art techniques person of haveing the knack of to understand technology of the present invention and implements according to this, and any advantage related to the present invention and purpose can be easily from the disclosed content of this specification, claim and graphic understanding.
Above about content of the present invention explanation and the explanation of following execution mode be in order to demonstration with explain principle of the present invention, and provide patent claim of the present invention further to explain.
Description of drawings
Fig. 1 a-Fig. 1 c shows the existing function mode that meets the interchanger of different Multiple Spanning Tree Protocol standards.
Fig. 2 shows the schematic diagram of disclosed interchanger.
Fig. 3 a shows acceptance inspection program implementation flow chart in the disclosed method.
Fig. 3 b shows the flowchart that transmits check problem in the disclosed method.
Fig. 4 a shows the field format of the Bridge Protocol Data Unit that meets the ieee standard Multiple Spanning Tree Protocol.
Fig. 4 b shows the field format of the Bridge Protocol Data Unit that meets Cisco's standard Multiple Spanning Tree Protocol.
Fig. 4 c shows the setting identification code field format of the Bridge Protocol Data Unit that meets the ieee standard Multiple Spanning Tree Protocol.
Fig. 4 d shows the setting identification code field format of the Bridge Protocol Data Unit that meets Cisco's standard Multiple Spanning Tree Protocol.
Fig. 4 e shows the MSTI information field form of the Bridge Protocol Data Unit that meets the ieee standard Multiple Spanning Tree Protocol.
Fig. 4 f shows the MSTI information field form of the Bridge Protocol Data Unit that meets Cisco's standard Multiple Spanning Tree Protocol.
Fig. 5 a shows the schematic diagram of an embodiment of disclosed method.
Fig. 5 b shows the schematic diagram of another embodiment of disclosed method.
Symbol description:
The 100-interchanger;
102-Cisco interchanger;
104-IEEE standard interchanger;
The formed Virtual switch of 106-multiple spanning tree;
108,110, the formed zone of 112-multiple spanning tree;
The 20-interchanger;
The 200-inspection module;
202-IEEE standard multiple spanning tree module;
204-Ethernet driver module;
210-acceptance inspection program;
212-transmits check problem;
230-agreement recognition module;
240-area validation module;
250-package modular converter;
400,402-third edition length (Version 3 Length) field;
410-MST extends the message length field;
412,420-MST setting identification code;
414,422-CIST bridger identification code;
404,406-MSTI information;
430, the configuration and setting title of 440-multiple spanning tree setting identification code (Configuration Name);
450-MSTI expansion tree numbering;
452,460-zone root identification code;
454-MSTI bridger identification code;
456-MSTI communication port identification code;
462-MSTI bridger priority;
464-MSTI communication port priority;
500, the reinforced interchanger of 510-(meeting the method that the present invention puies forward);
Other interchanger of 502-(supporting other multiple spanning tree);
504-Cisco interchanger (supporting Cisco's standard multiple spanning tree);
506, the formed zone of 516-multiple spanning tree;
The 512-Cisco formed zone of standard multiple spanning tree;
The formed zone of 514-IEEE standard multiple spanning tree.
Embodiment
Relevant characteristics and implementation of the present invention will cooperate graphicly to be described in detail as follows as most preferred embodiment, please refer to Fig. 2.Fig. 2 is the schematic diagram that shows disclosed interchanger.In one embodiment, the invention provides a kind of interchanger 20, it is made with the method for Multiple Spanning Tree Protocol compatibility.The Multiple Spanning Tree Protocol of interchanger itself is an example with ieee standard multiple spanning tree module, and the known compatible Multiple Spanning Tree Protocol of interchanger is an example with Cisco's standard multiple spanning tree module.
At first, provide inspection module 200 in ieee standard multiple spanning tree module (MST module) 202 and Ethernet driver module (LLC Layer﹠amp; Ethernet Driver Module) 204, inspection module 200 is in order to carry out acceptance inspection program 210 and to transmit check problem 212.Inspection module 200 comprises agreement identification module 230, area validation module 240 and package modular converter 250.Inspection module 200, ieee standard multiple spanning tree module 202 and Ethernet driver module 204 are arranged in the interchanger 20.
When judging that Bridge Protocol Data Unit meets ieee standard multiple spanning tree form, the inspection interchanger receives whether the Multiple Spanning Tree Protocol record of the communication port of this Bridge Protocol Data Unit is made as Cisco's standard multiple spanning tree (step S304). be recorded as Cisco's standard multiple spanning tree as this agreement, then the information of identification code record (step S308) that this agreement record is set at ieee standard multiple spanning tree (step S306) and removes this communication port.
When judging that Bridge Protocol Data Unit meets Cisco's standard multiple spanning tree form, carry out zone identification (step S310) by the Bridge Protocol Data Unit area validation function of area validation module 240.When the multiple spanning tree of checking Bridge Protocol Data Unit and interchanger has the same area configuration, write down setting identification code 412 (seeing also Fig. 4 b) in this Bridge Protocol Data Unit in the information of identification code of the communication port of receiving this Bridge Protocol Data Unit record (step S312), and the agreement record of this communication port is set at Cisco's standard multiple spanning tree (step S314).
At last, be Cisco's standard multiple spanning tree form as Bridge Protocol Data Unit, the Bridge Protocol Data Unit by package modular converter 250 encapsulation function again is converted to ieee standard multiple spanning tree form (step S316) with this Bridge Protocol Data Unit.Then, notice ieee standard multiple spanning tree module 202 is received Bridge Protocol Data Unit (step S318).
Wherein, the Bridge Protocol Data Unit kind discrimination function of agreement identification module 230 please refer to Fig. 4 a-Fig. 4 b.Fig. 4 a shows the Bridge Protocol Data Unit format fields that meets the ieee standard Multiple Spanning Tree Protocol, and Fig. 4 b shows the Bridge Protocol Data Unit format fields that meets Cisco's standard Multiple Spanning Tree Protocol.Can following condition criterion be Cisco's multiple spanning tree form, be that third edition length (Version 3 Length) field 400 numerical value in the Bridge Protocol Data Unit are 0, multiple spanning tree in the Bridge Protocol Data Unit extends message length (MST Extended Length) field 410 numerical value more than or equal to 64, the total length of Bridge Protocol Data Unit subtracts 38 numerical value that need more than or equal to multiple spanning tree extension message length field 410, the total length of Bridge Protocol Data Unit subtracts 103 and is required to be 26 multiple, and multiple spanning tree extends message length field 410 numerical value and subtracts 64 and be required to be 26 multiple.
The Bridge Protocol Data Unit area validation function of area validation module 240 is please in the lump with reference to Fig. 4 c-Fig. 4 d.Fig. 4 c is the form that shows the setting identification code field 420 that meets the ieee standard Multiple Spanning Tree Protocol, and Fig. 4 d is the form that shows the setting identification code field 412 that meets Cisco's standard Multiple Spanning Tree Protocol.Can following condition criterion ieee standard identical with the regional configuration and setting of Cisco standard multiple spanning tree, promptly configuration title (ConfigurationName) field 430 of setting identification code field 412 and MSTI information (MSTI message) quantity that comprises conform to the configuration title and the qualified expansion tree quantity of the multiple spanning tree of interchanger own in the Bridge Protocol Data Unit.
The Bridge Protocol Data Unit of package modular converter 250 is encapsulation function again, please refer to Fig. 4 a-Fig. 4 b, Fig. 4 e-Fig. 4 f.Fig. 4 a shows the Bridge Protocol Data Unit format fields that meets the ieee standard Multiple Spanning Tree Protocol, Fig. 4 b shows the Bridge Protocol Data Unit format fields that meets Cisco's standard Multiple Spanning Tree Protocol, Fig. 4 e is the form that shows the MSTI information field (Message) 406 that meets the ieee standard Multiple Spanning Tree Protocol, and Fig. 4 d is the form that shows the MSTI information field 404 that meets Cisco's standard Multiple Spanning Tree Protocol.Cisco's standard multiple spanning tree package form (Fig. 4 b) transfers ieee standard multiple spanning tree package form to, and (Fig. 4 a), be about to extend message length field 410 numerical value (64+26*N) and be converted into third edition length field 402 numerical value (64+16*N), the regional configuration identification code data that duplicates the Multiple Spanning Tree Protocol of interchanger own becomes setting identification code field 420 data, and all the other fields are directly set the corresponding field data.The MSTI of Cisco information field form (Fig. 4 f) transfers ieee standard MSTI information field form (Fig. 4 e) to, second byte that is about to regional root identification code (Regional Root Identity) 452 replaces to and is set as regional root identification code (Regional RootIdentity) 460 field datas after MSTI expansion tree numbers 450, first byte of MSTI bridger identification code (Bridge Identity) 454 is set as MSTI bridger priority (Bridge Priority) 462 field datas, first byte of MSTI communication port identification code (Port Identity) 456 is set as MSTI communication port priority (Port Priority) 464 field datas, and all the other fields are directly set the corresponding field data.
Transmit check problem 212 thin portion schematic flow sheets, shown in Fig. 3 b.At first, when ieee standard multiple spanning tree module 202 transmission Bridge Protocol Data Units (step S320).Communication port Multiple Spanning Tree Protocol record data by agreement identification module 230 carry out form judgement (step S322).
When judging that agreement that desire sends the communication port of Bridge Protocol Data Unit is recorded as Cisco's standard multiple spanning tree, the Bridge Protocol Data Unit by package modular converter 250 encapsulation function again is converted to Cisco's standard multiple spanning tree form (step S324) with this Bridge Protocol Data Unit.At last, notice Ethernet driver module 204 transmits Bridge Protocol Data Unit (step S318).
Wherein, the Bridge Protocol Data Unit of package modular converter 250 is encapsulation function again, please refer to Fig. 4 a-Fig. 4 b, Fig. 4 e-Fig. 4 f.Fig. 4 a shows the Bridge Protocol Data Unit format fields that meets the ieee standard Multiple Spanning Tree Protocol, Fig. 4 b shows the Bridge Protocol Data Unit format fields that meets Cisco's standard Multiple Spanning Tree Protocol, Fig. 4 e is the form that shows the MSTI information field 406 that meets the ieee standard Multiple Spanning Tree Protocol, and Fig. 4 f is the form that shows the MSTI information field 404 that meets Cisco's standard Multiple Spanning Tree Protocol.(Fig. 4 a) transfers Cisco's standard multiple spanning tree package form (Fig. 4 b) to ieee standard multiple spanning tree package form, be about to third edition length field 402 numerical value (64+16*N) and convert extension message length field 410 numerical value (64+26*N) to, and third edition length field 400 numerical value are made as 0, the information of identification code record that duplicates the communication port of interchanger desire transmission package becomes setting identification code field 412 data, and all the other fields are directly set the corresponding field data.Ieee standard MSTI information field form (Fig. 4 e) transfers the MSTI of Cisco information field form (Fig. 4 f) to, be about to regional root identification code 460 and be converted into regional root identification code 452 field datas, second byte of zone root identification code 460 is set as MSTI expansion tree numbering 450 field numerical value, first byte of CIST bridger identification code (Bridge Identity) 422 becomes MSTI bridger identification code 454 data after replacing to MSTI bridger priority 462, MSTI communication port priority 464 is formed MSTI communication port identification code 456 with the communication port numbering that the interchanger desire sends the communication port of package, and all the other fields are directly set the corresponding field data.
Referring again to Fig. 2, Fig. 2 is the schematic diagram that shows disclosed interchanger.In one embodiment, the present invention proposes a kind of system of Multiple Spanning Tree Protocol compatibility, comprises inspection module 200, and inspection module 200 comprises that agreement identification module 230, area validation mould determine 240 and package modular converter 250.Inspection module 200 is arranged at 204 of standard multiple spanning tree module 202 and Ethernet driver modules, and it is in order to carry out acceptance inspection program 210 and to transmit check problem 212.Inspection module 200, standard multiple spanning tree module 202 and Ethernet driver module 204 are arranged in the interchanger 20.
The Bridge Protocol Data Unit area validation function of area validation module 240 and communication port information of identification code record use when carrying out the acceptance inspection program.Area validation module 240 comprises the foregoing method step of Bridge Protocol Data Unit area validation function, does not repeat them here.
Package modular converter 250 comprises Bridge Protocol Data Unit encapsulation function again, uses when carrying out the acceptance inspection program and transmitting check problem.The Bridge Protocol Data Unit of package modular converter 250 is encapsulation function again, comprise that conversion ieee standard multiple spanning tree form becomes Cisco's standard multiple spanning tree form and conversion Cisco standard multiple spanning tree form becomes ieee standard multiple spanning tree form two parts, foregoing method step does not repeat them here.
Please refer to Fig. 5 a-Fig. 5 b, suppose to have in the network three interchangers 500,502 and 504, interchanger 500 is for using the made interchanger (to call reinforced interchanger in the following text) of method proposed by the invention, interchanger 502 is general or meets the interchanger (to call other interchanger in the following text) of other Multiple Spanning Tree Protocol, interchanger 504 is for meeting the interchanger (to call Cisco's interchanger in the following text) of Cisco's standard Multiple Spanning Tree Protocol. when Cisco's interchanger 504 and reinforced interchanger 500 are set at the same area, then reinforced interchanger 500 can form a zone 506 with Cisco's interchanger 504, conforms to ideal state.
When network system is complicated, shown in Fig. 5 b, interchanger 510 is reinforced interchanger, zone 514 is formed by many Cisco's interchangers, zone 516 is formed by the accurate interchanger of many station symbols (meeting the ieee standard Multiple Spanning Tree Protocol), because the centre couples mutually with reinforced interchanger 510, therefore just can form new multiple spanning tree zone 516.
Though the present invention discloses as above with preferred embodiment; right its is not in order to limiting the present invention, anyly has the knack of this skill person, without departing from the spirit and scope of the present invention; when can doing a little change and retouching, so protection scope of the present invention is when looking being as the criterion that claim defines.
Claims (19)
1. the method for a Multiple Spanning Tree Protocol compatibility is characterized in that comprising the following steps:
Provide an inspection module between a standard multiple spanning tree module and an Ethernet driver module, above-mentioned inspection module transmits check problem in order to carry out an acceptance inspection program and, and above-mentioned inspection module, above-mentioned standard multiple spanning tree module and above-mentioned Ethernet driver module are arranged in the interchanger;
Receive a Bridge Protocol Data Unit; And
When above-mentioned Bridge Protocol Data Unit during from above-mentioned Ethernet driver module, carry out above-mentioned acceptance inspection program for above-mentioned Bridge Protocol Data Unit, when above-mentioned Bridge Protocol Data Unit during, carry out above-mentioned transmission check problem for above-mentioned Bridge Protocol Data Unit from above-mentioned standard multiple spanning tree module.
2. the method for Multiple Spanning Tree Protocol compatibility as claimed in claim 1 is characterized in that, above-mentioned acceptance inspection program comprises the following steps:
Differentiate the kind of above-mentioned Bridge Protocol Data Unit;
When judging that above-mentioned Bridge Protocol Data Unit meets one first Multiple Spanning Tree Protocol, whether a communication port of differentiating in the above-mentioned interchanger is recorded as one second Multiple Spanning Tree Protocol;
When above-mentioned communication port is recorded as above-mentioned second Multiple Spanning Tree Protocol, above-mentioned communication port is set at meets above-mentioned first Multiple Spanning Tree Protocol;
Whether when judging that above-mentioned Bridge Protocol Data Unit meets above-mentioned second Multiple Spanning Tree Protocol, it is identical with the regional configuration of the multiple spanning tree of above-mentioned interchanger to discern above-mentioned Bridge Protocol Data Unit;
When the multiple spanning tree zone of above-mentioned Bridge Protocol Data Unit and above-mentioned interchanger configuration is identical, above-mentioned communication port record is set at meets above-mentioned second Multiple Spanning Tree Protocol; And
When judging that above-mentioned Bridge Protocol Data Unit meets above-mentioned second Multiple Spanning Tree Protocol, encapsulate above-mentioned Bridge Protocol Data Unit for meeting the above-mentioned first Multiple Spanning Tree Protocol form.
3. the method for Multiple Spanning Tree Protocol compatibility as claimed in claim 2 is characterized in that, the kind of the above-mentioned Bridge Protocol Data Unit of above-mentioned differentiation is to finish by following any one step:
Whether a third edition length field numerical value of differentiating in the above-mentioned Bridge Protocol Data Unit is 0;
Whether a multiple spanning tree of differentiating in the above-mentioned Bridge Protocol Data Unit extends message length field numerical value more than or equal to 64;
Above-mentioned Bridge Protocol Data Unit total length subtracts 38 and whether extends message length field numerical value more than or equal to above-mentioned multiple spanning tree;
Whether above-mentioned Bridge Protocol Data Unit total length subtracts 103 is 26 multiple; And
Whether above-mentioned multiple spanning tree to subtract 64 be 26 multiple if extending message length field numerical value.
4. the method for Multiple Spanning Tree Protocol compatibility as claimed in claim 2, it is characterized in that, above-mentioned above-mentioned communication port is set at the step that meets above-mentioned first Multiple Spanning Tree Protocol after, also comprise and remove an information of identification code, above-mentioned information of identification code is in order to the relevant information of expression with above-mentioned first Multiple Spanning Tree Protocol transmission data, and above-mentioned information of identification code is recorded in the communication port of above-mentioned reception Bridge Protocol Data Unit.
5. the method for Multiple Spanning Tree Protocol compatibility as claimed in claim 2, it is characterized in that, above-mentioned above-mentioned communication port is set at the step that meets above-mentioned second Multiple Spanning Tree Protocol before, also comprise record one information of identification code, above-mentioned information of identification code is in order to the relevant information of expression with above-mentioned second Multiple Spanning Tree Protocol transmission data, and above-mentioned information of identification code is recorded in the communication port of above-mentioned reception Bridge Protocol Data Unit.
6. the method for Multiple Spanning Tree Protocol compatibility as claimed in claim 2 is characterized in that, the step whether the multiple spanning tree zone of the above-mentioned Bridge Protocol Data Unit of above-mentioned identification and above-mentioned interchanger is identical is to finish by following any one step:
Whether the configuration name field of discerning in the above-mentioned Bridge Protocol Data Unit is identical with the configuration name field of above-mentioned interchanger; And
Whether discerning MSTI information content and above-mentioned interchanger in the above-mentioned Bridge Protocol Data Unit, to set up qualified expansion tree quantity identical.
7. the method for Multiple Spanning Tree Protocol compatibility as claimed in claim 2 is characterized in that, above-mentioned first Multiple Spanning Tree Protocol is the ieee standard Multiple Spanning Tree Protocol, and it is the Multiple Spanning Tree Protocol of interchanger itself.
8. the method for Multiple Spanning Tree Protocol compatibility as claimed in claim 2 is characterized in that, above-mentioned second Multiple Spanning Tree Protocol is Cisco's standard Multiple Spanning Tree Protocol, and it is the known compatible Multiple Spanning Tree Protocol of interchanger.
9. the method for Multiple Spanning Tree Protocol compatibility as claimed in claim 1 is characterized in that, above-mentioned transmission check problem comprises the following steps:
Whether the communication port record of differentiating in the above-mentioned interchanger meets above-mentioned second Multiple Spanning Tree Protocol; And
When above-mentioned communication port meets above-mentioned second Multiple Spanning Tree Protocol, encapsulate above-mentioned Bridge Protocol Data Unit and meet above-mentioned second Multiple Spanning Tree Protocol.
10. the system of a Multiple Spanning Tree Protocol compatibility is characterized in that comprising:
One inspection module, it is arranged between a standard multiple spanning tree module and an Ethernet driver module, above-mentioned inspection module transmits check problem in order to carry out an acceptance inspection program and, and above-mentioned inspection module, above-mentioned standard multiple spanning tree module and above-mentioned Ethernet driver module are arranged in the interchanger;
Wherein, above-mentioned inspection module comprises:
One agreement identification module is in order to provide the Multiple Spanning Tree Protocol record of Bridge Protocol Data Unit kind discrimination function and communication port;
One area validation module is in order to provide the information of identification code record of Bridge Protocol Data Unit area validation function and communication port; And
One package modular converter is in order to Bridge Protocol Data Unit that different-format is provided encapsulation function again;
Wherein, when inspection module was carried out the acceptance inspection program and transmitted check problem, required function and parameter were provided by above-mentioned agreement identification module, above-mentioned zone authentication module and above-mentioned package modular converter.
11. the system of Multiple Spanning Tree Protocol compatibility as claimed in claim 10 is characterized in that, above-mentioned inspection module when carrying out above-mentioned acceptance inspection program, also in order to:
Differentiate the kind of above-mentioned Bridge Protocol Data Unit;
When judging that above-mentioned Bridge Protocol Data Unit meets one first Multiple Spanning Tree Protocol, whether a communication port of differentiating in the above-mentioned interchanger is recorded as one second Multiple Spanning Tree Protocol;
When above-mentioned communication port record meets above-mentioned second Multiple Spanning Tree Protocol, above-mentioned communication port is set at meets above-mentioned first Multiple Spanning Tree Protocol;
Whether when judging that above-mentioned Bridge Protocol Data Unit meets above-mentioned second Multiple Spanning Tree Protocol, it is identical with the regional configuration of the multiple spanning tree of above-mentioned interchanger to discern above-mentioned Bridge Protocol Data Unit;
When the multiple spanning tree zone of above-mentioned Bridge Protocol Data Unit and above-mentioned interchanger configuration is identical, above-mentioned communication port record is set at meets above-mentioned second Multiple Spanning Tree Protocol; And
When judging that above-mentioned Bridge Protocol Data Unit meets above-mentioned second Multiple Spanning Tree Protocol, encapsulate above-mentioned Bridge Protocol Data Unit for meeting the above-mentioned first Multiple Spanning Tree Protocol form.
12. the system of Multiple Spanning Tree Protocol compatibility as claimed in claim 11 is characterized in that, the kind of the above-mentioned Bridge Protocol Data Unit of above-mentioned differentiation is the function that is provided by the agreement identification module, is to finish by following any one condition:
Whether the third edition length field numerical value in the above-mentioned Bridge Protocol Data Unit is 0;
Whether a multiple spanning tree in the above-mentioned Bridge Protocol Data Unit extends message length field numerical value more than or equal to 64;
Above-mentioned Bridge Protocol Data Unit length subtracts 38 and whether extends message length field numerical value more than or equal to above-mentioned multiple spanning tree;
Whether above-mentioned Bridge Protocol Data Unit length subtracts 103 is 26 multiple; And
Whether above-mentioned multiple spanning tree to subtract 64 be 26 multiple if extending message length field numerical value.
13. the system of Multiple Spanning Tree Protocol compatibility as claimed in claim 11, it is characterized in that, after the communication port record that above-mentioned agreement identification module is provided is set at and meets above-mentioned first Multiple Spanning Tree Protocol, also in order to remove an information of identification code, above-mentioned information of identification code is in order to the relevant information of expression with above-mentioned first Multiple Spanning Tree Protocol transmission data, and above-mentioned information of identification code is recorded in the communication port of above-mentioned reception Bridge Protocol Data Unit.
14. the system of Multiple Spanning Tree Protocol compatibility as claimed in claim 11, it is characterized in that, before the communication port record that above-mentioned agreement identification module is provided is set at and meets above-mentioned second Multiple Spanning Tree Protocol, also in order to write down an information of identification code, above-mentioned information of identification code is in order to the relevant information of expression with above-mentioned second Multiple Spanning Tree Protocol transmission data, and above-mentioned information of identification code is recorded in the communication port of above-mentioned reception Bridge Protocol Data Unit.
15. the system of Multiple Spanning Tree Protocol compatibility as claimed in claim 11, it is characterized in that, whether the multiple spanning tree zone configuration of the above-mentioned Bridge Protocol Data Unit of above-mentioned identification and above-mentioned interchanger is identical is the function that is provided by regional inspection module, is to finish by following any one condition:
Whether the configuration name field in the above-mentioned Bridge Protocol Data Unit is identical with the configuration name field of above-mentioned interchanger; And
Whether the MSTI information content in the above-mentioned Bridge Protocol Data Unit and above-mentioned interchanger are set up qualified expansion tree quantity identical.
16. the system of Multiple Spanning Tree Protocol compatibility as claimed in claim 11 is characterized in that, above-mentioned first Multiple Spanning Tree Protocol is the ieee standard Multiple Spanning Tree Protocol, is the Multiple Spanning Tree Protocol of interchanger itself.
17. the system of Multiple Spanning Tree Protocol compatibility as claimed in claim 11 is characterized in that, above-mentioned second Multiple Spanning Tree Protocol is Cisco's standard Multiple Spanning Tree Protocol, is the known compatible Multiple Spanning Tree Protocol of interchanger.
18. the system of Multiple Spanning Tree Protocol compatibility as claimed in claim 10 is characterized in that, above-mentioned inspection module when carrying out above-mentioned transmission check problem, also in order to:
Whether the communication port record of differentiating in the above-mentioned interchanger meets above-mentioned second Multiple Spanning Tree Protocol; And
When above-mentioned communication port meets above-mentioned second Multiple Spanning Tree Protocol, encapsulate above-mentioned Bridge Protocol Data Unit and meet above-mentioned second Multiple Spanning Tree Protocol.
19. an interchanger is characterized in that described interchanger comprises the system of the arbitrary described Multiple Spanning Tree Protocol compatibility of claim 10 to 18.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610000387A CN1997002B (en) | 2006-01-06 | 2006-01-06 | Compatible method, system and related switch for multi-fold expansion tree protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610000387A CN1997002B (en) | 2006-01-06 | 2006-01-06 | Compatible method, system and related switch for multi-fold expansion tree protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1997002A CN1997002A (en) | 2007-07-11 |
| CN1997002B true CN1997002B (en) | 2010-05-12 |
Family
ID=38251932
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200610000387A Expired - Fee Related CN1997002B (en) | 2006-01-06 | 2006-01-06 | Compatible method, system and related switch for multi-fold expansion tree protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1997002B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1353902A (en) * | 1999-12-06 | 2002-06-12 | 阿尔卡塔尔公司 | Telecommunication gateway between private network and mobile network |
| US20030152085A1 (en) * | 1996-12-25 | 2003-08-14 | Tetsuro Yoshimoto | IP switch, interface circuit and ATM switch used for IP switch, and IP switch network system |
| US6667985B1 (en) * | 1998-10-28 | 2003-12-23 | 3Com Technologies | Communication switch including input bandwidth throttling to reduce output congestion |
| WO2004039015A2 (en) * | 2002-10-24 | 2004-05-06 | Cisco Technology, Inc. | Modified spanning tree protocol for metropolitan area network |
| CN1620056A (en) * | 2003-11-21 | 2005-05-25 | 诠盛科技股份有限公司 | Bridge protocol data unit examination method using bridge address allowal table |
-
2006
- 2006-01-06 CN CN200610000387A patent/CN1997002B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030152085A1 (en) * | 1996-12-25 | 2003-08-14 | Tetsuro Yoshimoto | IP switch, interface circuit and ATM switch used for IP switch, and IP switch network system |
| US6667985B1 (en) * | 1998-10-28 | 2003-12-23 | 3Com Technologies | Communication switch including input bandwidth throttling to reduce output congestion |
| CN1353902A (en) * | 1999-12-06 | 2002-06-12 | 阿尔卡塔尔公司 | Telecommunication gateway between private network and mobile network |
| WO2004039015A2 (en) * | 2002-10-24 | 2004-05-06 | Cisco Technology, Inc. | Modified spanning tree protocol for metropolitan area network |
| CN1620056A (en) * | 2003-11-21 | 2005-05-25 | 诠盛科技股份有限公司 | Bridge protocol data unit examination method using bridge address allowal table |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1997002A (en) | 2007-07-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102347879A (en) | D-BUS high-speed bus technology based on ring type Ethernet and auxiliary network | |
| JPS61196645A (en) | Apparatus and method for executing communication protocol conversion | |
| CN110177013A (en) | A kind of EtherCAT master-salve station design and implementation methods based on FPGA | |
| CN102812744A (en) | Inter-working of EFM-OAM and CFM-OAM for mobile backhaul networks | |
| CN103685419A (en) | Business processing method and apparatus | |
| CN108111494A (en) | A kind of protocol conversion apparatus of 1553B buses and FlexRay buses | |
| CN113115346A (en) | Gateway multi-protocol conversion device based on 5G and method thereof | |
| CN100512168C (en) | Apparatus for connecting wireless network with at least one other network | |
| CN106506303A (en) | A kind of main station system of controller real-time ethernet EtherCAT | |
| CN103392315B (en) | Stand, target device and starting device | |
| CN100463426C (en) | Sevice quality control/device and method based on virtual network marker | |
| CN113194494B (en) | Air interface resource control method, device, network side equipment and terminal | |
| CN1917508B (en) | Device of wireless local area network and method for numbering serial number of frames | |
| US20070263638A1 (en) | Setting Up of a Wireless Network by Determining and Utilizing Local Topology Information | |
| CN1997002B (en) | Compatible method, system and related switch for multi-fold expansion tree protocol | |
| CN102742317B (en) | Communication system, communication method and communication apparatus | |
| CN102081383B (en) | Device and method for secure network protocol for field control | |
| CN114039898A (en) | Communication system | |
| CN109802877A (en) | A kind of CAN bus based Communication System Design | |
| CN105448337B (en) | Data recording system and data burning method | |
| CN109451597B (en) | WiFi amplifier automatic networking system and method thereof | |
| US6295280B1 (en) | Method for network node recognition | |
| CN101471901B (en) | Method and device for implementing mutual identification and interconnection of various wireless protocol equipment | |
| CN110784365A (en) | Standby device of station control layer and entity device of transformer substation and automatic online method thereof | |
| WO2013185535A1 (en) | Apparatus, method, and system for convergence and compatibility of protocol stack |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100512 Termination date: 20210106 |