CN114553761A - Exception handling method, exception handling device, network equipment and storage medium - Google Patents

Exception handling method, exception handling device, network equipment and storage medium Download PDF

Info

Publication number
CN114553761A
CN114553761A CN202210042868.2A CN202210042868A CN114553761A CN 114553761 A CN114553761 A CN 114553761A CN 202210042868 A CN202210042868 A CN 202210042868A CN 114553761 A CN114553761 A CN 114553761A
Authority
CN
China
Prior art keywords
arp
entry
network device
table entry
network equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202210042868.2A
Other languages
Chinese (zh)
Other versions
CN114553761B (en
Inventor
王阳
廖以顺
王逸
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd Hefei Branch
Original Assignee
New H3C Technologies Co Ltd Hefei Branch
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd Hefei Branch filed Critical New H3C Technologies Co Ltd Hefei Branch
Priority to CN202210042868.2A priority Critical patent/CN114553761B/en
Publication of CN114553761A publication Critical patent/CN114553761A/en
Application granted granted Critical
Publication of CN114553761B publication Critical patent/CN114553761B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • 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/28—Routing or path finding of packets in data switching networks using route fault recovery
    • 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
    • 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/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application provides an exception handling method, an exception handling device, network equipment and a storage medium. The method is applied to any first network equipment in the S-Trunk group and comprises the following steps: when receiving an ARP request message which originates from user equipment and needs to be sent to second network equipment having a neighbor relation with the first network equipment, judging whether a communication channel between the first network equipment and another first network equipment in the S-Trunk group is abnormal or not; if the judgment result is yes, further judging whether a first ARP table entry of an interface, which comprises the ARP request message received by the first network equipment, is set as an entry not needing to be aged, and if the judgment result is no, setting the first ARP table entry as an entry not needing to be aged; generating a second ARP table entry and a host route of the user equipment based on the ARP request message; and sending the ARP request message and the host route to second network equipment. The application can improve user experience.

Description

Exception handling method, exception handling device, network equipment and storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to an exception handling method and apparatus, a network device, and a storage medium.
Background
Smart link aggregation (S-Trunk) is a mechanism for cross-device link aggregation, and can perform cross-device link aggregation on two network devices, thereby improving the reliability of a link.
As shown in fig. 1, a S-Trunk group is created between a network device 1 and a network device 2, and Internet Protocol (IP) addresses of member ports in the S-Trunk group are in the same network segment; the switching device is deployed with ethernet link aggregation, interfaces of the switching device connected to the network device 1 and the network device 2 are in the same aggregation group, and all member ports in the aggregation group are in an UP state, so as to ensure that the switching device operates in a load sharing mode.
In the networking shown in fig. 1, both the network device 1 and the network device 2 may issue a network segment route corresponding to an IP address of a member port in the S-Trunk group to a corresponding neighboring device (e.g., the network device 3 shown in fig. 1), so that the neighboring device learns the network segment route and forms an equivalent route. Here, the network device 1, the network device 2, and the network device 3 may all be routing devices or the like.
When the user equipment 1 in fig. 1 needs to access the network device 3, for example, the IP Address of the network device 3 is 10.1.1.1, an Address Resolution (ARP) request message 1 with a destination IP Address of 10.1.1.1 is sent to the switching device.
After receiving the ARP request message 1, the switching device determines an egress interface of the ARP request message 1 based on a preset hash algorithm. Here, the outgoing interface determined by the switching device may be an interface of the switching device connected to the network device 1, or may be an interface of the switching device connected to the network device 2.
If the determined outgoing interface is an interface of the switch device connected to the network device 1, the switch device forwards the ARP request message 1 through the determined interface.
Subsequently, the network device 1 receives the ARP request message 1, generates an ARP entry for the user equipment based on the ARP request message 1, where the entry type of the ARP entry is a dynamic entry, synchronizes the generated ARP entry to the network device 2, and sends the ARP request message 1 to the next hop device (i.e., the network device 3) determined by the network device 1
Next, after generating the ARP response packet for the ARP request packet 1, the network device 3 determines the next hop device based on a preset equivalent routing algorithm. Here, the next hop device determined by the network device 3 may be the network device 1 or the network device 2.
Assuming that the determined next hop device is the network device 2, the network device 3 sends the ARP response packet to the network device 2, the network device 2 finally transmits the ARP response packet to the user device 1 based on the corresponding ARP entry and the corresponding routing table, and the user device 1 continues to send the corresponding access request packet.
In the whole processing process of the ARP request message, for any network device in the S-Trunk group, once the ARP request message 1 is received and not successfully synchronized to another network device, a situation may occur that an ARP response message is sent to another network device, in which case, another network device sends an ARP request message whose destination IP address is the IP address (e.g., 10.1.1.2) of the user device to the switching device, and subsequently, a situation may also occur that another network device cannot receive an ARP response message from the user device, because the ARP response message is sent to the network device by the switching device, the user device 1 cannot perform related service access, and user experience is seriously affected.
Disclosure of Invention
In order to overcome the problems in the related art, the application provides an exception handling method, an exception handling device, network equipment and a storage medium.
According to a first aspect of the embodiments of the present application, there is provided an exception handling method, which is applied to any first network device in an S-Trunk group, and the method includes:
when receiving an ARP request message which originates from user equipment and needs to be sent to second network equipment having a neighbor relation with the first network equipment, judging whether a communication channel between the first network equipment and another first network equipment in the S-Trunk group is abnormal or not;
if the judgment result is yes, further judging whether a first ARP table entry of an interface of the first network equipment receiving the ARP request message is set as an entry which does not need to be aged or not, and if the judgment result is no, setting the first ARP table entry as an entry which does not need to be aged;
generating a second ARP table entry and a host route of the user equipment based on the ARP request message, wherein the table entry type of the second ARP table entry is a specified table entry type, and the specified table entry type is neither a static table entry nor a dynamic table entry;
and sending the ARP request message and the host route to the second network equipment, so that the second network equipment sends an ARP response message aiming at the ARP request message to the first network equipment based on the host route after generating the ARP response message.
According to a second aspect of the embodiments of the present application, there is provided an exception handling apparatus, which is applied to any first network device in an S-Trunk group, and includes:
a first determining module, configured to determine whether a communication channel between a first network device and another first network device in the S-Trunk group is abnormal when receiving an ARP request packet that originates from a user equipment and needs to be sent to a second network device that has a neighbor relationship with the first network device;
a second judging module, configured to further judge whether a first ARP entry of an interface, which includes the interface where the first network device receives the ARP request packet, is set as an entry that does not need to be aged, if a judgment result of the first judging module is yes;
the setting module is used for setting the first ARP table entry as a table entry which does not need to be aged when the judgment result of the second judgment module is negative;
a generating module, configured to generate a second ARP entry and a host route of the user equipment based on the ARP request packet, where an entry type of the second ARP entry is a specified entry type, and the specified entry type is neither a static entry nor a dynamic entry;
and the sending module is used for sending the ARP request message and the host route to the second network equipment so that the second network equipment sends an ARP response message aiming at the ARP request message to the first network equipment based on the host route after generating the ARP response message.
According to a third aspect of embodiments herein, there is provided an electronic device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: method steps for implementing the above exception handling method.
According to a fourth aspect of the embodiments of the present application, there is provided a computer-readable storage medium having stored therein a computer program which, when executed by a processor, implements the method steps of the above-mentioned exception handling method.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
in this embodiment, for any first network device in the S-Trunk group, when receiving an ARP request packet from a user equipment and that needs to be sent to a second network device having a neighbor relationship with the first network device, it may first determine whether a communication channel between the first network device and another first network device in the S-Trunk group is abnormal; if the result of the determination is yes, further determining whether a first ARP entry of an interface, which includes the ARP request message received by the first network device, is set as an entry that does not need to be aged, and if the result of the determination is no, setting the first ARP entry as an entry that does not need to be aged; then, based on the ARP request message, generating a second ARP table entry and a host route of the user equipment, wherein the table entry type of the second ARP table entry is a specified table entry type, and the specified table entry type is neither a static table entry nor a dynamic table entry; and finally, the ARP request message and the host route are sent to the second network equipment, so that the second network equipment sends the ARP response message to the first network equipment based on the host route after generating the ARP response message aiming at the ARP request message, thereby ensuring that the user equipment can normally carry out related service access and further improving the user experience.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
FIG. 1 is a schematic diagram of a networking system with deployed S-Trunk groups;
fig. 2 is a schematic flowchart of an exception handling method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an exception handling apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a network device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same 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 words "if" or "if" as used herein may be interpreted as "at … …" or "at … …" depending on the context.
Next, examples of the present application will be described in detail.
An embodiment of the present application provides an exception handling method, which is applied to any first network device in an S-Trunk group, and as shown in fig. 2, the method may include the following steps:
s21, when receiving ARP request message from user equipment and needing to be sent to second network equipment having neighbor relation with the first network equipment, judging whether the communication channel between the first network equipment and another first network equipment in the S-Trunk group is abnormal; if yes, go to step S22; if the determination result is negative, step S26 to step S27 are executed.
S22, judging whether the first ARP list item of the interface of the first network equipment receiving the ARP request message is set as the list item which does not need aging; if the judgment result is negative, executing the step S23 to the step S25; if the determination result is yes, step S24 to step S25 are executed.
And S23, setting the first ARP table entry as an entry which does not need to be aged.
S24, based on the ARP request message, generating a second ARP list item and a host route of the user equipment.
In this step, the entry type of the second ARP entry is a specified entry type, where the specified entry type is either a static entry or a dynamic entry.
And S25, sending the ARP request message and the host route to the second network equipment, so that the second network equipment sends the ARP response message to the first network equipment based on the host route after generating the ARP response message aiming at the ARP request message.
And S26, generating a third ARP table item of the user equipment based on the ARP request message.
In this step, the entry type of the third ARP entry is a dynamic entry.
And S27, sending the ARP request message to the second network equipment, and synchronizing the third ARP table entry to another first network equipment.
Specifically, in step S21, it may be determined whether a communication channel between the first network device and another first network device in the S-Trunk group is abnormal, by the following method:
judging whether an S-TrunkHello message sent by another first network device is received within the set keep-alive duration;
if so, determining that the communication channel is normal;
and if the judgment result is negative, determining that the communication channel is abnormal.
Here, the set keep-alive duration may be set according to an actual requirement of a network in which the first network device is located.
In step S23, when the first network device sets the first ARP entry as an entry that does not need to be aged, the first network device may specifically change the aging time (i.e., the original aging time) in the first ARP entry to "null", "negative", or the like, so as to represent that the first ARP entry is an entry that does not need to be aged.
Of course, the first network device may be configured in other manners, which are not listed here.
It should be noted that, in the step S24, the first network device generates the host route, mainly because the priority of the host route is higher than the priority of the segment route, after the first network device sends the host route to the second network device, the second network device will preferentially hit the host route when determining the outgoing interface of the ARP reply message, and send the ARP reply message to the first network device based on the host route, which can ensure that the user device normally performs related service access, thereby improving user experience.
Further, in this embodiment, the first network device may further perform the following operations:
after the ARP request message and the host route are sent to a second network device, if the communication channel is monitored to be recovered to be normal, the item type of a second ARP item with the generated item type being the specified item type is changed into a dynamic item, and the changed second ARP item is synchronized to another first network device;
deleting the local host route and sending a route revocation message to the second network device;
and restoring the first ARP table entry into the table entry needing to be aged.
In this operation flow, when the first network device restores the first ARP entry to the entry that needs to be aged, the current aging time in the first ARP entry may be specifically restored to the original aging time.
By executing the operation flow, the load of the first network equipment can be relieved in time, and the communication quality of the whole networking is improved.
The foregoing exception handling method will be described in detail with reference to specific embodiments.
Still taking the network architecture shown in fig. 1 as an example, and taking the case that the user equipment 1 needs to access the network equipment 3 and the network equipment 1 receives the ARP request message 1 from the user equipment 1 as an example, after receiving the ARP request message 1, the network equipment 1 determines whether the communication channel between the network equipment 1 and the network equipment 2 is abnormal.
If the determination result is yes, at this time, the network device 1 further determines whether an ARP entry (marked as ARP entry 1) of an interface (for example, the corresponding interface is identified as interface 1) where the network device 1 receives the ARP request message 1 is set as an entry that does not need to be aged.
If the determination result is negative, at this time, the network device 1 sets the ARP entry 1 as an entry that does not need to be aged, as shown in table one below.
Figure BDA0003470975550000081
Watch 1
Then, the network device 1 generates an ARP entry (denoted as ARP entry 2) and a host route 1 of the user device 1 based on the ARP request message 1. The entry type of ARP entry 2 is H, as shown in table two below.
Figure BDA0003470975550000082
Watch two
Finally, the network device 1 sends the ARP request message 1 and the host route 1 to the network device 3, so that after the network device 3 generates an ARP response message 1 for the ARP request message 1, the ARP response message 1 is sent to the network device 1 based on the host route 1, and the network device 1 passes through the switching device to the user device 1, thereby ensuring normal service access of the user device 1.
Next, after the network device 1 sends the ARP request message 1 to the network device 3, once it is monitored that the communication channel between the network device 1 and the network device 2 is recovered to normal, the entry type of the ARP entry whose entry type is the specified entry type that has been generated is changed into a dynamic entry, and the changed ARP entry is synchronized to the network device 2. Taking the above table two as an example, the modified table can be as shown in the following table three.
Figure BDA0003470975550000091
Watch III
Network device 1 may also delete local host routes and send a route withdraw message to network device 2 to instruct network device 2 to delete these host routes; and also restores ARP entry 1 to the entry that needs to be aged, as shown in table four below.
Figure BDA0003470975550000092
Watch four
It can be seen from the foregoing technical solutions that, in the embodiment of the present application, for any first network device in the S-Trunk group, when receiving an ARP request packet that is sent from a user equipment and needs to be sent to a second network device that has a neighbor relationship with the first network device, it is first determined whether a communication channel between the first network device and another first network device in the S-Trunk group is abnormal; if the result of the determination is yes, further determining whether a first ARP entry of an interface, which includes the ARP request message received by the first network device, is set as an entry that does not need to be aged, and if the result of the determination is no, setting the first ARP entry as an entry that does not need to be aged; then, based on the ARP request message, generating a second ARP table entry and a host route of the user equipment, wherein the table entry type of the second ARP table entry is a specified table entry type, and the specified table entry type is neither a static table entry nor a dynamic table entry; and finally, the ARP request message and the host route are sent to the second network equipment, so that the second network equipment sends the ARP response message to the first network equipment based on the host route after generating the ARP response message aiming at the ARP request message, thereby ensuring that the user equipment can normally carry out related service access and further improving the user experience.
Based on the same inventive concept, the present application further provides an exception handling apparatus, where the apparatus is applied to any first network device in an S-Trunk group, and a schematic structural diagram of the apparatus is shown in fig. 3, and specifically includes:
a first determining module 31, configured to determine whether a communication channel between a first network device and another first network device in the S-Trunk group is abnormal when receiving an ARP request packet that originates from a user equipment and needs to be sent to a second network device that has a neighbor relationship with the first network device;
a second determining module 32, configured to further determine, when the determination result of the first determining module 31 is yes, whether a first ARP entry of an interface, where the first network device receives the ARP request packet, is set as an entry that does not need to be aged;
a setting module 33, configured to set the first ARP entry as an entry that does not need to be aged when the determination result of the second determining module 32 is negative;
a first generating module 34, configured to generate a second ARP entry and a host route of the user equipment based on the ARP request packet, where an entry type of the second ARP entry is a specific entry type, and the specific entry type is neither a static entry nor a dynamic entry;
a first sending module 35, configured to send the ARP request packet and the host route to the second network device, so that the second network device sends an ARP response packet to the first network device based on the host route after generating the ARP response packet for the ARP request packet.
Preferably, the apparatus further comprises:
a second generating module (not shown in fig. 3), configured to generate a third ARP entry of the user equipment based on the ARP request packet if the determination result of the first determining module 31 is negative, where an entry type of the third ARP entry is a dynamic entry;
a second sending module (not shown in fig. 3) configured to send the ARP request packet to the second network device, and synchronize the third ARP entry to the another first network device.
Preferably, the second determining module 32 is further configured to trigger the generating module to execute a step of generating a second ARP entry and a host route of the user equipment based on the ARP request packet if the determination result is yes.
Preferably, the apparatus further comprises:
a synchronization processing module (not shown in fig. 3), configured to, after the sending module sends the ARP request packet and the host route to the second network device, if it is monitored that the communication channel is recovered to normal, change an entry type of a second ARP entry whose entry type is the specified entry type into a dynamic entry, and synchronize the changed second ARP entry to the other first network device; deleting local host routing and sending a routing revocation message to the second network device; and recovering the first ARP table entry into the table entry needing to be aged.
It can be seen from the foregoing technical solutions that, in the embodiment of the present application, for any first network device in the S-Trunk group, when receiving an ARP request packet that is sent from a user equipment and needs to be sent to a second network device that has a neighbor relationship with the first network device, it is first determined whether a communication channel between the first network device and another first network device in the S-Trunk group is abnormal; if the result of the determination is yes, further determining whether a first ARP entry of an interface, which includes the ARP request message received by the first network device, is set as an entry that does not need to be aged, and if the result of the determination is no, setting the first ARP entry as an entry that does not need to be aged; then, based on the ARP request message, generating a second ARP table entry and a host route of the user equipment, wherein the table entry type of the second ARP table entry is a specified table entry type, and the specified table entry type is neither a static table entry nor a dynamic table entry; and finally, the ARP request message and the host route are sent to second network equipment, so that after the second network equipment generates an ARP response message aiming at the ARP request message, the ARP response message is sent to the first network equipment based on the host route, and thus, the user equipment can be ensured to normally carry out related service access, and the user experience is improved.
Embodiments of the present application further provide a network device, as shown in fig. 4, including a processor 41 and a machine-readable storage medium 42, where the machine-readable storage medium 42 stores machine-executable instructions that can be executed by the processor 41, and the processor 41 is caused by the machine-executable instructions to: and implementing the steps of the exception handling method.
The machine-readable storage medium may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Alternatively, the machine-readable storage medium may be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
In yet another embodiment provided by the present application, a computer-readable storage medium is further provided, in which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the above-mentioned exception handling method.
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. An exception handling method applied to any first network device in a flexible link aggregation (S-Trunk) group, the method comprising:
when receiving an ARP request message which originates from user equipment and needs to be sent to second network equipment having a neighbor relation with the first network equipment, judging whether a communication channel between the first network equipment and another first network equipment in the S-Trunk group is abnormal or not;
if the judgment result is yes, further judging whether a first ARP table entry of an interface of the first network equipment receiving the ARP request message is set as an entry which does not need to be aged or not, and if the judgment result is no, setting the first ARP table entry as an entry which does not need to be aged;
generating a second ARP table entry and a host route of the user equipment based on the ARP request message, wherein the table entry type of the second ARP table entry is a specified table entry type, and the specified table entry type is neither a static table entry nor a dynamic table entry;
and sending the ARP request message and the host route to the second network equipment, so that the second network equipment sends an ARP response message aiming at the ARP request message to the first network equipment based on the host route after generating the ARP response message.
2. The method of claim 1, further comprising:
after judging whether a communication channel between the first network device and another first network device in the S-Trunk group is abnormal or not, if not, generating a third ARP table entry of the user equipment based on the ARP request message, wherein the table entry type of the third ARP table entry is a dynamic table entry;
and sending the ARP request message to the second network equipment, and synchronizing the third ARP table entry to the other first network equipment.
3. The method of claim 1, further comprising:
after judging whether a first ARP table entry of an interface of the first network equipment, which receives the ARP request message, is set as an entry which does not need to be aged, if so, executing a step of generating a second ARP table entry and a host route of the user equipment based on the ARP request message.
4. The method of claim 1, further comprising:
after the ARP request message and the host route are sent to the second network equipment, if the communication channel is monitored to be recovered to normal, the item type of a second ARP item with the generated item type being the specified item type is changed into a dynamic item, and the changed second ARP item is synchronized to the other first network equipment;
deleting local host routing and sending a routing revocation message to the second network device;
and restoring the first ARP table entry into a table entry needing to be aged.
5. An exception handling apparatus, applied to any first network device in a flexible link aggregation S-Trunk group, the apparatus comprising:
a first judging module, configured to, when receiving an ARP request packet that originates from a user equipment and needs to be sent to a second network device that has a neighbor relationship with the first network device, judge whether a communication channel between the first network device and another first network device in the S-Trunk group is abnormal;
a second judging module, configured to further judge whether a first ARP entry of an interface, which includes the interface where the first network device receives the ARP request packet, is set as an entry that does not need to be aged, if a judgment result of the first judging module is yes;
the setting module is used for setting the first ARP table entry as a table entry which does not need to be aged when the judgment result of the second judgment module is negative;
a first generating module, configured to generate a second ARP entry and a host route of the user equipment based on the ARP request packet, where an entry type of the second ARP entry is a specified entry type, and the specified entry type is neither a static entry nor a dynamic entry;
and the first sending module is used for sending the ARP request message and the host route to the second network equipment so as to enable the second network equipment to send an ARP response message aiming at the ARP request message to the first network equipment based on the host route after generating the ARP response message.
6. The apparatus of claim 5, further comprising:
a second generating module, configured to generate a third ARP entry of the user equipment based on the ARP request packet if the determination result of the first determining module is negative, where an entry type of the third ARP entry is a dynamic entry;
and a second sending module, configured to send the ARP request packet to the second network device, and synchronize the third ARP entry with the another first network device.
7. The apparatus according to claim 5, wherein the second determining module is further configured to trigger the generating module to perform the step of generating the second ARP entry and the host route of the user equipment based on the ARP request packet if the determination result is yes.
8. The apparatus of claim 5, further comprising:
a synchronization processing module, configured to change an entry type of a second ARP entry whose entry type is the specified entry type into a dynamic entry if it is monitored that the communication channel is recovered to normal after the sending module sends the ARP request packet and the host route to the second network device, and synchronize the changed second ARP entry to the other first network device; deleting local host routing and sending a routing revocation message to the second network device; and recovering the first ARP table entry into the table entry needing to be aged.
9. A network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: -carrying out the method steps of any one of claims 1 to 4.
10. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of claims 1-4.
CN202210042868.2A 2022-01-14 2022-01-14 Exception handling method, device, network equipment and storage medium Active CN114553761B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210042868.2A CN114553761B (en) 2022-01-14 2022-01-14 Exception handling method, device, network equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210042868.2A CN114553761B (en) 2022-01-14 2022-01-14 Exception handling method, device, network equipment and storage medium

Publications (2)

Publication Number Publication Date
CN114553761A true CN114553761A (en) 2022-05-27
CN114553761B CN114553761B (en) 2024-02-09

Family

ID=81671529

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210042868.2A Active CN114553761B (en) 2022-01-14 2022-01-14 Exception handling method, device, network equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114553761B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103441932A (en) * 2013-08-30 2013-12-11 福建星网锐捷网络有限公司 Host routing table entry generating method and device
WO2017054526A1 (en) * 2015-09-28 2017-04-06 中兴通讯股份有限公司 Arp entry generation method and device
CN111740899A (en) * 2020-07-13 2020-10-02 中国联合网络通信集团有限公司 ARP request message forwarding method, cross-device link aggregation group and network device
CN111800337A (en) * 2020-06-10 2020-10-20 锐捷网络股份有限公司 Message forwarding method and device based on data center
CN111953607A (en) * 2020-07-17 2020-11-17 新华三技术有限公司 Method and device for updating route
CN112367254A (en) * 2020-10-30 2021-02-12 新华三技术有限公司 Cross-device link aggregation method and device and electronic device

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103441932A (en) * 2013-08-30 2013-12-11 福建星网锐捷网络有限公司 Host routing table entry generating method and device
WO2017054526A1 (en) * 2015-09-28 2017-04-06 中兴通讯股份有限公司 Arp entry generation method and device
CN111800337A (en) * 2020-06-10 2020-10-20 锐捷网络股份有限公司 Message forwarding method and device based on data center
CN111740899A (en) * 2020-07-13 2020-10-02 中国联合网络通信集团有限公司 ARP request message forwarding method, cross-device link aggregation group and network device
CN111953607A (en) * 2020-07-17 2020-11-17 新华三技术有限公司 Method and device for updating route
CN112367254A (en) * 2020-10-30 2021-02-12 新华三技术有限公司 Cross-device link aggregation method and device and electronic device

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
DAESUNG MOON: "RTNSS: a routing trace-based network security system for preventing ARP spoofing attacks", 《THE JOURNAL OF SUPERCOMPUTING 》 *
樊林波;: "EPON系统的三层路由及接口设计", 通信电源技术, no. 10 *

Also Published As

Publication number Publication date
CN114553761B (en) 2024-02-09

Similar Documents

Publication Publication Date Title
CN106878166B (en) Route notification method and device
US10033667B1 (en) Enhanced virtual router redundancy protocol
EP3122004A1 (en) Traffic switching method, device, and system
US8934490B2 (en) Accelerated MAC address resolution for IPv6 traffic with IS-IS protocol
US20130304805A1 (en) Network system and network relay apparatus
US9401958B2 (en) Method, apparatus, and system for migrating user service
US20040078619A1 (en) Method and system for implementing IS-IS protocol redundancy
CN106559246B (en) Cluster implementation method and server
CN112367254B (en) Cross-device link aggregation method and device and electronic device
CN108337161B (en) Method for smoothly switching three-layer data flow of MLAG interface fault
CN106878072B (en) Message transmission method and device
US9313090B2 (en) Tunnel fault detection method and traffic engineering node
WO2014173209A1 (en) Realizing graceful restart in is-is network
US11323310B2 (en) Method, device, and system for providing hot reservation for in-line deployed network functions with multiple network interfaces
WO2020135339A1 (en) Network path convergence method and related device
CN108540386B (en) Method and device for preventing service flow interruption
EP3291486B1 (en) Selective transmission of bidirectional forwarding detection (bfd) messages for verifying multicast connectivity
CN113615132A (en) Fast flooding topology protection
CN108833272A (en) A kind of route management method and device
CN106533771B (en) Network equipment and control information transmission method
JP2009194787A (en) Gateway apparatus
EP3550785B1 (en) Message processing method and network device
CN108768845B (en) Multi-homing host routing synchronization method and device
CN114553761B (en) Exception handling method, device, network equipment and storage medium
US20200169497A1 (en) Intermediate system to intermediate system routing protocol based notification method and apparatus

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant