CN105939270B - Update the method and device of MSTP neighbor table - Google Patents
Update the method and device of MSTP neighbor table Download PDFInfo
- Publication number
- CN105939270B CN105939270B CN201610053801.3A CN201610053801A CN105939270B CN 105939270 B CN105939270 B CN 105939270B CN 201610053801 A CN201610053801 A CN 201610053801A CN 105939270 B CN105939270 B CN 105939270B
- Authority
- CN
- China
- Prior art keywords
- mstp
- port
- neighbor table
- table entry
- state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/48—Routing tree calculation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/54—Organization of routing tables
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
The application provides a kind of method and device for updating MSTP neighbor table, which comprises when network topology changes, the changed port MSTP of recording status;State change is arranged for the changed port MSTP of state to mark;Start MSTP agreement, the neighbor entry for being provided with the port MSTP of state change label is removed based on the MSTP agreement.In this application, because no longer removing in change in topology there is no the port of state change, it can solve the slower problem of prior art convergence rate.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for updating an MSTP (Multiple Spanning tree protocol) neighbor table.
Background
In the switching network, MSTP can 'prune' the loop network into a loop-free tree network, thereby avoiding the proliferation and endless loop of messages in the loop network. Meanwhile, the MSTP also has a link backup function, when the network topology changes, the original backup link can be switched to a new main link, so as to realize the link switching and convergence of the network flow.
In the prior art, when the network topology changes, the network device will clear all the neighbor entries of the non-current port, and then relearn the neighbor entries of the port. Because many ports in the neighbor table entry of the port have no state change, the convergence speed of the prior art is slow.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for updating a multiple spanning tree MSTP neighbor table to solve the problem of slow convergence rate in the prior art.
Specifically, the method is realized through the following technical scheme:
according to a first aspect of embodiments of the present application, a method for updating an MSTP neighbor table is provided, where the method is applied to a MSTP device, and the method includes:
when the network topology changes, recording the MSTP port with the changed state;
setting a state change mark for the MSTP port with the changed state;
starting the MSTP protocol, and clearing the neighbor table entry of the MSTP port with the state change mark based on the MSTP protocol.
Optionally, the MSTP port that records the state change includes:
receiving a topology change TC message sent by neighbor equipment;
and determining the MSTP port with the changed state based on the TC message.
Optionally, the clearing, based on the MSTP protocol, the neighbor table entry of the port for which the state change flag is set includes:
creating a work queue for clearing neighbor table entries;
starting the work queue, and clearing the neighbor table entry of the MSTP port with the state change mark in the MSTP port linked list based on the work queue;
and after the neighbor table entry of the MSTP port with the state change mark is cleared, logging off the work queue.
Optionally, the creating a work queue for clearing the neighbor table entry includes:
judging whether the equipment has an idle CPU or not;
when there is an idle CPU, a work queue is created on the idle CPU for clearing neighbor entries.
Optionally, the method further includes:
and when the network topology change is finished, reestablishing the neighbor table entry aiming at the MSTP port with the cleared neighbor table entry.
Optionally, the CPU used when the neighbor table entry is cleared for the MSTP port whose state changes is different from the CPU used when the neighbor table entry is reestablished for the MSTP port whose neighbor table entry has been cleared.
According to a second aspect of the embodiments of the present application, there is provided an apparatus for updating an MSTP neighbor table, the apparatus being applied to a MSTP device, the apparatus including:
the recording unit is used for recording the MSTP port with the changed state when the network topology is changed;
the setting unit is used for setting a state change mark for the MSTP port with the changed state;
and the clearing unit is used for starting the MSTP protocol and clearing the neighbor table entry of the MSTP port with the state change mark based on the MSTP protocol.
Optionally, the recording unit is specifically configured to:
receiving a topology change TC message sent by neighbor equipment;
and determining the MSTP port with the changed state based on the TC message.
Optionally, the clearing unit includes:
the creating subunit is used for creating a work queue for clearing the neighbor table entry;
the starting unit is used for starting the work queue and eliminating the neighbor table entry of the MSTP port which is provided with the state change mark in the MSTP port linked list based on the work queue;
and the logout subunit is used for logging out the work queue after the neighbor table entry of the MSTP port with the state change mark is cleared.
Optionally, the creating subunit is specifically configured to:
judging whether the equipment has an idle CPU or not;
when there is an idle CPU, a work queue is created on the idle CPU for clearing neighbor entries.
Optionally, the apparatus further comprises:
and the establishing unit is used for reestablishing the neighbor table entry aiming at the MSTP port with the removed neighbor table entry when the network topology change is finished.
Optionally, the CPU used when the neighbor table entry is cleared for the MSTP port whose state changes is different from the CPU used when the neighbor table entry is reestablished for the MSTP port whose neighbor table entry has been cleared.
The application provides a method and a device for updating an MSTP neighbor table, MSTP equipment can set a state change mark for an MSTP port with a changed state when network topology changes, and only clears the neighbor table entry of the MSTP port with the state change mark when clearing the neighbor table entry based on an MSTP protocol, thereby solving the problem of low system convergence speed caused by clearing the neighbor table entries of all ports in the prior art.
Drawings
Fig. 1 is a flowchart illustrating a method for updating an MSTP neighbor table in an embodiment of the present application;
FIG. 2 is a hardware structure diagram of the device where the apparatus for updating the MSTP neighbor table of the present application is located;
FIG. 3 is a block diagram of one embodiment of an apparatus for updating an MSTP neighbor table;
FIG. 4 is a block diagram of another embodiment of an apparatus for updating an MSTP neighbor table according to the present application;
fig. 5 is a block diagram of another embodiment of the apparatus of the present application in conjunction with a new MSTP neighbor table.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Referring to fig. 1, a flowchart of a method for updating an MSTP neighbor table in an embodiment of the present application is shown. The embodiment is applied to the MSTP device, and the MSTP device can be a router, a switch and the like. The embodiment comprises the following steps:
step 101: when the network topology changes, the MSTP port with the changed state is recorded.
When the network Topology changes, the MSTP device may obtain, based on a received TC (Topology Change) message sent by a neighboring device, an MSTP port whose state changes, and record the MSTP port.
The process may specifically be:
the MSTP device may obtain source port information of the TC packet from the TC packet, and then obtain port information connected to the source port from the current MSTP neighbor table. When the port information connected to the source port is acquired, the MSTP device may detect a current state of the port connected to the source port, compare the current state of the port connected to the source port with a state before the network topology changes, and then determine the port whose state changes according to a comparison result.
When the current state of the port connected with the source port is the same as the state before the network topology changes, determining that the state of the port does not change; conversely, when the current state of the port connected to the source port is different from the state before the network topology changes, it may be determined that the state of the port has changed, and at this time, the MSTP device may record the record as the port whose state has changed.
In one example, when a port on the MSTP device enables MSTP, the MSTP device may set a per-port fabric for the port, where the per-port fabric may hold information for the port. For example, the per-port fabric may save the current state of the port. The MSTP device may use a linked list to connect all the per-port structures corresponding to the ports that open MSTP, where the linked list may be referred to as a spanning tree port linked list.
When the network topology changes, the MSTP device may traverse a port connected to the source port of the TC packet in the spanning tree port linked list, and detect the current state of the port. When the current state of the port is the same as the state of the port in the spanning tree port linked list, determining that the state of the port is not changed; otherwise, it can be determined that the state of the port has changed.
In one example, the port may be logged when its status changes. The port may be recorded as a port whose state changes in the port-by-port structure corresponding to the port, or may be recorded as a port whose state changes in a newly created port state change table.
Step 102: and setting a state change mark for the MSTP port with the changed state.
After the MSTP port whose state has changed is recorded, a state change flag may be set for the MSTP port whose state has changed.
The MSTP device may preset a state change flag bit in each port structure, and may set the state change flag bit corresponding to the MSTP port when the state of the MSTP port changes.
In one hypothetical example, the per-port structure can be represented as:
when the state of the port corresponding to the per-port structure changes, the state change flag in the per-port structure may be set, that is, the value of state _ change may be set to 1; when the state of the port corresponding to the per-port configuration is not changed, the state change flag may not be set, that is, the value of state _ change may be set to 0.
In another example, the state change flag may be a particular identification corresponding to the MSTP port that changed.
Step 103: starting the MSTP protocol, and clearing the neighbor table entry of the MSTP port with the state change mark based on the MSTP protocol.
After setting the state change flag for the MSTP port whose state changes, the MSTP device may determine whether there is an idle CPU, and when there is an idle CPU, may create a work queue on the CPU for clearing the neighbor table entry.
The MSTP device may then start the work queue and clear the neighbor entries of the MSTP ports in the MSTP port linked list that have the state change flag set based on the work queue.
The cleaning process may specifically be:
and setting the neighbor table entry of the MSTP port with the state change mark in the MSTP port linked list as an invalid state.
The work queue may be de-registered when the neighbor entry purge for the MSTP port with the state change flag set is complete.
It should be noted that the CPU used when the neighbor table entry is cleared for the MSTP port whose state changes may be different from the CPU used when the neighbor table entry is reestablished for the MSTP port whose neighbor table entry has been cleared.
When the network topology change is over, the MSTP device may re-establish the neighbor table entries for the MSTP ports from which the neighbor table entries have been cleared. The MSTP device may traverse the MSTP port from which the neighbor table entry is removed in the MSTP port linked list, send a neighbor request packet, and reestablish the neighbor table entry.
In the application, when the network topology changes, the MSTP device may set a state change flag for the MSTP port whose state changes, and then may clear the neighbor table entry of the MSTP port whose state change flag is set based on the MSTP protocol, so as to achieve the purpose of updating the MSTP neighbor table. In the application, because the port without state change in the topology change is not cleared any more, the problem of time waste in the prior art can be solved.
The above examples are described in detail below by way of specific examples:
when the network topology changes, the MSTP device may receive a TC packet sent by a neighbor device, and may obtain source port information of the packet by analyzing the TC packet, where the source port information may include priority information of the source port. The MSTP device may then obtain port information connected to the source port from the current MSTP neighbor table based on the source port. When the port information connected to the source port is successfully obtained, the MSTP device may obtain the priority information of the port connected to the source port from the port information or from the per-port structure of the port connected to the source port, and compare the priority of the port connected to the source port with the priority of the source port. After obtaining the comparison result, the MSTP device may obtain, from the spanning tree port linked list, a comparison result between the priority of the port connected to the source port before the network topology change and the priority of the source port. If the current comparison result is the same as the comparison result before the network topology change, the MSTP device may traverse the port connected to the source port in the spanning tree port linked list and detect the current state of the port. When the current state of the port is the same as the state of the port in the spanning tree port linked list, determining that the state of the port is not changed; otherwise, it can be determined that the state of the port has changed.
If the current comparison result is different from the comparison result before the network topology changes, the MSTP device may recalculate the current states of all the ports, and when the current states of all the ports of the MSTP device are calculated, the MSTP device may traverse the port connected to the source port in the spanning tree port linked list and detect the current state of the port. When the current state of the port is the same as the state of the port in the spanning tree port linked list, determining that the state of the port is not changed; otherwise, it can be determined that the state of the port has changed.
When the state of the port on the MSTP device is determined to change, the port with the changed state can be recorded. The port whose state changes may be recorded in the port-to-port structure corresponding to the port, or a port state change table may be newly created and the port may be recorded in the port state change table.
After the port whose state has changed is recorded, a state change flag may be set for the port whose state has changed. The MSTP device may preset a state change flag bit, and when the state of the MSTP port changes, may set the state change flag bit corresponding to the port. Of course, the status change flag may also be a specific identification corresponding to the port that changed.
After setting the state change flag for the MSTP port whose state changes, the MSTP device may first determine whether there is an idle CPU, and when there is an idle CPU, may create a work queue on the CPU for clearing the neighbor table entry.
When the work queue is successfully created, the MSTP device may start the work queue, and set the neighbor table entry of the MSTP port, which is set with the state change flag in the MSTP port linked list, as invalid based on the work queue, thereby completing the clearing of the neighbor table entry.
It should be noted that the CPU used when the neighbor table entry is cleared for the MSTP port whose state changes may be different from the CPU used when the neighbor table entry is reestablished for the MSTP port whose neighbor table entry has been cleared.
When the network topology change is finished, the MSTP device may send a neighbor solicitation message to the MSTP port from which the neighbor table entry has been removed, and re-establish the neighbor table entry.
In the above embodiment, when the network topology changes, the MSTP device may set a state change flag for the MSTP port whose state changes, and when the neighbor table entry is cleared based on the MSTP protocol, only the neighbor table entry of the MSTP port whose state change flag is set is cleared, so that the problem of slow system convergence speed caused by clearing the neighbor table entries of all ports in the prior art can be solved.
Corresponding to the embodiment of the method for updating the MSTP neighbor table, the application also provides an embodiment of a device for updating the MSTP neighbor table.
The embodiment of the apparatus for updating the MSTP neighbor table of the present application can be applied to MSTP devices. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the device where the software implementation is located as a logical means. From a hardware level, as shown in fig. 2, a hardware structure diagram of a device where the apparatus for updating the MSTP neighbor table is located in the present application is shown, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 2, the device where the apparatus is located in the embodiment may also generally include other hardware, such as a forwarding chip responsible for processing a packet, and the like.
Referring to fig. 3, a block diagram of an embodiment of an apparatus for updating an MSTP neighbor table according to the present application is shown:
the apparatus may include: a recording unit 310, a setting unit 320, and a clearing unit 330.
A recording unit 310, configured to record an MSTP port whose state changes when a network topology changes;
a setting unit 320, configured to set a state change flag for the MSTP port whose state changes;
a clearing unit 330, configured to start an MSTP protocol, and clear the neighbor table entry of the MSTP port with the state change flag set based on the MSTP protocol.
In an optional implementation manner, the recording unit 310 may specifically be configured to:
receiving a topology change TC message sent by neighbor equipment;
and determining the MSTP port with the changed state based on the TC message.
In an alternative implementation, the clearing unit 330 may include (as shown in fig. 4):
a creating subunit 330A, configured to create a work queue for clearing the neighbor table entry;
the promoter unit 330B is configured to start the work queue, and remove, based on the work queue, a neighbor table entry of an MSTP port in the MSTP port linked list, where a state change flag is set;
and a logout subunit 330C, configured to logout the work queue after the neighbor table entry of the MSTP port with the state change flag is cleared.
In an optional implementation manner, the creating subunit 330A may specifically be configured to:
judging whether the equipment has an idle CPU or not;
when there is an idle CPU, a work queue is created on the idle CPU for clearing neighbor entries.
In an alternative implementation, the apparatus may further include (as shown in fig. 5):
an establishing unit 340, configured to reestablish the neighbor table entry for the MSTP port from which the neighbor table entry is cleared when the network topology change is finished.
In an optional implementation manner, the CPU used when the neighbor table entry is cleared for the MSTP port whose state changes is different from the CPU used when the neighbor table entry is reestablished for the MSTP port whose neighbor table entry has been cleared.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
In the above embodiment, when the network topology changes, the MSTP device may set a state change flag for the MSTP port whose state changes, and when the neighbor table entry is cleared based on the MSTP protocol, only the neighbor table entry of the MSTP port whose state change flag is set is cleared, so that the problem of slow system convergence speed caused by clearing the neighbor table entries of all ports in the prior art can be solved.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A method for updating a multiple spanning tree MSTP neighbor table, the method being applied to a MSTP device, the method comprising:
when the network topology changes, recording the MSTP port with the changed state;
setting a state change mark for the MSTP port with the changed state;
starting an MSTP protocol, and clearing the neighbor table entry of the MSTP port with the state change mark based on the MSTP protocol; wherein,
the MSTP port that records the change of state includes:
receiving a topology change TC message sent by neighbor equipment;
and determining the MSTP port with the changed state based on the TC message.
2. The method of claim 1, wherein clearing the neighbor table entry of the port with the state change flag set based on the MSTP protocol comprises:
creating a work queue for clearing neighbor table entries;
starting the work queue, and clearing the neighbor table entry of the MSTP port with the state change mark in the MSTP port linked list based on the work queue;
and after the neighbor table entry of the MSTP port with the state change mark is cleared, logging off the work queue.
3. The method of claim 2, wherein creating the work queue for clearing neighbor entries comprises:
judging whether the equipment has an idle CPU or not;
when there is an idle CPU, a work queue is created on the idle CPU for clearing neighbor entries.
4. The method of claim 2, further comprising:
and when the network topology change is finished, reestablishing the neighbor table entry aiming at the MSTP port with the cleared neighbor table entry.
5. The method of claim 4, wherein the CPU used when performing neighbor table entry purging for the MSTP port with changed state is different from the CPU used when re-establishing neighbor table entries for the MSTP port with purged neighbor table entries.
6. An apparatus for updating a Multiple Spanning Tree (MSTP) neighbor table, the apparatus being adapted for use on a MSTP device, the apparatus comprising:
the recording unit is used for recording the MSTP port with the changed state when the network topology is changed;
the setting unit is used for setting a state change mark for the MSTP port with the changed state;
a clearing unit, configured to start an MSTP protocol, and clear, based on the MSTP protocol, a neighbor table entry of an MSTP port to which a state change flag is set; wherein,
the recording unit is specifically configured to:
receiving a topology change TC message sent by neighbor equipment;
and determining the MSTP port with the changed state based on the TC message.
7. The apparatus of claim 6, wherein the clearing unit comprises:
the creating subunit is used for creating a work queue for clearing the neighbor table entry;
the starting unit is used for starting the work queue and eliminating the neighbor table entry of the MSTP port which is provided with the state change mark in the MSTP port linked list based on the work queue;
and the logout subunit is used for logging out the work queue after the neighbor table entry of the MSTP port with the state change mark is cleared.
8. The apparatus according to claim 7, wherein the creating subunit is specifically configured to:
judging whether the equipment has an idle CPU or not;
when there is an idle CPU, a work queue is created on the idle CPU for clearing neighbor entries.
9. The apparatus of claim 7, further comprising:
and the establishing unit is used for reestablishing the neighbor table entry aiming at the MSTP port with the removed neighbor table entry when the network topology change is finished.
10. The apparatus of claim 9, wherein the CPU used to perform neighbor table entry purging for MSTP ports with changed states is different from the CPU used to re-establish neighbor table entries for MSTP ports with purged neighbor table entries.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610053801.3A CN105939270B (en) | 2016-01-26 | 2016-01-26 | Update the method and device of MSTP neighbor table |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610053801.3A CN105939270B (en) | 2016-01-26 | 2016-01-26 | Update the method and device of MSTP neighbor table |
Publications (2)
Publication Number | Publication Date |
---|---|
CN105939270A CN105939270A (en) | 2016-09-14 |
CN105939270B true CN105939270B (en) | 2019-09-17 |
Family
ID=57152966
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201610053801.3A Active CN105939270B (en) | 2016-01-26 | 2016-01-26 | Update the method and device of MSTP neighbor table |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN105939270B (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106506370A (en) * | 2016-11-09 | 2017-03-15 | 杭州迪普科技股份有限公司 | List item sweep-out method and device |
CN106656818B (en) * | 2016-11-18 | 2019-11-08 | 杭州迪普科技股份有限公司 | A kind of method and apparatus for removing fast-forwarding list item |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1859290A (en) * | 2005-10-28 | 2006-11-08 | 华为技术有限公司 | Processing method for network node configuration information when network topology changing |
CN101060485A (en) * | 2007-05-11 | 2007-10-24 | 杭州华三通信技术有限公司 | Topology changed messages processing method and processing device |
CN101753458A (en) * | 2009-12-30 | 2010-06-23 | 杭州华三通信技术有限公司 | Method and device for processing ND neighbor table entry |
CN103532741A (en) * | 2013-09-27 | 2014-01-22 | 瑞斯康达科技发展股份有限公司 | Access level network topology management method and system |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7673021B2 (en) * | 2004-02-12 | 2010-03-02 | Cisco Technology, Inc. | Automated provisioning of phones in packet voice networks |
-
2016
- 2016-01-26 CN CN201610053801.3A patent/CN105939270B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1859290A (en) * | 2005-10-28 | 2006-11-08 | 华为技术有限公司 | Processing method for network node configuration information when network topology changing |
CN101060485A (en) * | 2007-05-11 | 2007-10-24 | 杭州华三通信技术有限公司 | Topology changed messages processing method and processing device |
CN101753458A (en) * | 2009-12-30 | 2010-06-23 | 杭州华三通信技术有限公司 | Method and device for processing ND neighbor table entry |
CN103532741A (en) * | 2013-09-27 | 2014-01-22 | 瑞斯康达科技发展股份有限公司 | Access level network topology management method and system |
Also Published As
Publication number | Publication date |
---|---|
CN105939270A (en) | 2016-09-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2912803B1 (en) | Forwarding table optimization with flow data | |
US9667537B2 (en) | Transport system, packet transport apparatus, and packet transport method | |
US9736057B2 (en) | Forwarding packet fragments using L4-L7 headers without reassembly in a software-defined networking (SDN) system | |
CN102598599B (en) | RSVP-TE graceful restart under fast re-route conditions | |
US8249065B2 (en) | Destination MAC aging of entries in a Layer 2 (L2) forwarding table | |
CN102387065B (en) | Use the method and apparatus keeping link state data based on the Routing Protocol flooded | |
CN104283738B (en) | A kind of chain circuit detecting method and equipment | |
ATE335332T1 (en) | METHOD AND DEVICE FOR IMPROVING THE AVAILABILITY OF ROUTING SYSTEMS WITH MULTI-PATH EQUAL COSTS | |
CN104869057B (en) | Open flow switch Graceful Restart processing method, device and open flow controller | |
RU2612599C1 (en) | Control device, communication system, method for controlling switches and program | |
CN105721321B (en) | A kind of the outgoing interface update method and device of equal cost multipath | |
CN106656857B (en) | Message speed limiting method and device | |
CN110891018B (en) | Network traffic recovery method and device, SDN controller and storage medium | |
WO2013149520A1 (en) | Transmission path switching | |
CN108737217B (en) | Packet capturing method and device | |
JP5900652B2 (en) | Switch device, VLAN setting management method, and program | |
US20190334808A1 (en) | Data plane forwarding table downed link updating | |
US9699073B2 (en) | System and method for reducing traffic loss while using loop free alternate routes for multicast only fast reroute (MoFRR) | |
CN105939270B (en) | Update the method and device of MSTP neighbor table | |
EP2122925A1 (en) | Method, bridge and computer network for calculating a spanning tree based on link state advertisements (lsa) | |
CN102136960A (en) | Method and device for controlling switch ports | |
CN101252523B (en) | Message redirecting method, method and device for reverting redirecting message feature information | |
WO2012142888A1 (en) | Tunnel group protection method and device based on multi-protocol label switching network | |
US6973026B1 (en) | Resilient chassis-based network switching | |
CN105939254B (en) | The method and device of VRRP backup group state switching |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
CB02 | Change of applicant information | ||
CB02 | Change of applicant information |
Address after: Binjiang District and Hangzhou city in Zhejiang Province Road 310051 No. 68 in the 6 storey building Applicant after: Hangzhou Dipu Polytron Technologies Inc Address before: Binjiang District and Hangzhou city in Zhejiang Province Road 310051 No. 68 in the 6 storey building Applicant before: Hangzhou Dipu Technology Co., Ltd. |
|
GR01 | Patent grant | ||
GR01 | Patent grant |