CN102684914B - Method and system for achieving bridge interface linkage - Google Patents
Method and system for achieving bridge interface linkage Download PDFInfo
- Publication number
- CN102684914B CN102684914B CN201210122174.6A CN201210122174A CN102684914B CN 102684914 B CN102684914 B CN 102684914B CN 201210122174 A CN201210122174 A CN 201210122174A CN 102684914 B CN102684914 B CN 102684914B
- Authority
- CN
- China
- Prior art keywords
- bridge
- interface
- sub
- described current
- current bridge
- 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
Landscapes
- Small-Scale Networks (AREA)
Abstract
The invention discloses a method and a system for achieving bridge interface linkage and relates to the technical field of network communication. The method comprises step one, judging whether a current bridge starts the interface linkage when a subinterface of the current bridge is in down state; step two, if the current bridge starts the interface linkage, executing step three, and if the current bridge does not start the interface linkage, executing step four; step three, performing the interface linkage processing process and returning to step one; and step four, removing a media access control (mac) address table item corresponding to the subinterface in the down state in a mac address table, and returning to step one. When the link state of the subinterface of the bridge is abnormal, a dynamic route can find abnormality as soon as possible through the interface linkage processing process and enable other paths to replace a fault path.
Description
Technical field
The present invention relates to network communications technology field, particularly a kind of implementation method and system of bridge interface interlock.
Background technology
Bridge is used at least two similar networks to couple together, and the circulation of network data is managed.It works in data link layer, distance or scope that not only can extended network, and performance, reliability and the fail safe that can improve network.After being connected by bridge with network 2 when network 1, bridge receives the packet that network 1 sends, and checks the address in packet, if address belongs to network 1, it is just abandoned, and on the contrary, if the address of network 2, it just continues to send to network 2.Can utilize like this bridge isolation information, same network number is divided into multiple network segments (belonging to same network number), isolate the safe network segment, prevent the user's unauthorized access in other network segment.Due to the segmentation of network, each network segment relatively independent (belonging to same network number), the fault of a network segment can not have influence on the operation of another network segment.
With reference to Fig. 1, suppose that described network 1 and network 2 are connected with 2 sub-interface g0/0 and g0/1 on same bridge (transparent bridge) respectively.In the time that network 1 and network 2 will be with external network generation data interactions, need to first pass through bridge joint mouth, that is to say 3 layers mutual on, external network is not also known the existence of sub-interface g0/0 and g0/1, is just carrying out data interaction with bridge joint mouth.There is extremely (such as interface fault, netting twine fault etc.) in the Link State of supposing sub-interface g0/0, in down state, external network can not perceive this event, and message still can be sent to bridge joint mouth, but in fact now fault has appearred in bridge.If do not taken measures, link backup, two-node cluster hot backup and Spanning-Tree Protocol (Spanning Tree Protocol, STP) etc. just all cannot be brought into play real effect.
Summary of the invention
(1) technical problem that will solve
The technical problem to be solved in the present invention is: how occur when abnormal, allowing as early as possible dynamic route discovery abnormal at the Link State of the sub-interface of bridge, allow other path replace failure path.
(2) technical scheme
For solving the problems of the technologies described above, the invention provides a kind of implementation method of bridge interface interlock, said method comprising the steps of:
S1: in the time that down state has appearred in the sub-interface of current bridge, judge whether described current bridge has started interface linkage;
S2: if so, perform step S3, otherwise execution step S4;
S3: carry out interface linkage processing procedure, return to step S1;
S4: mac the address list item corresponding sub-interface that has occurred down state in mac address table is removed, returned to step S1.
Preferably, in step S3, described interface linkage processing procedure is further comprising the steps:
S31: check that the bridge joint mouth of described current bridge, whether in up state, if so, performs step S32;
S32: check that the current sub-interface of described current bridge, whether in down state, if so, performs step S33, otherwise execution step S34;
S33: all sub-interfaces of described current bridge and bridge mouth are all placed in to down state, and delete all sub-interfaces and the corresponding mac address list item of bridge mouth of current bridge described in described mac address table, return to step S1;
S34: whether all sub-interfaces that judge described current bridge all check, if so, return to step S1, otherwise using the sub-interface not being inspected on described current bridge as described current sub-interface, return to step S32.
Preferably, in step S31, the bridge joint mouth of described current bridge, in the time of up state, is not carried out following steps:
S35: check that the current sub-interface of described current bridge, whether in up state, if so, processes other sub-interface of described current bridge, execution step S36, otherwise execution step S38;
S36: check that other sub-interface of described current bridge, whether all in up state, if so, processes the bridge joint mouth of described current bridge, to make the bridge joint mouth of described current bridge in up state, return to step S1, otherwise execution step S37;
S37: all sub-interfaces of described current bridge are all set to down state, return to step S1;
S38: whether all sub-interfaces that judge described current bridge all check, if so, return to step S1, otherwise using the sub-interface not being inspected on described current bridge as described current sub-interface, return to step S35.
Preferably, further comprising the steps of between step S36 and step S37:
S361: judge whether to have exceeded Preset Time, if so, perform step S37, otherwise return to step S36.
The system that realizes that the invention also discloses a kind of bridge interface interlock, described system comprises:
Judge module, in the time that down state has appearred in the sub-interface of current bridge, judges whether described current bridge has started interface linkage;
Select Executive Module, for if so, carrying out processing module, remove module otherwise carry out;
Processing module, for carrying out interface linkage processing procedure, returns to judge module;
Remove module, remove for mac address list item corresponding to sub-interface that mac address table has been occurred to down state, return to judge module.
(3) beneficial effect
The present invention occurs when abnormal, by interface linkage processing procedure, can allowing as soon as possible dynamic route discovery abnormal at the Link State of the sub-interface of bridge, allows other path replace failure path.
Brief description of the drawings
Fig. 1 is the structural representation with the bridge of two sub-interfaces;
Fig. 2 is according to the flow chart of the implementation method of the bridge interface interlock of one embodiment of the present invention;
Fig. 3 is according to the flow chart of the implementation method of the bridge interface interlock of an embodiment of the present invention.
Embodiment
Below in conjunction with drawings and Examples, the specific embodiment of the present invention is described in further detail.Following examples are used for illustrating the present invention, but are not used for limiting the scope of the invention.
Fig. 2 is according to the flow chart of the implementation method of the bridge interface interlock of one embodiment of the present invention; With reference to Fig. 2, the method for present embodiment comprises the following steps:
S1: occurred that at the sub-interface of current bridge (down state is herein physics down state to down state, described physics down state refers to that device port is without line, or there is line but line disconnects, break without connection device or line in the opposite end of for example line) time, judge whether described current bridge has started interface linkage;
S2: if so, perform step S3, otherwise execution step S4;
S3: carry out interface linkage processing procedure, return to step S1;
S4: mac the address list item corresponding sub-interface that has occurred down state in mac address table is removed, returned to step S1.
What port interlock will be done is exactly to allow as early as possible dynamic route discovery abnormal, and upgrades routing table, allows other path replace failure path.Taking the bridge shown in Fig. 1 as example, in the time detecting that down state (down state is herein physics down state) appears in sub-interface g0/0, just other all sub-interfaces on bridge all down (down state is herein logic down state, described logic down state refers to force lower electricity) fall, bridge mouth also down (down state is herein logic down state) is fallen simultaneously.Dynamic routing will note abnormalities and upgrade like this, and network is expected to recover as early as possible, and preferably, in step S3, described interface linkage processing procedure is further comprising the steps:
S31: check that the bridge joint mouth of described current bridge, whether in up state (up state is herein physics up state, and described physics up state refers to that device port normally connects), if so, performs step S32;
S32: check that the current sub-interface of described current bridge, whether in down state (down state is herein physics down state), if so, performs step S33, otherwise execution step S34;
S33: all sub-interfaces of described current bridge and bridge mouth are all placed in to down state (down state is herein logic down state), and delete all sub-interfaces and the corresponding mac address list item of bridge mouth of current bridge described in described mac address table, return to step S1;
S34: whether all sub-interfaces that judge described current bridge all check, if so, return to step S1, otherwise using the sub-interface not being inspected on described current bridge as described current sub-interface, return to step S32.
In the time that the state of the sub-interface in down state (down state is herein physics down state) becomes up state (up state is herein physics up state), just need to attempt other total interfaces under bridge to be set to up state (up state is herein logic up state).After fault is excluded, there is abnormal sub-interface before and likely again become up state (up state is herein physics up state), now should attempt allowing sub-interface under bridge all again in up state (up state is herein physics up state).If can both be in up state (up state be herein physics up state), illustrate that whole bridge can normally work, now again bridge mouth is also set to up state (up state is herein physics up state), there is else if the state of sub-interface can not be in up state (up state is herein physics up state), the total interface under bridge is all set to down state (down state is herein logic down state), now bridge mouth is still down state (down state is herein physics down state), preferably, in step S31, the bridge joint mouth of described current bridge is not or not the time of up state, carry out following steps:
S35: check that whether the current sub-interface of described current bridge is in up state (up state is herein physics up state), if, other sub-interface of described current bridge is processed, (up state is herein logic up state to attempt that other sub-interface of current bridge is all placed in to up state, described logic up state refers to force to power on by modes such as order lines), execution step S36, otherwise execution step S38;
S36: check that whether other sub-interface of described current bridge is all in up state (up state is herein physics up state), if, the bridge joint mouth of described current bridge is processed, to make the bridge joint mouth of described current bridge in up state (up state is herein as physics up state), return to step S1, otherwise execution step S37;
S37: all sub-interfaces of described current bridge are all set to down state (down state is herein logic down state), return to step S1;
S38: whether all sub-interfaces that judge described current bridge all check, if so, return to step S1, otherwise using the sub-interface not being inspected on described current bridge as described current sub-interface, return to step S35.
For ensureing certain processing time, preferably, further comprising the steps of between step S36 and step S37:
S361: judge whether to have exceeded Preset Time, if so, perform step S37, otherwise return to step S36.
Embodiment
Fig. 3 is according to the flow chart of the implementation method of the bridge interface interlock of an embodiment of the present invention; With reference to Fig. 3, in the present embodiment, handling process and above-mentioned execution mode are basic identical, and difference is: described Preset Time is 10 seconds; Before S4 returns to step S1, step S34 returns before step S1 and S38 has all carried out the dormancy of 1 second before returning to step S1.
The system that realizes that the invention also discloses a kind of bridge interface interlock, described system comprises:
Judge module, in the time that down state has appearred in the sub-interface of current bridge, judges whether described current bridge has started interface linkage;
Select Executive Module, for if so, carrying out processing module, remove module otherwise carry out;
Processing module, for carrying out interface linkage processing procedure, returns to judge module;
Remove module, remove for mac address list item corresponding to sub-interface that mac address table has been occurred to down state, return to judge module.
Above execution mode is only for illustrating the present invention; and be not limitation of the present invention; the those of ordinary skill in relevant technologies field; without departing from the spirit and scope of the present invention; can also make a variety of changes and modification; therefore all technical schemes that are equal to also belong to category of the present invention, and scope of patent protection of the present invention should be defined by the claims.
Claims (4)
1. an implementation method for bridge interface interlock, is characterized in that, said method comprising the steps of:
S1: in the time that down state has appearred in the sub-interface of current bridge, judge whether described current bridge has started interface linkage;
S2: if so, perform step S3, otherwise execution step S4;
S3: carry out interface linkage processing procedure, return to step S1;
S4: mac the address list item corresponding sub-interface that has occurred down state in mac address table is removed, returned to step S1;
Wherein, in step S3, described interface linkage processing procedure is further comprising the steps:
S31: check that the bridge joint mouth of described current bridge, whether in up state, if so, performs step S32;
S32: check that the current sub-interface of described current bridge, whether in down state, if so, performs step S33, otherwise execution step S34;
S33: all sub-interfaces of described current bridge and bridge mouth are all placed in to down state, and delete all sub-interfaces and the corresponding mac address list item of bridge mouth of current bridge described in described mac address table, return to step S1;
S34: whether all sub-interfaces that judge described current bridge all check, if so, return to step S1, otherwise using the sub-interface not being inspected on described current bridge as described current sub-interface, return to step S32.
2. the method for claim 1, is characterized in that, in step S31, the bridge joint mouth of described current bridge, in the time of up state, is not carried out following steps:
S35: check that the current sub-interface of described current bridge, whether in up state, if so, processes other sub-interface of described current bridge, execution step S36, otherwise execution step S38;
S36: check that other sub-interface of described current bridge, whether all in up state, if so, processes the bridge joint mouth of described current bridge, to make the bridge joint mouth of described current bridge in up state, return to step S1, otherwise execution step S37;
S37: all sub-interfaces of described current bridge are all set to down state, return to step S1;
S38: whether all sub-interfaces that judge described current bridge all check, if so, return to step S1, otherwise using the sub-interface not being inspected on described current bridge as described current sub-interface, return to step S35.
3. method as claimed in claim 2, is characterized in that, further comprising the steps of between step S36 and step S37:
S361: judge whether to have exceeded Preset Time, if so, perform step S37, otherwise return to step S36.
4. the system that realizes of bridge interface interlock, is characterized in that, described system comprises:
Judge module, in the time that down state has appearred in the sub-interface of current bridge, judges whether described current bridge has started interface linkage;
Select Executive Module, for if so, carrying out processing module, remove module otherwise carry out;
Processing module, for carrying out interface linkage processing procedure, returns to judge module;
Remove module, remove for mac address list item corresponding to sub-interface that mac address table has been occurred to down state, return to judge module;
Wherein, described processing module is carried out interface linkage processing procedure by carrying out following steps:
S31: check that the bridge joint mouth of described current bridge, whether in up state, if so, performs step S32;
S32: check that the current sub-interface of described current bridge, whether in down state, if so, performs step S33, otherwise execution step S34;
S33: all sub-interfaces of described current bridge and bridge mouth are all placed in to down state, and delete all sub-interfaces and the corresponding mac address list item of bridge mouth of current bridge described in described mac address table;
S34: whether all sub-interfaces that judge described current bridge all check, otherwise using the sub-interface not being inspected on described current bridge as described current sub-interface, return to step S32.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210122174.6A CN102684914B (en) | 2012-04-23 | 2012-04-23 | Method and system for achieving bridge interface linkage |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210122174.6A CN102684914B (en) | 2012-04-23 | 2012-04-23 | Method and system for achieving bridge interface linkage |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102684914A CN102684914A (en) | 2012-09-19 |
| CN102684914B true CN102684914B (en) | 2014-12-10 |
Family
ID=46816309
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210122174.6A Expired - Fee Related CN102684914B (en) | 2012-04-23 | 2012-04-23 | Method and system for achieving bridge interface linkage |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102684914B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107968753B (en) * | 2016-10-20 | 2021-08-13 | 华为技术有限公司 | Method and device for modifying media access control address forwarding table |
| CN107948039B (en) * | 2017-11-17 | 2020-05-29 | 新华三信息安全技术有限公司 | Address table item processing method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1866922A (en) * | 2006-02-10 | 2006-11-22 | 华为技术有限公司 | Control system and data message transmission method in Ethernet |
| CN101151853A (en) * | 2005-05-31 | 2008-03-26 | 思科技术公司 | A spanning-tree protocol for wireless networks |
| WO2010135392A1 (en) * | 2009-05-20 | 2010-11-25 | Verizon Patent And Licensing, Inc. | Automatic protection switching of virtual connections |
-
2012
- 2012-04-23 CN CN201210122174.6A patent/CN102684914B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101151853A (en) * | 2005-05-31 | 2008-03-26 | 思科技术公司 | A spanning-tree protocol for wireless networks |
| CN1866922A (en) * | 2006-02-10 | 2006-11-22 | 华为技术有限公司 | Control system and data message transmission method in Ethernet |
| WO2010135392A1 (en) * | 2009-05-20 | 2010-11-25 | Verizon Patent And Licensing, Inc. | Automatic protection switching of virtual connections |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102684914A (en) | 2012-09-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102769568B (en) | A kind of flow forwarding method based on virtual switch cluster and system | |
| JP6076373B2 (en) | Technology to cope with changes in the state of interconnection nodes | |
| CN101588304B (en) | Implementation method of VRRP and device | |
| CN103684716B (en) | For carrying out the method and communication equipment of message transmission in industrial communication network | |
| CN105656645B (en) | The decision-making technique and device of the troubleshooting of stacking system | |
| CN101371474A (en) | System and method for detecting and recovering from virtual switch link failures | |
| CN102882704B (en) | Link protection method in the soft reboot escalation process of a kind of ISSU and equipment | |
| CN101291243A (en) | Split brain preventing method for highly available cluster system | |
| CN105765889B (en) | Extension bridge and the method being executed by it | |
| CN103856357B (en) | A kind of stacking system fault handling method and stacking system | |
| TWI455525B (en) | Recovery method for ring-based network | |
| CN104113428A (en) | Apparatus management device and method | |
| CN104618147A (en) | Longitudinally stacked system management method and system | |
| CN105871674A (en) | Ring protection link fault protection method, device and system | |
| CN104753707B (en) | A kind of system maintenance method and the network switching equipment | |
| CN103441878B (en) | The ownership processing method of PE equipment and equipment in VCF network | |
| CN103455464A (en) | Relay device, connection management method, and information communication system | |
| CN101237343B (en) | Method for quick failure switching and quick switching system | |
| CN102932183A (en) | Double-up link failure processing method and device | |
| JP4724763B2 (en) | Packet processing apparatus and interface unit | |
| CN102684914B (en) | Method and system for achieving bridge interface linkage | |
| CN101895444A (en) | Dual system of ATCA blade server, connection method and test method | |
| CN107979499A (en) | Network multipoint fault restoration methods based on stateful datum plane | |
| CN102651712B (en) | Node routing method of multiprocessor system, controller and multiprocessor system | |
| CN102142931B (en) | Method, device and system for preventing packet loss of E-TRUNK (Enhanced-Trunk) |
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: 20141210 Termination date: 20180423 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |