CN108337161B - Method for smoothly switching three-layer data flow of MLAG interface fault - Google Patents

Abstract

The invention provides a method for three-layer data flow smooth switching of MLAG interface failure, which is characterized in that a backup FIB table item with a peer-link interface as an output interface is dynamically generated based on an FIB table item with an MLAG interface as the output interface of Switch equipment, when the MLAG interface has communication failure, a data message forwarded by an MLAG interface route can be quickly switched to the output interface for the peer-link interface to forward the data message, the FIB table item is quickly updated, and the forwarding of the data message is ensured not to be influenced. The invention reduces the packet loss rate of the Switch equipment to which the failure MLAG member port belongs in a backup routing mode; the communication capability between the Network side and the CE side is ensured in a backup routing mode; and route shock caused by a shutdownfault of an MLAG (Multi-level Access gateway) upper-connection port is avoided by a backup route mode.

Description

Method for smoothly switching three-layer data flow of MLAG interface fault

Technical Field

The invention relates to the technical field of cross-device link aggregation of network switches in the field of data communication, in particular to a method for switching backup routes by an MLAG system when an MLAG interface is used as a three-layer interface and communication faults occur.

Background

Mlag (multiple links Aggregation group), which is a mechanism for implementing cross-device Link Aggregation, can implement Link Aggregation among multiple devices, and the Aggregation devices form a dual active system, thereby improving the reliability of links.

In the attached fig. 1, the MLAG system is composed of three layers of switch devices, and the three devices are respectively: SwitchA, SwitchB, and CE. The SwitchA and SwitchB are two access devices, and the CE device is an accessed device. The basic idea of the MLAG technique is to let two access switches, namely, switch a and switch b, perform link aggregation negotiation with an accessed CE device in the same state, and the accessed CE device looks as if a link aggregation relationship is established with one device. In order to ensure that the two access devices, switch a and switch b, present the CE device in the same state, the two access devices need a peer-link for inter-device data and state synchronization. After cross-device link aggregation between the CE device and the SwitchA and SwitchB devices is successful, the CE device has the capacity of dual-homing access to the Ethernet, so that the reliability of data forwarding of the CE device is improved. A Keepalive link is arranged between the two devices of the switch A and the switch B and is mainly used for detecting the working condition of the whole device.

The application scenario of fig. 2 is CE dual-homing switch a and switch b devices. The communication between the SwitchA equipment and the SwitchB equipment and the Network and the CE equipment respectively adopts three-layer IP routing communication. The flow of forwarding the data packet through the MLAG system is identified in the figure. Two access switches in the MLAG system present the state to the outside consistently, when the Network communicates with CE apparatus, can adopt any route to transmit, in order to guarantee the correctness of data transmission, two access apparatuses will have the same routing table entry, any Ethernet interface receives IP data message, can all pass IP route to CE apparatus, finish the correct message transmission.

In fig. 3, when MLAG interfaces of the switch b devices of the two access devices of the MLAG system fail, data packets whose interfaces are routed through the switch b devices and are MLAG interfaces will be discarded, and at this time, if the network side continues to send IP data packets to the switch b devices, a serious communication problem will occur. At present, in order to ensure that a data packet at a Network side is not forwarded to a switch b device any more, the most direct, effective and simple method is to connect the switch b device to a port at the Network side for shutdown, so that the Network side senses that the switch b cannot perform normal routing forwarding work, and all data packets are forwarded through the switch a device, thereby ensuring normal communication between the Network word side and a CE side.

In the prior art, the uplink port shutdown of the switch b device is directly used, so that the Network side can timely sense that the switch b fails, and the Network side route switching is triggered, thereby ensuring normal communication. However, the technical scheme has the following problems:

the IP data message which is already routed and forwarded to the SwitchB equipment is lost, so that the risk of network communication delay is increased;

because the SwitchA and SwitchB devices are in a load balancing mode when working normally, the uplink interface of the shutdown SwitchB device will affect the communication bandwidth of the Network side and the CE side, and the data communication capability is reduced;

the Shutdown of the uplink port of the SwitchB device causes route calculation on the Network side, thereby causing route topology oscillation.

Disclosure of Invention

In order to solve the above technical problems, an object of the present invention is to provide a method for smoothly switching three-layer data traffic due to MLAG interface failure, which solves the communication problems of the CE side and the Network side when the MLAG interface communication fails and recovers in an MLAG system. A backup routing mechanism is provided based on an MLAG interface, so that when the communication of the MLAG interface fails and recovers, data messages forwarded through the MLAG interface of the Switch equipment can be forwarded normally, and the problem of data packet loss caused by the communication failure of the MLAG interface is solved to the maximum extent.

The invention is realized according to the following technical scheme:

a method for three-layer data flow smooth switching of MLAG interface failure is characterized in that a backup FIB table item with a peer-link interface as an output interface is dynamically generated based on an FIB table item with an MLAG interface as the output interface of Switch equipment, when the MLAG interface has a communication failure, a data message forwarded by an MLAG interface route can be quickly switched to the output interface for the peer-link interface to forward the data message, the FIB table item is quickly updated, data message forwarding is not affected, and a NetWork side does not sense the communication failure of the MLAG interface of Switch, so that the stability of the whole system is improved, and the method is characterized by comprising the following steps:

step 1: the method comprises the following steps that a MLAG interface, a Peer-link interface and an uplink interface connected with a NetWork word side of Switch equipment are configured into three-layer interfaces, and data between the CE side and the NetWork word side adopt a routing three-layer forwarding mode;

step 2: the Switch equipment generates an FIB table item with an output interface as an MLAG interface, generates a backup FIB table item with an output interface as a peer-link interface based on the FIB table item, and does not need to update the backup FIB table item to a hardware forwarding table;

and step 3: when communication of an MLAG interface of Switch equipment fails, an FIB table item of an outgoing interface which is the MLAG interface is deleted from a hardware table, and then a backup FIB table item is updated to the hardware forwarding table;

and 4, step 4: recovering communication of an MLAG interface of Switch equipment, updating an FIB table item of an outgoing interface which is the MLAG interface to a hardware table, and then deleting a backup FIB table item from the hardware forwarding table;

and 5: the Switch equipment deletes an FIB table item with an output interface as an MLAG interface, and deletes software and hardware table items corresponding to the FIB table item with the output interface as the MLAG interface and a backup FIB table item with an output interface as a peer-link interface.

In the above technical solution, the method for generating the FIB entry of the Switch device includes:

step 201: an FIB table management module of Switch equipment registers an FIB table item adding event;

step 202: when an FIB table addition event is received, analyzing the received FIB table addition event message, acquiring the type of an outgoing interface forwarded in an FIB forwarding table, checking whether the type of the forwarding outgoing interface is an MLAG interface of Switch equipment, copying the received FIB table to generate a same FIB table if the type of the forwarding outgoing interface is the MLAG interface, updating the copied FIB forwarding outgoing interface to a peer-link interface of the Switch equipment, and marking the copied FIB table as a backup FIB table;

step 203: writing FIB table items of which non-backup forwarding output interfaces are MLAGs into a switching chip through corresponding interfaces, and enabling corresponding data messages to complete normal routing data forwarding through the switching chip of the Switch equipment; and the backup FIB table item is only stored as software backup data and is not written into the exchange chip, and the backup FIB table item with a peer-link output interface is written into the exchange chip when the MLAG interface fails so as to participate in the routing data forwarding of the data message.

In the above technical solution, step 3 comprises the following steps:

step 301: an FIB management module of Switch equipment registers an MLAG interface communication fault event;

step 302: when receiving an MLAG interface communication failure event, analyzing MLAG interface data carried in the MLAG interface communication failure event, and checking the validity of an MLAG interface, if the MLAG interface is valid, checking whether an MLAG communication recovery timer exists, if the MLAG interface communication recovery timer exists, stopping the timer; the MLAG interface communication recovery timer avoids the problem of route oscillation of the Switch equipment, if the communication fault and communication recovery of the MLAG interface need to update the route every time, the communication fault and communication recovery continuously occur in the MLAG interface in a short time, which causes the route oscillation of the Switch equipment.

Step 303: and searching a corresponding FIB table item according to the faulted MLAG interface, then checking whether the state of the FIB table item is active, if the active of the FIB table item is active, calling a driving interface to delete the routing forwarding table item from the exchange chip, and simultaneously setting the state of the FIB table item to be inactive.

Step 304: according to the FIB table, a backup FIB table item of which the forwarding output interface is a peer-link is found, and then the backup FIB table item is written into a switching chip, so that the data message passing through the Switch equipment is ensured, and the corresponding effective output interface can be found.

In the above technical solution, step 4 includes the following steps:

step 401: an FIB table management module of Switch equipment registers an MLAG interface communication recovery event;

step 402: when receiving an MLAG interface communication recovery event, analyzing MLAG interface data carried in the MLAG interface communication recovery event, and checking the validity of an MLAG interface; and if the MLAG interface is effective, traversing all FIB table entries with the routing output interfaces being the MLAG interfaces, setting the state of the corresponding FIB table entry to active, and starting an MLAG interface communication recovery timer.

Step 403: when the MLAG interface communication recovery timer is overtime, traversing all FIB table items of which the route output interfaces are MLAG interfaces, writing the FIB table items in an active state into a switching chip, wherein at the moment, two forwarding paths exist for a data message between a Network side and a CE side through Switch equipment, one route forwarding output interface is a peer-link interface, the other route output interface is an MLAG interface, and the two forwarding paths both forward the data message with normal parameters;

step 404: deleting the backup route with the output interface being a peer-link interface from the exchange chip, wherein only an FIB table item with the output interface being an MLAG interface exists in the exchange chip; and adding an FIB table item with an output interface of an MLAG interface, and deleting a routing table item with an output interface of a peer-link interface, so that smooth switching of data message forwarding by an exchange chip is ensured, and data flow between a Network side and a CE side is lossless.

In the above technical solution, step 5 comprises the following steps:

step 501: an FIB table management module of Switch equipment registers an FIB table item deletion event;

step 502: when an FIB table item deleting event is received, analyzing the received FIB table item deleting event message, acquiring the type of an outgoing interface forwarded in an FIB forwarding table item, checking whether the type of the forwarding outgoing interface is an MLAG interface of Switch equipment, traversing and searching FIB table items of all outgoing interface MLAG interfaces if the type of the forwarding outgoing interface is the MLAG interface, deleting the FIB table items from a switching chip if the FIB table items are written into the switching chip, and deleting corresponding software FIB table items;

step 503: and according to the traversal of the MLAG interface, backup FIB table entries of all the outgoing interfaces peer-link are searched, if the FIB backup table entries are written into the slave exchange chip, the table entries are deleted from the exchange chip, and meanwhile, the corresponding software FIB table entries are deleted.

Compared with the prior art, the invention has the following beneficial effects:

1) the invention reduces the packet loss rate of the Switch equipment to which the failure MLAG member port belongs in a backup routing mode;

2) the invention ensures the communication capacity between the Network side and the CE side in a backup routing mode;

3) the invention avoids route oscillation caused by a shutdownfault of the MLAG uplink port in a backup route mode.

Drawings

Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments with reference to the following drawings:

FIG. 1 is a schematic diagram of a prior art MLAG;

FIG. 2 is a schematic diagram of an IP packet forwarding network on the MLAG CE side and the network side in the prior art;

FIG. 3 is a schematic diagram of an IP packet forwarding network on a CE side and a network side with a faulty MLAG member port in the prior art;

FIG. 4 is a flow chart of the FIB table generation of the Switch device according to the present invention;

FIG. 5 is a flow chart of the communication failure processing of the MLAG interface of the Switch device according to the present invention;

fig. 6 is a flowchart of a Switch device MLAG interface communication recovery process according to the present invention;

fig. 7 is a flowchart of FIB table deletion in the Switch device according to the present invention.

Detailed Description

The present invention will be described in detail with reference to specific examples. The following examples will assist those skilled in the art in further understanding the invention, but are not intended to limit the invention in any way. It should be noted that it would be obvious to those skilled in the art that various changes and modifications can be made without departing from the spirit of the invention. All falling within the scope of the present invention.

The invention relates to a method for smoothly switching three-layer data flow of MLAG interface failure, which is characterized in that an outlet interface of Switch equipment is an FIB table of an MLAG interface, a backup FIB table with a peer-link interface as an outlet interface is dynamically generated, when the MLAG interface has communication failure, a data message forwarded by an MLAG interface route can be quickly switched to the outlet interface for the peer-link interface to forward the data message, the FIB table is quickly updated, the forwarding of the data message is not influenced, and the NetWork side does not sense the communication failure of the MLAG interface of Switch, so that the stability of the whole system is improved, and the method is characterized by comprising the following steps:

step 1: the method comprises the following steps that a MLAG interface, a Peer-link interface and an uplink interface connected with a NetWork word side of Switch equipment are configured into three-layer interfaces, and data between the CE side and the NetWork word side adopt a routing three-layer forwarding mode;

step 2: the Switch equipment generates an FIB table item with an output interface as an MLAG interface, generates a backup FIB table item with an output interface as a peer-link interface based on the FIB table item, and does not need to update the backup FIB table item to a hardware forwarding table;

and step 3: when communication of an MLAG interface of Switch equipment fails, an FIB table item of an outgoing interface which is the MLAG interface is deleted from a hardware table, and then a backup FIB table item is updated to the hardware forwarding table;

and 4, step 4: recovering communication of an MLAG interface of Switch equipment, updating an FIB table item of an outgoing interface which is the MLAG interface to a hardware table, and then deleting a backup FIB table item from the hardware forwarding table;

and 5: the Switch equipment deletes an FIB table item with an output interface as an MLAG interface, and deletes software and hardware table items corresponding to the FIB table item with the output interface as the MLAG interface and a backup FIB table item with an output interface as a peer-link interface.

FIG. 4 is a flow chart of the FIB table generation of the Switch device according to the present invention; as shown in fig. 4, the method for generating the FIB entry of the Switch device includes:

step 201: an FIB table management module of Switch equipment registers an FIB table item adding event;

step 202: when an FIB table addition event is received, analyzing the received FIB table addition event message, acquiring the type of an outgoing interface forwarded in an FIB forwarding table, checking whether the type of the forwarding outgoing interface is an MLAG interface of Switch equipment, copying the received FIB table to generate a same FIB table if the type of the forwarding outgoing interface is the MLAG interface, updating the copied FIB forwarding outgoing interface to a peer-link interface of the Switch equipment, and marking the copied FIB table as a backup FIB table;

step 203: writing FIB table items of which non-backup forwarding output interfaces are MLAGs into a switching chip through corresponding interfaces, and enabling corresponding data messages to complete normal routing data forwarding through the switching chip of the Switch equipment; and the backup FIB table item is only stored as software backup data and is not written into the exchange chip, and the backup FIB table item with a peer-link output interface is written into the exchange chip when the MLAG interface fails so as to participate in the routing data forwarding of the data message.

FIG. 5 is a flow chart of the communication failure processing of the MLAG interface of the Switch device according to the present invention; as shown in fig. 5, step 3 comprises the following steps:

step 301: an FIB management module of Switch equipment registers an MLAG interface communication fault event;

step 302: when receiving an MLAG interface communication failure event, analyzing MLAG interface data carried in the MLAG interface communication failure event, and checking the validity of an MLAG interface, if the MLAG interface is valid, checking whether an MLAG communication recovery timer exists, if the MLAG interface communication recovery timer exists, stopping the timer; the MLAG interface communication recovery timer avoids the problem of route oscillation of the Switch equipment, if the communication fault and communication recovery of the MLAG interface need to update the route every time, the communication fault and communication recovery continuously occur in the MLAG interface in a short time, which causes the route oscillation of the Switch equipment. In order to solve the problem of routing oscillation, an MLAG interface communication recovery timer is introduced into an FIB table management module, and when the MLAG interface recovers stable communication, the routing table is allowed to be updated.

Step 303: and searching a corresponding FIB table item according to the faulted MLAG interface, then checking whether the state of the FIB table item is active, if the active of the FIB table item is active, calling a driving interface to delete the routing forwarding table item from the exchange chip, and simultaneously setting the state of the FIB table item to be inactive.

Step 304: according to the FIB table, a backup FIB table item of which the forwarding output interface is a peer-link is found, and then the backup FIB table item is written into a switching chip, so that the data message passing through the Switch equipment is ensured, and the corresponding effective output interface can be found. The problem of data message loss caused by the absence of the route or the invalid route interface is avoided as much as possible.

Fig. 6 is a flowchart of a Switch device MLAG interface communication recovery process according to the present invention; as shown in fig. 6, step 4 includes the following steps:

step 401: an FIB table management module of Switch equipment registers an MLAG interface communication recovery event;

step 402: when receiving an MLAG interface communication recovery event, analyzing MLAG interface data carried in the MLAG interface communication recovery event, and checking the validity of an MLAG interface; and if the MLAG interface is effective, traversing all FIB table entries with the routing output interfaces being the MLAG interfaces, setting the state of the corresponding FIB table entry to active, and starting an MLAG interface communication recovery timer.

Step 403: when the MLAG interface communication recovery timer is overtime, traversing all FIB table items of which the route output interfaces are MLAG interfaces, writing the FIB table items in an active state into a switching chip, wherein at the moment, two forwarding paths exist for a data message between a Network side and a CE side through Switch equipment, one route forwarding output interface is a peer-link interface, the other route output interface is an MLAG interface, and the two forwarding paths both forward the data message with normal parameters;

step 404: deleting the backup route with the output interface being a peer-link interface from the exchange chip, wherein only an FIB table item with the output interface being an MLAG interface exists in the exchange chip; and adding an FIB table item with an output interface of an MLAG interface, and deleting a routing table item with an output interface of a peer-link interface, so that smooth switching of data message forwarding by an exchange chip is ensured, and data flow between a Network side and a CE side is lossless.

Fig. 7 is a flowchart of FIB table deletion in Switch device according to the present invention, as shown in fig. 7, step 5 includes the following steps:

step 501: an FIB table management module of Switch equipment registers an FIB table item deletion event;

step 502: when an FIB table item deleting event is received, analyzing the received FIB table item deleting event message, acquiring the type of an outgoing interface forwarded in an FIB forwarding table item, checking whether the type of the forwarding outgoing interface is an MLAG interface of Switch equipment, traversing and searching FIB table items of all outgoing interface MLAG interfaces if the type of the forwarding outgoing interface is the MLAG interface, deleting the FIB table items from a switching chip if the FIB table items are written into the switching chip, and deleting corresponding software FIB table items;

step 503: and according to the traversal of the MLAG interface, backup FIB table entries of all the outgoing interfaces peer-link are searched, if the FIB backup table entries are written into the slave exchange chip, the table entries are deleted from the exchange chip, and meanwhile, the corresponding software FIB table entries are deleted.

The foregoing description of specific embodiments of the present invention has been presented. It is to be understood that the present invention is not limited to the specific embodiments described above, and that various changes or modifications may be made by one skilled in the art within the scope of the appended claims without departing from the spirit of the invention. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.

Claims (4)

1. A method for three-layer data flow smooth switching of MLAG interface failure is characterized in that a backup FIB table item with a peer-link interface as an output interface is dynamically generated based on an FIB table item with an MLAG interface as the output interface of Switch equipment, when the MLAG interface has a communication failure, a data message forwarded by an MLAG interface route can be quickly switched to the output interface for the peer-link interface to forward the data message, the FIB table item is quickly updated, data message forwarding is not affected, and a NetWork side does not sense the communication failure of the MLAG interface of Switch, so that the stability of the whole system is improved, and the method is characterized by comprising the following steps:

step 1: the method comprises the following steps that a MLAG interface, a Peer-link interface and an uplink interface connected with a NetWork word side of Switch equipment are configured into three-layer interfaces, and data between the CE side and the NetWork word side adopt a routing three-layer forwarding mode;

step 2: the Switch equipment generates an FIB table item with an output interface as an MLAG interface, generates a backup FIB table item with an output interface as a peer-link interface based on the FIB table item, and does not need to update the backup FIB table item to a hardware forwarding table;

and step 3: when communication of an MLAG interface of Switch equipment fails, an FIB table item of an outgoing interface which is the MLAG interface is deleted from a hardware table, and then a backup FIB table item is updated to the hardware forwarding table;

and 4, step 4: recovering communication of an MLAG interface of Switch equipment, updating an FIB table item of an outgoing interface which is the MLAG interface to a hardware table, and then deleting a backup FIB table item from the hardware forwarding table;

and 5: the Switch equipment deletes an FIB table item with an output interface as an MLAG interface, and deletes software and hardware table items corresponding to the FIB table item with the output interface as the MLAG interface and a backup FIB table item with an output interface as a peer-link interface;

the method for generating the FIB table of the Switch equipment comprises the following steps:

step 201: an FIB table management module of Switch equipment registers an FIB table item adding event;

