CN1997002A - 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
- CN1997002A CN1997002A CNA2006100003876A CN200610000387A CN1997002A CN 1997002 A CN1997002 A CN 1997002A CN A2006100003876 A CNA2006100003876 A CN A2006100003876A CN 200610000387 A CN200610000387 A CN 200610000387A CN 1997002 A CN1997002 A CN 1997002A
- Authority
- CN
- China
- Prior art keywords
- mentioned
- fold expansion
- data unit
- expansion tree
- tree protocol
- 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.)
- Granted
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 multiple extensive 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 multi-fold expansion tree protocols that is applicable to the invention relates to a kind of multi-fold expansion 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 multi-fold expansion tree protocol (MSTP) just arises at the historic moment, and that is to say to use the multiple topology (multiple topology) that multi-fold expansion tree protocol can calculate network.Multi-fold expansion tree protocol is be that unit operates with zone (region), and the interchanger in the same area has identical iterated extension and sets 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 multi-fold expansion 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 multi-fold expansion tree protocol (IEEE 802.1 standard) and meet between the interchanger of Cisco's multi-fold expansion 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 multi-fold expansion tree protocol), and interchanger 104 is standard interchanger (meeting the ieee standard multi-fold expansion 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 multi-fold expansion 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 multi-fold expansion 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 iterated extension 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 multi-fold expansion tree protocol compatibility, at first provide inspection module between standard iterated extension tree module and Ethernet driver module, avoid changing existing iterated extension tree module.Inspection module is in order to carry out the acceptance inspection program and to transmit check problem.Inspection module, standard iterated extension 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 when Bridge Protocol Data Unit is set module from the standard iterated extension, carry out the transmission check problem for Bridge Protocol Data Unit.
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 iterated extension tree format of interchanger own or known compatible iterated extension tree format.The iterated extension tree of interchanger own can be the ieee standard multi-fold expansion tree protocol, and known compatible iterated extension tree can be Cisco's standard multi-fold expansion tree protocol.
Meet the iterated extension tree format of interchanger own or be unknown form as Bridge Protocol Data Unit.Whether the multi-fold expansion 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 multi-fold expansion tree protocol, can be by obtaining in the Bridge Protocol Data Unit.
Meet known compatible iterated extension tree format 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 own iterated extension tree of interchanger, identical with configuration title and the qualified expansion tree quantity of the iterated extension tree of interchanger own as confirming configuration name field (Configuration Name) and MSTI information (MSTI message) quantity in the Bridge Protocol Data Unit.When the regional configuration and setting of determining the own iterated extension tree of Bridge Protocol Data Unit and interchanger was consistent, whether 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 that multi-fold expansion tree protocol that interchanger receives the communication port of this Bridge Protocol Data Unit writes down and meet.As do not meet, then adjust the agreement record of this communication port.
When judging that Bridge Protocol Data Unit is different with the iterated extension tree format of interchanger own, but when meeting known compatible iterated extension tree format, the Bridge Protocol Data Unit form encapsulated again be converted to the form that the iterated extension of interchanger own is set.Transfer to the iterated extension tree module of interchanger and carry out the agreement running.
The transmission check problem comprises the following steps, differentiates at first whether the multi-fold expansion tree protocol record that interchanger transmits the communication port of this Bridge Protocol Data Unit is known compatible multi-fold expansion tree protocol.
Agreement record as this communication port meets known compatible multi-fold expansion tree protocol, the Bridge Protocol Data Unit form is encapsulated again be converted to known compatible iterated extension tree format.The Ethernet driver module of transferring to interchanger carries out package and transmits.
In addition, the present invention also proposes a kind of interchanger, comprises an inspection module, and it is in order to carry out the method step of foregoing multi-fold expansion tree protocol compatibility.
In addition, the present invention also proposes a kind of system of multi-fold expansion 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 iterated extension 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 iterated extension 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 multi-fold expansion tree protocol record, uses 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, uses when carrying out the acceptance inspection program.The package modular converter comprises Bridge Protocol Data Unit encapsulation function again, uses when carrying out the acceptance inspection program and transmitting check problem, and the conversion package is known iterated extension tree format.
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 multi-fold expansion 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 multi-fold expansion tree protocol.
Fig. 4 b shows the field format of the Bridge Protocol Data Unit that meets Cisco's standard multi-fold expansion tree protocol.
Fig. 4 c shows the setting identification code field format of the Bridge Protocol Data Unit that meets the ieee standard multi-fold expansion tree protocol.
Fig. 4 d shows the setting identification code field format of the Bridge Protocol Data Unit that meets Cisco's standard multi-fold expansion tree protocol.
Fig. 4 e shows the MSTI information field form of the Bridge Protocol Data Unit that meets the ieee standard multi-fold expansion tree protocol.
Fig. 4 f shows the MSTI information field form of the Bridge Protocol Data Unit that meets Cisco's standard multi-fold expansion 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 106-iterated extension is set formed Virtual switch;
108,110, the 112-iterated extension is set formed zone;
The 20-interchanger;
The 200-inspection module;
202-IEEE standard iterated extension 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 (ConfigurationName) of 440-iterated extension tree setting identification code;
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 iterated extension tree);
504-Cisco interchanger (supporting Cisco standard iterated extension tree);
506, the 516-iterated extension is set formed zone;
512-Cisco standard iterated extension is set formed zone;
514-IEEE standard iterated extension is set formed zone.
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 multi-fold expansion tree protocol compatibility.The multi-fold expansion tree protocol of interchanger itself is an example with ieee standard iterated extension tree module, and the known compatible multi-fold expansion tree protocol of interchanger is an example with Cisco's standard iterated extension tree module.
At first, provide inspection module 200 in ieee standard iterated extension 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 iterated extension tree module 202 and Ethernet driver module 204 are arranged in the interchanger 20.
When judging that Bridge Protocol Data Unit meets ieee standard iterated extension tree format, the inspection interchanger receives whether the multi-fold expansion tree protocol record of the communication port of this Bridge Protocol Data Unit is made as Cisco standard iterated extension tree (step S304).Be recorded as Cisco standard iterated extension tree as this agreement, then the information of identification code record (step S308) that this agreement record is set at ieee standard iterated extension tree (step S306) and removes this communication port.
When judging that Bridge Protocol Data Unit meets Cisco's standard iterated extension tree format, carry out zone identification (step S310) by the Bridge Protocol Data Unit area validation function of area validation module 240.When the iterated extension 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 standard iterated extension tree (step S314).
At last, be Cisco's standard iterated extension tree format as Bridge Protocol Data Unit, the Bridge Protocol Data Unit by package modular converter 250 encapsulation function again is converted to ieee standard iterated extension tree format (step S316) with this Bridge Protocol Data Unit.Then, notice ieee standard iterated extension 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 multi-fold expansion tree protocol, and Fig. 4 b shows the Bridge Protocol Data Unit format fields that meets Cisco's standard multi-fold expansion tree protocol.Can following condition criterion be Cisco's iterated extension tree format, be that third edition length (Version 3 Length) field 400 numerical value in the Bridge Protocol Data Unit are 0, iterated extension tree in the Bridge Protocol Data Unit is extended 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 to be needed to extend the numerical value of message length field 410 more than or equal to the iterated extension tree, the total length of Bridge Protocol Data Unit subtracts 103 and is required to be 26 multiple, and iterated extension tree is extended 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 multi-fold expansion tree protocol, and Fig. 4 d is the form that shows the setting identification code field 412 that meets Cisco's standard multi-fold expansion tree protocol.Can following condition criterion ieee standard identical with the regional configuration and setting of Cisco standard iterated extension tree, promptly configuration title of the configuration title of setting identification code field 412 (Configuration Name) field 430 and MSTI information (MSTI message) quantity that comprises and the iterated extension tree of interchanger own and qualified expansion be set quantity and are conformed 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 multi-fold expansion tree protocol, Fig. 4 b shows the Bridge Protocol Data Unit format fields that meets Cisco's standard multi-fold expansion tree protocol, Fig. 4 e is the form that shows the MSTI information field (Message) 406 that meets the ieee standard multi-fold expansion tree protocol, and Fig. 4 d is the form that shows the MSTI information field 404 that meets Cisco's standard multi-fold expansion tree protocol.Cisco's standard iterated extension tree package form (Fig. 4 b) transfers ieee standard iterated extension 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 multi-fold expansion 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 Root Identity) 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 iterated extension tree module 202 transmission Bridge Protocol Data Units (step S320).Communication port multi-fold expansion 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 standard iterated extension tree, the Bridge Protocol Data Unit by package modular converter 250 encapsulation function again is converted to Cisco's standard iterated extension tree format (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 multi-fold expansion tree protocol, Fig. 4 b shows the Bridge Protocol Data Unit format fields that meets Cisco's standard multi-fold expansion tree protocol, Fig. 4 e is the form that shows the MSTI information field 406 that meets the ieee standard multi-fold expansion tree protocol, and Fig. 4 f is the form that shows the MSTI information field 404 that meets Cisco's standard multi-fold expansion tree protocol.(Fig. 4 a) transfers Cisco's standard iterated extension to and sets package form (Fig. 4 b) ieee standard iterated extension 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 multi-fold expansion tree protocol compatibility, comprises inspection module 200, and inspection module 200 comprises agreement identification module 230, area validation module 240 and package modular converter 250.Inspection module 200 is arranged at 204 of standard iterated extension 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 iterated extension 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 iterated extension tree format becomes Cisco's standard iterated extension tree format and conversion Cisco standard iterated extension tree format becomes ieee standard iterated extension tree format 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 multi-fold expansion tree protocol that interchanger 504 is for meeting the interchanger (to call Cisco's interchanger in the following text) of Cisco's standard multi-fold expansion tree protocol.When Cisco's interchanger 504 and reinforced interchanger 500 were 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 multi-fold expansion tree protocol), because the centre couples mutually with reinforced interchanger 510, therefore just can form new iterated extension 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 multi-fold expansion tree protocol compatibility is characterized in that comprising the following steps:
Provide an inspection module between a standard iterated extension 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 iterated extension 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 is set module from above-mentioned standard iterated extension, carry out above-mentioned transmission check problem for above-mentioned Bridge Protocol Data Unit.
2. the method for multi-fold expansion 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 multi-fold expansion tree protocol, whether a communication port of differentiating in the above-mentioned interchanger is recorded as one second multi-fold expansion tree protocol;
When above-mentioned communication port record meets above-mentioned second multi-fold expansion tree protocol, above-mentioned communication port is set at meets above-mentioned first multi-fold expansion tree protocol;
When judging that above-mentioned Bridge Protocol Data Unit meets above-mentioned second multi-fold expansion tree protocol, whether discerning above-mentioned Bridge Protocol Data Unit and the iterated extension of above-mentioned interchanger, to set regional configuration identical;
When the above-mentioned Bridge Protocol Data Unit and the iterated extension of above-mentioned interchanger are set regional configuration when identical, above-mentioned communication port record is set at meet above-mentioned second multi-fold expansion tree protocol; And
When judging that above-mentioned Bridge Protocol Data Unit meets above-mentioned second multi-fold expansion tree protocol, encapsulate above-mentioned Bridge Protocol Data Unit for meeting the above-mentioned first multi-fold expansion tree protocol form.
3. the method for multi-fold expansion 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 with following at least one step:
Whether a third edition length field numerical value of differentiating in the above-mentioned Bridge Protocol Data Unit is 0;
Whether the iterated extension 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 iterated extension tree;
Whether above-mentioned Bridge Protocol Data Unit total length subtracts 103 is 26 multiple; And
Whether above-mentioned iterated extension tree to subtract 64 be 26 multiple if being extended message length field numerical value.
4. the method for multi-fold expansion 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 multi-fold expansion 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 multi-fold expansion 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 multi-fold expansion 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 multi-fold expansion 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 multi-fold expansion 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 multi-fold expansion tree protocol compatibility as claimed in claim 2 is characterized in that, the step whether the iterated extension tree zone of the above-mentioned Bridge Protocol Data Unit of above-mentioned identification and above-mentioned interchanger is identical is to finish with following at least 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 multi-fold expansion tree protocol compatibility as claimed in claim 2 is characterized in that, above-mentioned first multi-fold expansion tree protocol is the ieee standard multi-fold expansion tree protocol, and it is the multi-fold expansion tree protocol of interchanger itself.
8. the method for multi-fold expansion tree protocol compatibility as claimed in claim 2 is characterized in that, above-mentioned second multi-fold expansion tree protocol is Cisco's standard multi-fold expansion tree protocol, and it is the known compatible multi-fold expansion tree protocol of interchanger.
9. the method for multi-fold expansion 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 multi-fold expansion tree protocol; And
When above-mentioned communication port meets above-mentioned second multi-fold expansion tree protocol, encapsulate above-mentioned Bridge Protocol Data Unit and meet above-mentioned second multi-fold expansion tree protocol.
10. an interchanger is characterized in that comprising an inspection module, and above-mentioned inspection module is carried out the method as each described multi-fold expansion tree protocol compatibility in the claim 1 to 9.
11. the system of a multi-fold expansion tree protocol compatibility is characterized in that comprising:
One inspection module, it is arranged between a standard iterated extension 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 iterated extension 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 multi-fold expansion 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.
12. the system of multi-fold expansion tree protocol compatibility as claimed in claim 11 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 multi-fold expansion tree protocol, whether a communication port of differentiating in the above-mentioned interchanger is recorded as one second multi-fold expansion tree protocol;
When above-mentioned communication port record meets above-mentioned second multi-fold expansion tree protocol, above-mentioned communication port is set at meets above-mentioned first multi-fold expansion tree protocol;
When judging that above-mentioned Bridge Protocol Data Unit meets above-mentioned second multi-fold expansion tree protocol, whether discerning above-mentioned Bridge Protocol Data Unit and the iterated extension of above-mentioned interchanger, to set regional configuration identical;
When the above-mentioned Bridge Protocol Data Unit and the iterated extension of above-mentioned interchanger are set regional configuration when identical, above-mentioned communication port record is set at meet above-mentioned second multi-fold expansion tree protocol; And
When judging that above-mentioned Bridge Protocol Data Unit meets above-mentioned second multi-fold expansion tree protocol, encapsulate above-mentioned Bridge Protocol Data Unit for meeting the above-mentioned first multi-fold expansion tree protocol form.
13. the system of multi-fold expansion tree protocol compatibility as claimed in claim 12 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 with following at least one:
Whether the third edition length field numerical value in the above-mentioned Bridge Protocol Data Unit is 0;
Whether iterated extension 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 iterated extension tree;
Whether above-mentioned Bridge Protocol Data Unit length subtracts 103 is 26 multiple; And
Whether above-mentioned iterated extension tree to subtract 64 be 26 multiple if being extended message length field numerical value.
14. the system of multi-fold expansion tree protocol compatibility as claimed in claim 12, 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 multi-fold expansion 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 multi-fold expansion 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 multi-fold expansion tree protocol compatibility as claimed in claim 12, 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 multi-fold expansion 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 multi-fold expansion 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.
16. the system of multi-fold expansion tree protocol compatibility as claimed in claim 12, it is characterized in that, whether the above-mentioned Bridge Protocol Data Unit of above-mentioned identification and the iterated extension of above-mentioned interchanger are set regional configuration identical is the function that is provided by regional inspection module, is to finish with following at least one:
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.
17. the system of multi-fold expansion tree protocol compatibility as claimed in claim 12 is characterized in that, above-mentioned first multi-fold expansion tree protocol is the ieee standard multi-fold expansion tree protocol, is the multi-fold expansion tree protocol of interchanger itself.
18. the system of multi-fold expansion tree protocol compatibility as claimed in claim 12 is characterized in that, above-mentioned second multi-fold expansion tree protocol is Cisco's standard multi-fold expansion tree protocol, is the known compatible multi-fold expansion tree protocol of interchanger.
19. the system of multi-fold expansion tree protocol compatibility as claimed in claim 11 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 multi-fold expansion tree protocol; And
When above-mentioned communication port meets above-mentioned second multi-fold expansion tree protocol, encapsulate above-mentioned Bridge Protocol Data Unit and meet above-mentioned second multi-fold expansion tree protocol.
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 true CN1997002A (en) | 2007-07-11 |
| CN1997002B 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) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH10190733A (en) * | 1996-12-25 | 1998-07-21 | Hitachi Ltd | Ip switch, interface circuit and atm switch used for the 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 |
| FR2802042B1 (en) * | 1999-12-06 | 2002-05-31 | Cit Alcatel | TELECOMMUNICATION GATEWAY BETWEEN A PRIVATE NETWORK AND A MOBILE NETWORK |
| US7292581B2 (en) * | 2002-10-24 | 2007-11-06 | Cisco Technology, Inc. | Large-scale layer 2 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
Also Published As
| Publication number | Publication date |
|---|---|
| CN1997002B (en) | 2010-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102347879A (en) | D-BUS high-speed bus technology based on ring type Ethernet and auxiliary network | |
| CN110177013A (en) | A kind of EtherCAT master-salve station design and implementation methods based on FPGA | |
| CN102144420B (en) | For the agency mechanism of grid type network | |
| WO2006095787A1 (en) | Relay device | |
| CN102812744A (en) | Inter-working of EFM-OAM and CFM-OAM for mobile backhaul networks | |
| CN103814605A (en) | Method and device for rate matching | |
| CA2535134C (en) | Compatible methods and systems for multiple spanning tree protocols | |
| CN103685419A (en) | Business processing method and apparatus | |
| 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 | |
| CN111510363A (en) | Slave station conversion device based on MODBUS protocol and control method thereof | |
| CN100463426C (en) | Sevice quality control/device and method based on virtual network marker | |
| CN106657377B (en) | A kind of WIA-PA/ interconnects manufacture network information service adapter and implementation method entirely | |
| CN1997002B (en) | Compatible method, system and related switch for multi-fold expansion tree protocol | |
| CN112468755B (en) | Data transmission method and network terminal equipment | |
| CN102081383B (en) | Device and method for secure network protocol for field control | |
| CN201323593Y (en) | Network device for automatic smooth switching between various network topology structures | |
| US6295280B1 (en) | Method for network node recognition | |
| CN109451597B (en) | WiFi amplifier automatic networking system and method thereof | |
| CN106992896B (en) | SDN connection judgment method, apparatus and system | |
| 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 | |
| CN1735072B (en) | Improved realization process for WLAN net bridge transparent bridge |
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 |
Granted publication date: 20100512 Termination date: 20210106 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |