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

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

Info

Publication number
CN114553761B
CN114553761B CN202210042868.2A CN202210042868A CN114553761B CN 114553761 B CN114553761 B CN 114553761B CN 202210042868 A CN202210042868 A CN 202210042868A CN 114553761 B CN114553761 B CN 114553761B
Authority
CN
China
Prior art keywords
arp
table entry
network equipment
request message
network device
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
Application number
CN202210042868.2A
Other languages
Chinese (zh)
Other versions
CN114553761A (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

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 device in the S-Trunk group, and comprises the following steps: when an ARP request message which is derived from user equipment and needs to be sent to second network equipment with a neighbor relation with the first network equipment is received, 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 judging result is yes, further judging whether a first ARP table item comprising an interface of the ARP request message received by the first network equipment is set as a table item which does not need aging, and setting the first ARP table item as a table item which does not need aging when the judging result is no; generating a second ARP (address resolution protocol) 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 the second network equipment. The method and the device can improve user experience.

Description

Exception handling method, device, network equipment and storage medium
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to an exception handling method, an exception handling device, a network device, and a storage medium.
Background
Flexible link aggregation (S-Trunk) is a mechanism for cross-device link aggregation, and two network devices can be subjected to cross-device link aggregation, so that the reliability of a link is improved.
As shown in fig. 1, an S-Trunk group is created between the network device 1 and the network device 2, and the internet protocol (Internet Protocol, IP) addresses of the member ports in the S-Trunk group are in the same network segment; the switching device is deployed with an ethernet link aggregation, the interfaces of the switching device, which are connected with 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 works in a load sharing mode.
In the networking shown in fig. 1, each of the network device 1 and the network device 2 issues a network segment route corresponding to an IP address of each member port in the S-Trunk group to a corresponding neighbor device (such as the network device 3 shown in fig. 1), so that the neighbor 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 each be a routing device or the like.
When the user equipment 1 in fig. 1 needs to access the network equipment 3, for example, the IP address of the network equipment 3 is 10.1.1.1, an address resolution protocol (Address Resolution, ARP) request message 1 with a destination IP address of 10.1.1.1 is sent to the switching equipment.
After the switching device receives the ARP request message 1, the switching device determines an output interface of the ARP request message 1 based on a preset hash algorithm. The outgoing interface determined by the switching device may be an interface of the switching device connected to the network device 1 or an interface of the switching device connected to the network device 2.
Assuming that the determined outgoing interface is the interface on the switching device connected to the network device 1, the switching 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 table entry of the user device based on the ARP request message 1, where a table entry type of the ARP table entry is a dynamic table entry, synchronizes the generated ARP table 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 message for ARP request message 1, 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 an ARP response message to the network device 2, and the network device 2 finally and transparently transmits the ARP response message to the user device 1 based on the corresponding ARP table entry and the corresponding routing table, and the user device 1 continues to send a corresponding access request message.
In the whole processing process of the ARP request message, once any network device in the S-Trunk group receives the ARP request message 1, it may happen that the ARP response message is sent to another network device without being successfully synchronized with the other network device, in this case, the other network device may send the ARP request message with the destination IP address being the IP address (e.g. 10.1.1.2) of the user device to the switching device, and in the following cases, it may happen that the other network device cannot receive the ARP response message from the user device, because the ARP response message is sent to the network device by the switching device, so that the user device 1 cannot perform related service access, which seriously affects the user experience.
Disclosure of Invention
In order to overcome the problems in the related art, the application provides an exception handling method, an exception handling device, a network device and a storage medium.
According to a first aspect of an embodiment of the present application, there is provided an exception handling method, which is applied to any first network device in an S-Trunk group, the method including:
when an ARP request message which is derived from user equipment and needs to be sent to second network equipment with a neighbor relation with the first network equipment is received, 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 judging result is yes, further judging whether a first ARP table entry comprising an interface of the ARP request message received by the first network equipment is set as a table entry which does not need aging, and setting the first ARP table entry as a table entry which does not need aging when the judging result is no;
generating a second ARP (address resolution protocol) 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 designated table entry type, and the designated 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 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.
According to a second aspect of embodiments of the present application, there is provided an exception handling apparatus applied to any first network device in an S-Trunk group, the apparatus including:
the first judging module is used for judging whether the communication channel between the first network equipment and another first network equipment in the S-Trunk group is abnormal or not when an ARP request message which is derived from the user equipment and needs to be sent to the second network equipment with a neighbor relation with the first network equipment is received;
the second judging module is used for further judging whether a first ARP list item comprising an interface of the first network equipment for receiving the ARP request message is set as a list item which does not need aging when the judging 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 aging when the judging result of the second judging module is negative;
the generation module is used for generating a second ARP (address resolution protocol) 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 designated table entry type, and the designated table entry type is neither a static table entry nor a dynamic table 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 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.
According to a third aspect of embodiments of the present application, 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: the method steps of the exception handling method are realized.
According to a fourth aspect of 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-described exception handling method.
The technical scheme provided by the embodiment of the application can comprise the following beneficial effects:
in this embodiment, for any first network device in the S-Trunk group, when an ARP request message from a user device and sent to a second network device having a neighbor relation with the first network device is received, 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 judging result is yes, further judging whether a first ARP table entry comprising an interface of the first network equipment receiving the ARP request message is set as a table entry which does not need aging, and if the judging result is no, setting the first ARP table entry as a table entry which does not need aging; 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 designated table entry type, and the designated 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 can send 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 perform related service access and 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 specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
FIG. 1 is a schematic diagram of a networking deployed with an S-Trunk group;
FIG. 2 is a schematic flow chart of an exception handling method according to an embodiment of the present disclosure;
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 exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present 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 or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. The word "if" or "if" as used herein may be interpreted as "at … …" or "at … …", depending on the context.
Next, embodiments of the present application will be described in detail.
The embodiment of the application provides an exception handling method, which is applied to any first network device in an S-Trunk group, as shown in fig. 2, and may include the following steps:
s21, judging whether a communication channel between the first network equipment and another first network equipment in the S-Trunk group is abnormal or not when an ARP request message which is derived from the user equipment and needs to be sent to the second network equipment which has a neighbor relation with the first network equipment is received; if yes, executing step S22; if the determination result is negative, step S26 to step S27 are executed.
S22, judging whether a first ARP list item comprising an interface of the first network equipment receiving the ARP request message is set as a list item which does not need aging; if the judgment result is negative, executing the steps S23 to S25; if the determination result is yes, steps S24 to S25 are executed.
S23, setting the first ARP table entry as a table entry which does not need aging.
S24, generating a second ARP table entry and a host route of the user equipment based on the ARP request message.
In this step, the entry type of the second ARP entry is a specified entry type, where the specified entry type is neither a static entry nor a dynamic entry.
S25, sending the ARP request message and the host route to the second network device, so that the second network device sends the ARP response message to the first network device based on the host route after generating the ARP response message aiming at the ARP request message.
S26, generating a third ARP table entry 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.
S27, sending the ARP request message to the second network device, and synchronizing the third ARP list item to the other first network device.
Specifically, in the above step S21, for the first network device, it may be determined whether an abnormality occurs in the communication channel between the first network device and another first network device in the S-Trunk group by:
judging whether an S-Trunk Hello message sent by another first network device is received within the set keep-alive time period;
when the judgment result is yes, 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 period may be set according to actual requirements of the network in which the first network device is located.
In the step S23, when the first ARP entry is set to 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", "to" and so on, so as to be used to characterize the first ARP entry as an entry that does not need to be aged.
Of course, the first network device may also be configured in other ways, 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 network segment route, and after the first network device sends the host route to the second network device, the second network device preferentially hits the host route when determining the outbound interface of the ARP reply message, and sends the ARP reply message to the first network device based on the host route, so that it can be ensured that the user device normally performs related service access, thereby improving user experience.
Further, in the embodiment of the present application, the first network device may further perform the following operations:
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 be normal, changing the table item type of the generated second ARP table item with the table item type being the designated table item type into a dynamic table item, and synchronizing the changed second ARP table item to another first network equipment;
deleting the local host route and sending a route withdrawal message to the second network device;
and recovering the first ARP table entry into a table entry needing aging.
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 specifically be restored to the original aging time.
By executing the operation flow, the load of the first network equipment can be timely relieved, and the communication quality of the whole networking is improved.
The above-described abnormality processing method is described in detail with reference to specific embodiments.
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, the network equipment 1 determines whether an abnormality occurs in the communication channel between the network equipment 1 and the network equipment 2 after receiving the ARP request message 1.
Assuming that the determination result is yes, at this time, the network device 1 further determines whether an ARP table entry (denoted as ARP table entry 1) including an interface (for example, a corresponding interface identifier is interface 1) of the network device 1 that receives the ARP request message 1 is set as a table entry that does not require aging.
Assuming that the determination result is no, at this time, the network device 1 first sets the ARP entry 1 as an entry that does not require aging, as shown in table one below.
List one
Then, the network device 1 generates an ARP entry (denoted as ARP entry 2) of the user device 1 and the host route 1 based on the ARP request message 1. The entry type of the ARP entry 2 is H, as shown in table two below.
Watch II
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 the ARP response message 1 for the ARP request message 1, the network device 1 sends the ARP response message 1 to the network device 1 based on the host route 1, and the ARP response message is transmitted to the user device 1 through the switching device by the network device 1, so as to ensure normal service access of the user device 1.
Next, after sending the ARP request message 1 to the network device 3, the network device 1 changes the table entry type of the ARP table entry with the generated table entry type being the specified table entry type to a dynamic table entry, and synchronizes the changed ARP table entry to the network device 2 once it is monitored that the communication channel between the network device 1 and the network device 2 is restored to be normal. Taking the above table two as an example, the modified table can be shown in the following table three.
Watch III
The network device 1 will also delete the local host routes and send a route withdrawal message to the network device 2 instructing the network device 2 to delete these host routes; and also will restore ARP entry 1 to the entry that needs aging, as shown in table four below.
Table four
As can be seen from the above technical solutions, in the embodiments of the present application, when any first network device in the S-Trunk group receives an ARP request message from a user device and needs to be sent to a second network device having a neighbor relation 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 judging result is yes, further judging whether a first ARP table entry comprising an interface of the first network equipment receiving the ARP request message is set as a table entry which does not need aging, and if the judging result is no, setting the first ARP table entry as a table entry which does not need aging; 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 designated table entry type, and the designated 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 can send 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 perform related service access and 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 the S-Trunk group, and the structural schematic diagram of the apparatus is shown in fig. 3, and specifically includes:
a first judging module 31, configured to judge, when an address resolution protocol ARP request message originated from a user equipment and required to be sent to a second network device having a neighbor relation with the first network device, 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 32, configured to further judge, when the judging result of the first judging module 31 is yes, whether a first ARP table entry including an interface of the first network device that receives the ARP request message is set to be a table entry that does not need aging;
a setting module 33, configured to set the first ARP entry as an entry that does not need aging when the determination result of the second determining module 32 is no;
a first generating module 34, configured to generate a second ARP table entry and a host route of the user device based on the ARP request message, where a 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;
a first sending module 35, configured to send the ARP request message and the host route to the second network device, so that after the second network device generates an ARP response message for the ARP request message, the second network device sends the ARP response message to the first network device based on the host route.
Preferably, the apparatus further comprises:
a second generation module (not shown in fig. 3), configured to generate a third ARP entry of the user equipment based on the ARP request message when the determination result of the first determination module 31 is no, 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 message to the second network device, and synchronize the third ARP entry to the other first network device.
Preferably, the second judging module 32 is further configured to trigger the generating module to execute the step of generating the second ARP entry of the user equipment and the host route based on the ARP request message when the self judging 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 message and the host route to the second network device, change an entry type of the generated second ARP entry with the specified entry type to a dynamic entry if it is monitored that the communication channel is restored to normal, and synchronize the changed second ARP entry to the other first network device; deleting a local host route and sending a route withdrawal message to the second network device; and recovering the first ARP table entry into a table entry needing aging.
As can be seen from the above technical solutions, in the embodiments of the present application, when any first network device in the S-Trunk group receives an ARP request message from a user device and needs to be sent to a second network device having a neighbor relation 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 judging result is yes, further judging whether a first ARP table entry comprising an interface of the first network equipment receiving the ARP request message is set as a table entry which does not need aging, and if the judging result is no, setting the first ARP table entry as a table entry which does not need aging; 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 designated table entry type, and the designated 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 can send 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 perform related service access and improving the user experience.
The present embodiments also provide a network device, as shown in fig. 4, including a processor 41 and a machine-readable storage medium 42, the machine-readable storage medium 42 storing machine-executable instructions executable by the processor 41, the processor 41 being caused by the machine-executable instructions to: and the step of realizing the exception handling method.
The machine-readable storage medium may include random access Memory (Random Access Memory, RAM) or Non-Volatile Memory (NVM), such as at least one magnetic disk Memory. In the alternative, the machine-readable storage medium may also be at least one memory device located remotely from the foregoing processor.
The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
In yet another embodiment provided herein, there is also provided a computer-readable storage medium having stored therein a computer program which, when executed by a processor, implements the steps of the above-described exception handling method.
The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.

Claims (10)

1. An exception handling method, wherein the method is applied to any first network device in a flexible link aggregation S-Trunk group, the method comprising:
when an address resolution protocol ARP request message which is derived from user equipment and needs to be sent to second network equipment with a neighbor relation with the first network equipment is received, 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 judging result is yes, further judging whether a first ARP table entry comprising an interface of the ARP request message received by the first network equipment is set as a table entry which does not need aging, and setting the first ARP table entry as a table entry which does not need aging when the judging result is no;
generating a second ARP (address resolution protocol) 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 designated table entry type, and the designated 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 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.
2. The method according to claim 1, wherein the method further comprises:
after judging whether the communication channel between the first network device and another first network device in the S-Trunk group is abnormal, if not, generating a third ARP table entry of the user device 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 according to claim 1, wherein the method further comprises:
after judging whether a first ARP table entry comprising an interface of the first network equipment receiving the ARP request message is set as a table entry which does not need aging, if so, executing the step of generating a second ARP table entry of the user equipment and a host route based on the ARP request message.
4. The method according to claim 1, wherein the method further comprises:
after the ARP request message and the host route are sent to the second network equipment, if the communication channel is monitored to be normal, changing the table entry type of the generated second ARP table entry with the table entry type being the appointed table entry type into a dynamic table entry, and synchronizing the changed second ARP table entry to the other first network equipment;
deleting a local host route and sending a route withdrawal message to the second network device;
and recovering the first ARP table entry into a table entry needing aging.
5. An exception handling apparatus, the apparatus being applied to any first network device in a flexible link aggregation S-Trunk group, the apparatus comprising:
the first judging module is used for judging whether the communication channel between the first network equipment and another first network equipment in the S-Trunk group is abnormal or not when an Address Resolution Protocol (ARP) request message which is derived from the user equipment and needs to be sent to the second network equipment with a neighbor relation with the first network equipment is received;
the second judging module is used for further judging whether a first ARP list item comprising an interface of the first network equipment for receiving the ARP request message is set as a list item which does not need aging when the judging 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 aging when the judging result of the second judging module is negative;
the first generation module is used for generating a second ARP (address resolution protocol) 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 designated table entry type, and the designated table entry type is neither a static table entry nor a dynamic table entry;
and the first 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 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.
6. The apparatus of claim 5, wherein the apparatus further comprises:
the second generating module is configured to generate a third ARP table entry of the user equipment based on the ARP request message when the determination result of the first determining module is no, where a table entry type of the third ARP table entry is a dynamic table entry;
and the second sending module is used for sending the ARP request message to the second network equipment and synchronizing the third ARP list item to the other first network equipment.
7. The apparatus of claim 5, wherein the second judging module is further configured to trigger the generating module to execute the step of generating the second ARP entry and the host route of the user device based on the ARP request message when the judging result of the second judging module is yes.
8. The apparatus of claim 5, wherein the apparatus further comprises:
the synchronization processing module is configured to, after the sending module sends the ARP request message and the host route to the second network device, change an entry type of a second ARP entry that is the specified entry type to a dynamic entry if it is monitored that the communication channel is restored to normal, and synchronize the changed second ARP entry to the other first network device; deleting a local host route and sending a route withdrawal message to the second network device; and recovering the first ARP table entry into a table entry needing aging.
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: method steps of any of claims 1-4 are achieved.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored therein a computer program which, when executed by a processor, implements the method steps of any 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 CN114553761A (en) 2022-05-27
CN114553761B true 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
EPON系统的三层路由及接口设计;樊林波;;通信电源技术(第10期);全文 *
RTNSS: a routing trace-based network security system for preventing ARP spoofing attacks;Daesung Moon;《The Journal of Supercomputing 》;全文 *

Also Published As

Publication number Publication date
CN114553761A (en) 2022-05-27

Similar Documents

Publication Publication Date Title
EP3122004B1 (en) Traffic switching method, device, and system
US20200220803A1 (en) Link-State Advertisement LSA Sending Method, Apparatus, and System
US10033667B1 (en) Enhanced virtual router redundancy protocol
US8934490B2 (en) Accelerated MAC address resolution for IPv6 traffic with IS-IS protocol
US20030128668A1 (en) Distributed implementation of control protocols in routers and switches
CN106559246B (en) Cluster implementation method and server
WO2009067865A2 (en) Method, router, line card and active master card for realizng a link state database synchronization
CN112367254B (en) Cross-device link aggregation method and device and electronic device
US11855876B2 (en) BMP route detection method and network device
WO2014173209A1 (en) Realizing graceful restart in is-is network
WO2020135339A1 (en) Network path convergence method and related device
US11323310B2 (en) Method, device, and system for providing hot reservation for in-line deployed network functions with multiple network interfaces
CN113746733A (en) Table item synchronization method, gateway equipment, networking system and storage medium
CN108833272B (en) Route management method and device
US20200366602A1 (en) Coordinating pseudowire connection characteristics and multi-homed provider edge device capabilities
WO2018219103A1 (en) Method and device for determining link state
CN113615132A (en) Fast flooding topology protection
US20210320858A1 (en) Preventing traffic outages during address resolution protocol (arp) storms
CN114553761B (en) Exception handling method, device, network equipment and storage medium
US11088939B1 (en) Reducing open shortest path first protocol link flap
EP3550785B1 (en) Message processing method and network device
US20200169497A1 (en) Intermediate system to intermediate system routing protocol based notification method and apparatus
JP2011166245A (en) Network system, switching method of gateway device, first tunnel termination gateway device and second tunnel termination gateway device
JP6459665B2 (en) COMMUNICATION DEVICE, COMMUNICATION SYSTEM, COMMUNICATION METHOD, AND COMMUNICATION PROGRAM
CN109981463B (en) Information processing method, device, gateway and storage medium

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