step 202: when an FIB table addition event is received, analyzing the received FIB table addition event message, acquiring the type of an outgoing interface forwarded in an FIB forwarding table, checking whether the type of the forwarding outgoing interface is an MLAG interface of Switch equipment, copying the received FIB table to generate a same FIB table if the type of the forwarding outgoing interface is the MLAG interface, updating the copied FIB forwarding outgoing interface to a peer-link interface of the Switch equipment, and marking the copied FIB table as a backup FIB table;

step 203: writing FIB table items of which non-backup forwarding output interfaces are MLAGs into a switching chip through corresponding interfaces, and enabling corresponding data messages to complete normal routing data forwarding through the switching chip of the Switch equipment; and the backup FIB table item is only stored as software backup data and is not written into the exchange chip, and the backup FIB table item with a peer-link output interface is written into the exchange chip when the MLAG interface fails so as to participate in the routing data forwarding of the data message.

2. The method of MLAG interface failure three-layer data traffic smooth switching according to claim 1, wherein step 3 comprises the steps of:

step 301: an FIB management module of Switch equipment registers an MLAG interface communication fault event;

step 302: when receiving an MLAG interface communication failure event, analyzing MLAG interface data carried in the MLAG interface communication failure event, and checking the validity of an MLAG interface, if the MLAG interface is valid, checking whether an MLAG communication recovery timer exists, if the MLAG interface communication recovery timer exists, stopping the timer; the MLAG interface communication recovery timer avoids the problem of route oscillation of the Switch equipment, if the communication fault and communication recovery of the MLAG interface need to update the route every time, the communication fault and communication recovery continuously occur in the MLAG interface in a short time, so that the Switch equipment generates the route oscillation;

step 303: searching a corresponding FIB table item according to the MLAG interface with the fault, then checking whether the state of the FIB table item is active, if the active of the FIB table item is found, calling a driving interface to delete the routing forwarding table item from the exchange chip, and simultaneously setting the state of the FIB table item as inactive;

step 304: according to the FIB table, a backup FIB table item of which the forwarding output interface is a peer-link is found, and then the backup FIB table item is written into a switching chip, so that the data message passing through the Switch equipment is ensured, and the corresponding effective output interface can be found.

3. The method of MLAG interface failure three-layer data traffic smooth switching according to claim 1, wherein step 4 comprises the steps of:

step 401: an FIB table management module of Switch equipment registers an MLAG interface communication recovery event;

step 402: when receiving an MLAG interface communication recovery event, analyzing MLAG interface data carried in the MLAG interface communication recovery event, and checking the validity of an MLAG interface; if the MLAG interface is effective, traversing all FIB table entries of which the route output interfaces are MLAG interfaces, setting the state of the corresponding FIB table entry as active, and starting an MLAG interface communication recovery timer;

step 403: when the MLAG interface communication recovery timer is overtime, traversing all FIB table items of which the route output interfaces are MLAG interfaces, writing the FIB table items in an active state into a switching chip, wherein at the moment, two forwarding paths exist for a data message between a Network side and a CE side through Switch equipment, one route forwarding output interface is a peer-link interface, the other route output interface is an MLAG interface, and the two forwarding paths both forward the data message with normal parameters;

step 404: deleting the backup route with the output interface being a peer-link interface from the exchange chip, wherein only an FIB table item with the output interface being an MLAG interface exists in the exchange chip; and adding an FIB table item with an output interface of an MLAG interface, and deleting a routing table item with an output interface of a peer-link interface, so that smooth switching of data message forwarding by an exchange chip is ensured, and data flow between a Network side and a CE side is lossless.

4. The method of claim 1, wherein step 5 comprises the steps of:

step 501: an FIB table management module of Switch equipment registers an FIB table item deletion event;

step 502: when an FIB table item deleting event is received, analyzing the received FIB table item deleting event message, acquiring the type of an outgoing interface forwarded in an FIB forwarding table item, checking whether the type of the forwarding outgoing interface is an MLAG interface of Switch equipment, traversing and searching FIB table items of all outgoing interface MLAG interfaces if the type of the forwarding outgoing interface is the MLAG interface, deleting the FIB table items from a switching chip if the FIB table items are written into the switching chip, and deleting corresponding software FIB table items;

step 503: and according to the traversal of the MLAG interface, backup FIB table entries of all the outgoing interfaces peer-link are searched, if the FIB backup table entries are written into the slave exchange chip, the table entries are deleted from the exchange chip, and meanwhile, the corresponding software FIB table entries are deleted.

Images