WO2024066587A1

WO2024066587A1 - Message forwarding method, communication device, and storage medium

Info

Publication number: WO2024066587A1
Application number: PCT/CN2023/104221
Authority: WO
Inventors: 林宁
Original assignee: 中兴通讯股份有限公司
Priority date: 2022-09-30
Filing date: 2023-06-29
Publication date: 2024-04-04
Also published as: CN117857484A

Abstract

The present application discloses a message forwarding method, a communication device, and a storage medium. The method comprises: when a physical port of a network device fails, deleting corresponding physical port information from a pre-configured virtual port table of the network device, wherein the virtual port table comprises the correspondence between the physical port and a virtual port of the network device, and port information in an ARP entry corresponding to the physical port is virtual port information corresponding to the physical port corresponding to the ARP entry.

Description

Message forwarding method, communication device and storage medium

Related Applications

This application claims priority to Chinese patent application No. 202211210587.X filed on September 30, 2022, the entire contents of which are incorporated by reference into this application.

Technical Field

The present application relates to the field of network technology, and in particular to a message forwarding method, communication equipment and storage medium.

Background technique

Generally speaking, the ARP (Address Resolution Protocol) entry of a network device identifies the host route of the network device, and its exit points to a forwarding path of this network device. This path includes the physical port, the MAC (Media Access Control) address of the other host, Vlan (Virtual Local Area Network) and other information.

At present, when the physical port of a network device and its related forwarding path fails, the convergence process of the related ARP entries after the physical port fails needs to be processed one by one, which is time-consuming. In some scenarios, it is necessary to quickly converge the ARP entries after the physical port fails to achieve the effect of fast network switching, but the current ARP convergence technology cannot meet the requirements of fast convergence in such scenarios.

Summary of the invention

In view of this, the main purpose of the embodiments of the present application is to propose a message forwarding method, communication equipment and storage medium, which aims to quickly complete ARP entry convergence when the physical port of the network device fails, so as to achieve the effect of fast network switching, improve the response speed of the network device to network abnormalities, and improve the routing performance of the entire network.

The present application provides a message forwarding method, which is applied to a network device and includes:

In the event that a physical port of a network device fails, the corresponding physical port information is deleted from a pre-configured virtual port table of the network device, wherein the virtual port table includes a correspondence between the physical port and the virtual port of the network device, and the port information in the ARP entry corresponding to the physical port is the virtual port information corresponding to the physical port corresponding to the ARP entry.

An embodiment of the present application also provides a communication device, which includes a memory, a processor, and a message forwarding program stored in the memory and executable on the processor, wherein the message forwarding program implements the message forwarding method described above when executed by the processor.

An embodiment of the present application further provides a computer-readable storage medium, on which a message forwarding program is stored. When the message forwarding program is executed by a processor, the message forwarding method as described above is implemented.

The embodiment of the present application proposes a message forwarding method, communication device and storage medium. When a physical port of a network device fails, the corresponding physical port information is deleted in a pre-configured virtual port table of the network device. The virtual port table includes the correspondence between the physical port and the virtual port of the network device. The port information in the ARP entry corresponding to the physical port is the virtual port information corresponding to the physical port corresponding to the ARP entry. Thus, by pre-configuring the virtual port table, configuring the correspondence between the physical port and the virtual port of the network device in the virtual port table, and pre-configuring the port information in the ARP entry as the virtual port information corresponding to the physical port corresponding to the ARP entry, when the physical port of the network device fails, it is only necessary to delete the corresponding physical port information in the ARP table entry without processing the ARP entries one by one, so that the ARP entry convergence can be completed quickly to achieve the effect of fast network switching.

Compared with the general ARP processing method in the prior art, the embodiment of the present application uses a virtual port (VP) to replace the physical port to write into the ARP table through the above technical solution, which can not only complete the one-time operation of the ARP table when the physical port fails, so as to achieve the rapid convergence and rapid flow cutting of the ARP entry, but also complete the flow processing of the ARP table in the case of port oscillation without causing a large number of routing oscillations. It is a very efficient and simple ARP processing method when the port fails. Therefore, the use of this method can improve the response speed of network equipment to network abnormalities, improve the routing convergence speed of the entire network, and improve the routing performance of the entire network.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor.

FIG1 is a flow chart of an embodiment of a message forwarding method of the present application;

FIG2 is a flow chart of another embodiment of the message forwarding method of the present application;

FIG3 is a flow chart of another embodiment of the message forwarding method of the present application;

FIG4 is a schematic diagram of the internal flow of a network device in an embodiment of the present application;

FIG5 is a schematic diagram of an actual networking application scenario of an embodiment of the present application;

FIG6 is a schematic diagram of functional modules of an embodiment of a message forwarding device of the present application;

FIG. 7 is a schematic diagram of functional modules of an embodiment of a communication device of the present application.

The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

In this article, the term "comprises", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element. Components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context in the specific embodiment.

Although the terms first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this article, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination". Furthermore, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising" and "including" indicate the presence of the described features, steps, operations, elements, components, projects, kinds, and/or groups, but do not exclude the presence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and/or groups. The terms "or", "and/or", "including at least one of the following" used in this application, etc. can be interpreted as inclusive, or mean any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”, and for another example, “A, B or C” or “A, B and/or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will only occur when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

Although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

In this article, step codes such as S10, S100, etc. are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the sequence.

The specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.

In the embodiments of the present application, the communication device may be a server, a terminal device, or a base station device, etc., and the present application needs to be determined according to the specific context.

The following description will be made by taking a server as an example, and those skilled in the art will understand that, in addition to components specifically used for mobile purposes, the construction according to the embodiments of the present application can also be applied to other fixed types of terminals.

The main solution of the embodiment of the present application is: in the case of failure of the physical port of the network device, the corresponding physical port information is deleted in the pre-configured virtual port table of the network device, the virtual port table includes the correspondence between the physical port and the virtual port of the network device, and the port information in the ARP entry corresponding to the physical port is the virtual port information corresponding to the physical port corresponding to the ARP entry. Therefore, by pre-configuring the virtual port table and configuring the correspondence between the physical port and the virtual port of the network device in the virtual port table, it is only necessary to delete the corresponding physical port information in the ARP table entry without processing the ARP entries one by one, so that the ARP entry convergence can be completed quickly to achieve the effect of fast network switching, improve the response speed of the network device to network abnormalities, and improve the routing performance of the entire network.

Technical terms involved in the embodiments of this application:

VP, Virtual Port, virtual port;

ARP, Address Resolution Protocol, is a TCP/IP protocol that obtains the physical address based on the IP address. When a host sends information, it broadcasts the ARP request containing the target IP address to all hosts on the network and receives the return message to determine the physical address of the target; after receiving the return message, the IP address and physical address are stored in the local ARP cache and retained for a certain period of time. The next request directly queries the ARP cache to save resources.

ARP table: refers to the host routing table, which includes several ARP entries. The ARP entry in the ARP table identifies the host route of the network device, and its exit points to a forwarding path of this network device. In the embodiment of the present application, this path contains the routing information of the network device such as the VP corresponding to the physical port, the MAC address of the opposite host, and the Vlan.

Convergence of ARP entries: ARP entries converge in response to the failure of the physical port of the network device and its related forwarding path. The so-called convergence means that after the physical port fails, all related ARP entries are deleted, and the neighboring devices are notified of the related route deletion through the routing protocol.

MC-LAG, Multi-Chassis Link Aggregation Group, cross-device link aggregation group: After entering the era of mobile Internet, the Internet has become increasingly closely integrated with people's daily lives. While bringing people a convenient network experience, it has also brought the interactive processing of massive data to the network, and put forward higher requirements for the bandwidth and reliability of the network. However, traditional link aggregation technology is limited to one-to-one between two devices, and cannot achieve link aggregation between one-to-many devices. Therefore, in order to provide a more reliable network, MC-LAG was created. When an access device (which can be a server or a switch) is connected to two upper-layer network devices A and B, MC-LAG technology can be used to form a cross-device link aggregation group.

The basic idea of MC-LAG is to allow two network devices A and B to perform link aggregation with the access device in the same state. From the access device's point of view, it is as if a link aggregation relationship has been established with the same network device. In this way, link aggregation technology is expanded from one-to-one device docking to being able to access two devices at the same time and form a dual-active system.

VLAN, Virtual Local Area Network, is a logical segmentation of network users connected to the second layer switch port. It is not limited by the physical location of the network users but is segmented according to user needs. A VLAN can be implemented on a switch or across switches. VLANs can be grouped according to the location, role, department of network users or according to the applications and protocols used by network users. Switch-based virtual LANs can solve conflict domains, broadcast domains, and bandwidth issues for LANs.

MAC address, Media Access Control address, also known as LAN address, Ethernet address, physical address, media access control address, is an address used to confirm the location of network devices. The length of a MAC address is 48 bits (6 bytes), usually expressed as 12 hexadecimal numbers. The MAC address is used to uniquely identify a network card in the network. If a device has one or more network cards, each network card needs and will have a unique MAC address. MAC address filtering technology can ensure that authorized MAC addresses can access network resources.

VPN, Virtual Private Network, is a communication method used to connect medium and large enterprises or private networks between groups. It uses tunneling protocols to achieve confidentiality, sender authentication, message accuracy and other private message security effects. VPN technology can use insecure networks to send reliable and secure messages, which can be achieved through servers, hardware, software and other methods.

The embodiment of the present application considers that, in the related art, the convergence process of the ARP entry response to the failure of the physical port of the network device and its related forwarding path is as follows:

First, the network device senses the abnormality of the port and notifies the CPU of the abnormality of the physical port;

Then, the CPU notifies the protocol stack according to the abnormal physical port. The protocol stack calculates all ARP entries (i.e., ARP entries) that need to be deleted according to the abnormal physical port, and notifies the network device one by one to perform hardware deletion of the ARP entries.

Finally, the protocol stack receives a message that the hardware has been successfully deleted and notifies other network devices of the deleted ARP entry through the routing protocol.

It can be seen that in the prior art, the convergence of related ARP entries after the failure of a physical port is a relatively time-consuming process, and its processing is related to the ARP entries. The more ARP entries there are, the slower the processing time. In some scenarios, it is necessary to quickly converge the ARP entries after the failure of a physical port to achieve the effect of fast network switching. For example, in the network switching scenario of MCLAG (Multi-Chassis Link Aggregation Group, cross-device link aggregation group), similar requirements will arise, and the current ARP convergence technology cannot meet the requirements of fast convergence in such scenarios.

Therefore, the embodiment of the present application proposes a solution, in the case of a physical port failure of a network device, all the ARP entries related thereto can be quickly converged at one time. With this method, there is no need to process the ARP entries one by one, but all the ARP entries related thereto can be directly processed according to the physical port. Therefore, with this method, all the ARP entries related to the failed physical port can be quickly converged, and the neighboring network devices can be quickly notified. Thereby, the response speed of the network device to the network abnormality is improved, the routing convergence speed of the whole network is improved, and the routing performance of the whole network is improved.

Refer to Figure 1, which is a flow chart of an embodiment of a message forwarding method of the present application.

As shown in FIG. 1 , an embodiment of the present application provides a message forwarding method, which is applied to a network device and includes:

Step S101, when a physical port of a network device fails, the corresponding physical port information is deleted in a pre-configured virtual port table of the network device, the virtual port table includes a correspondence between the physical port and the virtual port of the network device, and the port information in the ARP entry corresponding to the physical port is the virtual port information corresponding to the physical port corresponding to the ARP entry.

In this embodiment, the network device may be a switch or a router, etc., and the internal processing flow of the network device may be shown in FIG. 4 .

The application environment of the message forwarding method of this embodiment may include: a switch or a router needs to quickly converge and respond to changes in the ARP entry of a physical port, for example, in MCLAG switching, core network connection, etc. The actual networking scenario can be shown in FIG5 .

The execution subject of the method of this embodiment may be a network device.

In this embodiment, the network device is pre-configured with a virtual port table, wherein the virtual port table includes a correspondence between the physical ports of the network device and the virtual ports.

In addition, in this embodiment, the ARP entry in the ARP table sent to the network device identifies the host route of the network device, and its exit points to a forwarding path of this network device, which includes the virtual port corresponding to the physical port, the MAC address of the opposite host, Vlan and other routing information of the network device.

In this embodiment, the port information in the ARP entry is the virtual port information corresponding to the physical port corresponding to the ARP entry corresponding to the physical port, that is, the physical port information in the ARP entry of the physical port corresponding to the virtual port is replaced with the virtual port information.

The virtual port table may be a VP table, or other table entries similar to the VP that can be bound to a physical port and can find the physical port during forwarding. This embodiment takes the VP table as an example.

The main idea of the embodiment of the present application is to utilize the virtual port VP resources of the network device and correspond one-to-one with the physical port. When ARP processing is performed, the real physical port is no longer used to write into the ARP table, but VP is written into the ARP table, and the information of the real physical port is then corresponded in the VP table. When the physical port of the network device fails and ARP entries need to be converged, the ARP entries are no longer processed one by one, but the VP table is processed directly. In this way, all ARP entries related to the failed physical port can be quickly converged, thereby achieving a fast convergence effect.

This embodiment takes into account that: network devices generally have VP resources, which are normally used for VPN services. This embodiment uses the VP resources to manage ARP entries, thereby achieving the effect of fast convergence of ARP entries when a physical port fails.

A virtual port table (VP table is used as an example below) is pre-configured on the network device, and the VP is written into the ARP table, and the real physical port is no longer used to write into the ARP table.

The VP table includes the correspondence between the physical ports and virtual ports (hereinafter referred to as VP) of the network device.

The VP table includes VPs and physical port information corresponding to the VPs one by one, wherein the physical port information may include a physical port ID.

Write the egress path with the ARP entry in the ARP table.

The ARP entry in the ARP table identifies the host route of the network device, and its exit points to a forwarding path of this network device. Contains the routing information of network devices such as the VP corresponding to the physical port, the MAC address of the remote host, and VLAN.

The port information in the ARP entry is virtual port information corresponding to the physical port corresponding to the ARP entry.

In specific implementation, firstly, the VP of the network device is matched with the physical port of the network device one by one. Specifically, the corresponding port ID of the physical port can be written into the VP table.

Then, when issuing ARP table entries, VP is used in the hardware of the network device to replace the existing method of using physical ports to write into the ARP table, that is, the exit path of the ARP entry is no longer written as: physical port + host MAC + vlan, but as: VP + host MAC + vlan. That is, VP is written into the ARP table entry, and the real physical port is no longer used to write into the ARP table. At the same time, the correspondence between the virtual port VP and the physical port is configured in the VP table.

Since the VP table corresponds to the relationship between VP and physical port, when the network device forwards the message, the message finds the exit through the ARP entry. When it is found that the exit is a VP, the real exit will be found in the VP table, so as to find the real physical port for forwarding. In this way, the message forwarding can still be carried out according to the original correct path.

In this embodiment, when the network device senses that the physical port fails, the corresponding physical port information is deleted from the pre-configured virtual port table of the network device, and the virtual port table includes the correspondence between the physical port and the virtual port of the network device. After this processing, when the physical port fails, there is no need to process the ARP entries one by one.

When the physical port of a network device fails, after the network device directly deletes the corresponding physical port information in the VP table, all VPs of ARP entries related to this physical port will not be able to find the real physical exit in the VP table, so all traffic is immediately interrupted, ARP entries cannot forward traffic, and messages cannot be forwarded.

As an implementation method, after the network device directly deletes the corresponding physical port information in the VP table, the ARP entry related to the physical port can be deleted to the neighbor devices of the network device through the routing protocol. Thus, through the notification, the neighbor devices of the network device can be informed that the corresponding physical port has failed, and the ARP entries related to the failed physical port need to be deleted. The neighbor devices of the network device can then delete all routes related to the failed physical port. Therefore, when the physical port of the network device fails, it is only necessary to delete the corresponding physical port information in the ARP table item without processing the ARP entries one by one, so that the ARP entry convergence can be completed quickly, thereby achieving the effect of fast network switching.

As an implementation method, after the network device directly deletes the corresponding physical port information in the VP table, it notifies the CPU that the corresponding physical port information in the VP table has been successfully deleted. The CPU immediately triggers a routing protocol notification to delete all ARP entries related to the failed physical port in the network protocol to the neighbors of the network device.

At this time, the CPU of the network device quickly sends out a routing announcement, but the ARP entry of the hardware in the network device is not really deleted. The ARP entry in the hardware still exists, but because its egress VP has failed, the ARP entry cannot forward traffic at present. Therefore, in the case of a physical port failure of the network device, you only need to delete the corresponding physical port information in the ARP table entry without processing the ARP entries one by one, so that the ARP entry convergence can be completed quickly, achieving the effect of fast network switching.

At this time, the real hardware ARP entries in the network device can be deleted one by one according to the routing protocol. Since the routing announcement and the forwarding interruption of the ARP entries of the underlying hardware have been completed, the deletion of the ARP entries in the hardware will no longer affect the fast convergence speed of the entire network.

According to the above scheme, it can be seen that, unlike the prior art, the routing processing scheme of this embodiment no longer needs to process the deletion of hardware ARP entries one by one, nor does it need to wait for the hardware ARP entry deletion time and then notify the neighbor device through the network protocol. Instead, it only needs to operate the VP once, and all ARP entries can be deleted according to the result of this operation. The speed of this operation is no longer related to the number of ARP entries, so it can achieve the effect of fast response and fast convergence, and the actual operation result can reach a convergence speed of milliseconds.

This embodiment uses the above scheme. When a physical port of a network device fails, the corresponding physical port information is deleted from a pre-configured virtual port table of the network device. The virtual port table includes the correspondence between the physical port of the network device and the virtual port. The port information in the ARP entry corresponding to the physical port is the virtual port information corresponding to the physical port corresponding to the ARP entry. Thus, by pre-configuring the virtual port table and configuring the correspondence between the physical port and the virtual port of the network device in the virtual port table, when a physical port of the network device fails, it is only necessary to delete the corresponding physical port information in the ARP table entry without processing the ARP entries one by one, so that the ARP entry convergence can be completed quickly to achieve the effect of fast network switching.

Compared with the existing general ARP processing method, the embodiment of the present application uses the above technical solution to use a virtual port (VP) to replace the physical port to write into the ARP table, which can not only complete the one-time operation of the ARP table when the physical port fails, to achieve rapid convergence of ARP entries and rapid traffic cutoff, but also complete the traffic processing of ARP table entries in the case of port oscillation without causing a large number of routing oscillations. A very efficient and simple ARP processing method when a port fails. Therefore, using this method can improve the response speed of network devices to network abnormalities, improve the routing convergence speed of the entire network, and improve the routing performance of the entire network.

Refer to FIG. 2 , which is a flow chart of another embodiment of the message forwarding method of the present application.

As shown in FIG. 2 , another embodiment of the present application proposes a message forwarding method. Based on the embodiment shown in FIG. 1 above, in the above step S101, when the physical port of the network device fails, after deleting the corresponding physical port information in the pre-configured virtual port table of the network device, it also includes:

Step S102: Sending a notification of physical port failure to a neighbor device of the network device through a routing protocol, so that the neighbor device deletes all ARP entries related to the failed physical port.

After the network device directly deletes the corresponding physical port information in the VP table, the ARP entry related to the physical port can be deleted to the neighbor devices of the network device through the routing protocol. Thus, through the notification, the neighbor devices of the network device can be informed that the corresponding physical port has failed, and all ARP entries related to the failed physical port need to be deleted. The neighbor devices of the network device can then delete all routes related to the failed physical port. Therefore, when the physical port of the network device fails, it is only necessary to delete the corresponding physical port information in the ARP table item without processing the ARP entries one by one, so as to quickly complete the ARP entry convergence and achieve the effect of fast network switching.

As an implementation manner, the method may further include, before deleting the corresponding physical port information in the pre-configured virtual port table of the network device:

Creating a virtual port table for characterizing the correspondence between virtual ports and physical ports;

The physical port information in the ARP entry of the physical port corresponding to the virtual port is replaced with the virtual port information corresponding to the physical port.

Generate a first correspondence table, the first correspondence table is used to represent the correspondence between the virtual port corresponding to the physical port of the network device and the ARP entry of the physical port, the port information of the ARP entry in the first correspondence table is the virtual port information corresponding to the physical port corresponding to the ARP entry; and/or

A second correspondence table is generated, where the second correspondence table is used to characterize the correspondence between the physical port of the network device and the ARP entry, and the port information of the ARP entry in the second correspondence table is the virtual port information corresponding to the physical port corresponding to the ARP entry.

As an implementation mode, a notification of physical port failure is sent to a neighbor device of the network device through a routing protocol so that the neighbor device deletes all ARP entries related to the failed physical port. The following solution may be adopted:

First, based on the failed physical port, the virtual port table is searched to obtain the corresponding target virtual port;

Based on the target virtual port, the first correspondence table is searched, as shown in FIG4 , to obtain a target ARP entry corresponding to the target virtual port, wherein the first correspondence table includes a correspondence between a virtual port corresponding to a physical port of the network device and an ARP entry of the physical port, and the port information of the ARP entry in the first correspondence table is virtual port information corresponding to the physical port corresponding to the ARP entry;

Finally, the target ARP entry is notified to the neighboring device of the network device through a routing protocol, so that the neighboring device deletes the corresponding target ARP entry.

As another implementation, a notification of physical port failure is sent to a neighbor device of the network device through a routing protocol so that the neighbor device deletes all ARP entries related to the failed physical port. The following solution may also be adopted:

Searching the second correspondence table based on the failed physical port to obtain a target ARP entry corresponding to the failed physical port, wherein the second correspondence table includes a correspondence between the physical port of the network device and the ARP entry (VP1 in the first correspondence table shown in FIG. 4 may be replaced with PORT1 to obtain a second correspondence table of correspondence between the physical port and the ARP entry), and the port information of the ARP entry in the second correspondence table is virtual port information;

Then, the target ARP entry is notified to the neighboring device of the network device through a routing protocol, so that the neighboring device deletes the corresponding target ARP entry.

Searching the virtual port table based on the failed physical port to obtain the corresponding target virtual port;

Through a routing protocol, a routing notification of the invalidation of the target virtual port is sent to a neighbor device of the network device, so that the neighbor device deletes all target ARP entries corresponding to the target virtual port according to the first correspondence table obtained from the network device, wherein the first correspondence table includes the correspondence between the virtual port corresponding to the physical port of the network device and the ARP entry of the physical port, and the port information of the ARP entry in the first correspondence table is the virtual port information corresponding to the physical port corresponding to the ARP entry.

As mentioned above, this embodiment corresponds the VP of the network device to the physical port of the network device one by one, and writes it into the VP table. At the same time, the VP table is written into the ARP table item. That is, when the ARP table item is issued, the VP is used to replace the physical port to write the ARP table item in the hardware of the network device, that is, the exit path of the ARP item is no longer written as: physical port + host MAC + vlan, but as: VP + host MAC + vlan. That is, the VP table is written in the ARP table item, and the real physical port is no longer used to write the ARP table item. At the same time, the correspondence between the VP and the physical port is configured in the VP table.

Since the VP table corresponds to the relationship between VP and physical port, when the network device forwards the message, the message finds the exit through the ARP entry. When it is found that the exit is a VP, the real physical port will be found in the VP table to find the real physical port for forwarding. In this way, the message forwarding can still be carried out according to the original correct path.

When a physical port fails, the network device directly deletes the corresponding physical port information in the VP table. In this way, the VP of all ARP entries related to this failed physical port will not be able to find the real physical port in the VP table. Therefore, all traffic is immediately interrupted, the ARP entry cannot forward traffic, and the message cannot be forwarded.

In this embodiment, it is necessary for the neighboring devices of the network device to timely learn the routing information related to the ARP table entries of the network device.

Therefore, after obtaining the ARP table entry, the network device of this embodiment sends the relevant ARP entry and the corresponding VP routing announcement to the neighboring device of the network device through the routing protocol, so that the neighboring device obtains the association relationship table between the VP and the ARP entry, that is, the first correspondence relationship table.

Subsequently, after receiving the routing advertisement of the invalid target virtual port sent by the network device, the neighbor device of the network device may delete all target ARP entries corresponding to the target virtual port according to the first correspondence table obtained from the network device.

Therefore, if the neighboring device supports associating the received VP information with the ARP entry, the network device can directly notify the neighboring device of the VP failure before notifying the ARP entry deletion. At this time, the neighboring device can delete all ARP entries related to this VP at a faster speed. In this way, the neighboring device can also revoke all related routes at a faster speed.

When the network device notifies the routing information related to these ARP table entries through the routing protocol, it can simultaneously notify the VP information and the related information of the ARP table entries. In this way, the corresponding entries related to the VP and the routing can also be formed on the neighboring device. In this way, when the physical port of the network device fails, the network device can immediately send a VP failure message to the neighboring device, and the neighboring device can immediately delete all the routing entries related to this VP based on this VP information. This avoids unnecessary routing forwarding operations of neighboring devices, improves the response speed of network devices to network abnormalities, improves the routing convergence speed of the entire network, and improves the routing performance of the entire network.

It can be seen from the above-mentioned scheme that after the network device directly deletes the corresponding physical port information in the VP table, the ARP entry related to the physical port can be deleted to the neighboring devices of the network device through the routing protocol. Through the notification, the neighboring devices of the network device can be informed that the corresponding physical port has failed, and the ARP entries related to the failed physical port need to be deleted. The neighboring devices of the network device can then delete all routes related to the failed physical port. Therefore, when the physical port of the network device fails, it is only necessary to delete the corresponding physical port information in the ARP table item without processing the ARP entries one by one, so as to quickly complete the ARP entry convergence and achieve the effect of fast network switching.

According to the above scheme, it can be seen that, unlike the prior art, the routing processing scheme of this embodiment no longer needs to process one by one. When deleting hardware ARP entries, there is no need to wait for the hardware ARP entry deletion time and then notify neighbor devices through the network protocol. Instead, you only need to perform an operation on the VP once, and all ARP entries can be deleted based on the result of this operation. The speed of this operation is no longer related to the number of ARP entries, so it can achieve the effect of fast response and fast convergence, and the actual operation result can reach a convergence speed of milliseconds.

Refer to FIG. 3 , which is a flow chart of another embodiment of the message forwarding method of the present application.

As shown in FIG. 3 , another embodiment of the present application provides a message forwarding method. Based on the embodiment shown in FIG. 1 above, the method further includes:

Step S103: Delete the target ARP entries corresponding to the invalid physical ports one by one through the routing protocol.

Compared with the embodiment shown in FIG. 1 , this embodiment further includes: a solution in which the network device deletes the ARP entry related to the failed physical port.

As an implementation mode, when a network device senses that a physical port fails, the corresponding physical port information in the VP table is deleted from the ARP table entry of the network device.

After the network device deletes the corresponding physical port information in the VP table in the ARP table entry, it notifies the CPU that the corresponding physical port information in the VP table has been successfully deleted. The CPU immediately triggers a routing protocol notification to delete all ARP entries related to the invalid physical port in the network protocol to the neighbors of the network device.

At this time, the CPU of the network device quickly sends out a routing announcement, but the ARP entry of the hardware in the network device is not actually deleted. The ARP entry in the hardware still exists, but because its egress VP has expired, the ARP entry cannot currently forward traffic.

In this embodiment, the network device deletes the ARP entry related to the failed physical port in the network device according to the routing protocol.

As an implementation method, the relationship between the ARP entry and the VP can be stored in a fast-retrieval correspondence table (ie, the first correspondence table in this embodiment) on the network device for fast software deletion.

The specific implementation is as follows:

Then, based on the target virtual port, searching the first correspondence table to obtain a target ARP entry corresponding to the target virtual port, wherein the first correspondence table includes a correspondence between a virtual port corresponding to a physical port of the network device and an ARP entry of the physical port, and the port information of the ARP entry in the first correspondence table is virtual port information corresponding to the physical port corresponding to the ARP entry;

Finally, the target ARP entries are deleted one by one through the routing protocol.

Therefore, if there is a corresponding table between VP and ARP entries, the processing speed will be faster, and the network device can quickly delete all ARP entries corresponding to this VP in the network protocol and notify all neighbor devices through the network protocol.

In addition, as another implementation method, the relationship between the ARP entry and the physical port can also be stored in a correspondence table (i.e., the second correspondence table referred to in this embodiment) on the network device, so that the network device can delete the ARP entry related to the failed physical port in the network device through the routing protocol based on the correspondence table between the ARP entry and the physical port.

The specific implementation is as follows:

First, based on the failed physical port, the second correspondence table is searched to obtain a target ARP entry corresponding to the failed physical port, wherein the second correspondence table includes a correspondence between the physical port of the network device and the ARP entry, and the port information of the ARP entry in the second correspondence table is virtual port information corresponding to the physical port corresponding to the ARP entry;

Then, the target ARP entries are deleted one by one through the routing protocol.

Through the above scheme, in the case of failure of the physical port of the network device, the corresponding physical port information is deleted in the pre-configured virtual port table of the network device, the virtual port table includes the correspondence between the physical port and the virtual port of the network device, and the port information in the ARP entry corresponding to the physical port is the virtual port information corresponding to the physical port corresponding to the ARP entry; at the same time, the ARP entry related to the failed physical port in the network device can be deleted according to the routing protocol. Thus, By pre-configuring a virtual port table in the ARP table entry and configuring the correspondence between the physical port and the virtual port of the network device in the virtual port table, a virtual port (VP) is used to replace the physical port in the ARP table entry. This can not only complete the one-time operation of the ARP table entry by deleting the corresponding physical port information in the ARP table entry when the physical port fails, but also achieve fast convergence of ARP entries and fast traffic cutting, improve the response speed of network devices to network abnormalities, and improve the routing convergence speed of the entire network. In addition, the traffic processing of the ARP table entry can be completed in the case of port oscillation without causing a large number of routing oscillations, thereby improving the routing performance of the entire network.

As an embodiment, the method may further include:

Step S104, when a message forwarding request is received, extracting the destination IP address carried in the message forwarding request;

Step S105, determining a corresponding ARP entry according to the destination IP address;

Step S106, determining the destination virtual port corresponding to the corresponding ARP entry;

Step S107, searching the virtual port table for a corresponding destination physical port ID based on the destination virtual port;

Step S108: when the corresponding destination physical port ID is found, the message is forwarded through the corresponding destination physical port; when the corresponding destination physical port ID is not found, the message is not forwarded.

As mentioned above, this embodiment corresponds the VP of the network device to the physical port of the network device one by one, and writes them into the VP table. When issuing ARP table entries, in the hardware of the network device, VP is used to replace the physical port to write the ARP table entry, that is, the exit path of the ARP entry is no longer written as: physical port + host MAC + vlan, but as: VP + host MAC + vlan. That is, the real physical port is no longer used to write the ARP table entry, and the VP table is written in the ARP table entry, and the correspondence between VP and physical port is configured in the VP table.

When the network device receives a message forwarding request, it extracts the destination IP address carried in the message forwarding request; and determines a corresponding ARP entry according to the destination IP address.

The egress path of the ARP entry is searched in the ARP table of the network device: VP+host MAC+vlan.

The corresponding VP is determined according to the egress path of the ARP entry.

Since the VP table corresponds to the relationship between VP and physical port, when the network device forwards the message, it finds the egress path of the message through the ARP entry. When it finds that the egress is a VP, it looks up its real physical port in the VP table, such as looking up its real physical port ID in the VP table.

As a case, when searching for the corresponding physical port ID from the VP table, if the corresponding physical port ID is found, it means that the physical port is not invalid, and the message is forwarded through the corresponding physical port, so that the real physical port is found through the above scheme to forward the message, so that when the ARP table configuration is modified, the message forwarding can still be carried out according to the original correct path.

As another case, when searching for the corresponding physical port ID in the VP table, if the corresponding physical port ID is not found, it means that the physical port has failed and the corresponding physical port information in the VP table has been deleted, and the message is not forwarded.

When a physical port fails, the network device directly deletes the corresponding physical port information in the VP table. In this way, all VPs of ARP entries related to this failed physical port will not be able to find the real physical port in the VP table. Therefore, all traffic is immediately interrupted, ARP entries cannot forward traffic, and messages cannot be forwarded.

The solution of this embodiment can be reasonably combined with the above embodiments according to actual conditions and implemented, and will not be described in detail here.

As an embodiment, before deleting the target ARP entries one by one, the method may further include:

Step S109, when the invalid physical port of the network device becomes valid again, correspondingly adding valid physical port information to the virtual port table;

In the case where it is detected that the failed physical port of the network device continues to be invalid, the step of: deleting the target ARP entries corresponding to the failed physical port one by one through the routing protocol.

When a previously invalid physical port of a network device becomes valid again, the network device may add corresponding valid physical port information to the VP table of the ARP table entry.

The embodiment of the present application can directly delete the physical port corresponding to the VP when it is invalid. If the physical port becomes valid again before the target ARP entries are deleted one by one, the valid physical port can be directly added to the VP table. Only one operation is required to make all the ARPs related to it valid again or invalid, thereby greatly reducing the consumption of CPU.

As an embodiment, the method may further include:

When the first physical port corresponding to the ARP entry is changed to a second physical port, the port information in the ARP entry is replaced with the virtual port information corresponding to the second physical port.

If the physical port information of the ARP entry's egress path changes, the VP also needs to be updated synchronously, which is similar to the general The effect of using VP is different (VP is generally used in VPN, and the export change is to directly change the export in the VP table). Here, the physical port corresponding to the VP in the VP table is not changed, but the VP in the ARP entry is changed to the VP corresponding to the new physical port, that is, the VP is updated.

According to the above scheme, it can be seen that, unlike the prior art, the routing processing scheme of the embodiment of the present application no longer needs to process the deletion of hardware ARP entries one by one when the physical port of the network device fails, nor does it need to wait for the hardware ARP entry deletion time and then notify the neighboring device through the network protocol. Instead, it only needs to operate the VP once, and all ARP entries can be deleted according to the result of this operation. The speed of this operation is no longer related to the number of ARP entries, so it can achieve the effect of fast response and fast convergence, and the actual operation result can reach a convergence speed of milliseconds.

If the port oscillates at this time, and becomes valid and invalid continuously in a short period of time, in previous technologies, a large amount of CPU consumption will occur because a large number of ARP deletion and addition operations for hardware will occur. However, the embodiment of the present application can directly delete the physical port corresponding to the VP when it fails. If the physical port is valid again, this valid physical port can be directly added to the VP table. Only one operation is required to make all related ARPs valid or invalid again, thereby greatly reducing CPU consumption.

The ARP entries in the hardware can be compared with the protocol calculation results after the network reaches a steady state, and deleted or added to achieve the same effect as the ARP entries in the protocol and hardware. The specific implementation effect can be shown in Figure 4.

The present embodiment is described in detail below with reference to FIG4 through a specific example:

The description is mainly divided into two steps.

Assuming an ARP entry exists:

10.1.1.1 Path egress: physical port port1, MAC: 00:11:22:33:44:55, vlan 100;

10.1.1.2 Path egress: physical port port1, MAC: 00:11:22:33:44:66, vlan 100;

10.1.1.3 Path exit: physical port port2, MAC: 00:11:22:33:44:77, vlan 200;

The first step is to use VP to replace the real physical port to write into the ARP table. As shown in Figure 4, the specific process is as follows:

1. The network device is assigned VP1, and VP1 corresponds to physical port port1; the network device is assigned VP2, and VP2 corresponds to physical port port2;

The entries in the VP table are as follows:

VP1->port1; VP2->port2;

2. When the protocol needs to be written into ARP 10.10.10.1, 10.10.10.2, and 10.10.10.3, the physical port port1 is found to correspond to VP1, and the physical port port2 is found to correspond to VP2. Then the VP information is written into the hardware (optionally, ARP entries 10.10.10.1, 10.10.10.2 corresponding to VP1 and ARP entry 10.10.10.3 corresponding to VP2 are formed in the software). Finally, the ARP entries written into the hardware are:

10.1.1.1 path egress: VP1, MAC: 00:11:22:33:44:55, vlan 100;

10.1.1.2 Path egress: VP1, MAC: 00:11:22:33:44:66, vlan 100;

10.1.1.3 Path egress: VP2, MAC: 00:11:22:33:44:77, vlan 200;

3. At this time, the ARP entry of 10.1.1.3 changes and is transferred to port1. At this time, the network device finds the corresponding VP of port1 as VP1, and directly modifies the relevant fields of the ARP table. Finally, the entry of 10.1.1.3 written into the ARP table becomes (optionally, modify the corresponding table of software VP and ARP):

10.1.1.3 Path egress: VP1, MAC: 00:11:22:33:44:77, vlan 100;

In the second step, the physical port fails:

1. At this time, the ARP entries in the hardware are as follows:

10.1.1.1 path egress: VP1, MAC: 00:11:22:33:44:55, vlan 100;

10.1.1.2 Path egress: VP1, MAC: 00:11:22:33:44:66, vlan 100;

10.1.1.3 Path egress: VP1, MAC: 00:11:22:33:44:77, vlan 100;

2. If the physical port port1 fails and the ARP entry needs to be quickly converged, the value of VP1 in the VP table will be deleted, that is, the port field corresponding to VP1 will be empty:

That is, the field in the VP table becomes: VP1->NULL (not pointing to any port).

3. At this time, the ARP table in the hardware has not been processed and is still:

10.1.1.1 path egress: VP1, MAC: 00:11:22:33:44:55, vlan 100;

10.1.1.2 Path egress: VP1, MAC: 00:11:22:33:44:66, vlan 100;

10.1.1.3 Path egress: VP1, MAC: 00:11:22:33:44:77, vlan 100;

However, since the VP1 field is empty, all packets that hit this ARP will be directly discarded and cannot be forwarded.

At this point, the CPU senses that port 1 has failed, and immediately searches for all ARP entries related to port 1 in the software, and notifies neighboring devices through the routing protocol that all of their own ARP entries have been revoked.

As an implementation method, if a corresponding table of ARP and VP is created when ARP is created, VP1 can be found through port1, and all ARP entries related to it can be quickly indexed through VP1 for rapid revocation;

As an implementation mode, if the neighboring device supports creating routes through the VP notified by the network device, the failure of VP1 can be directly notified to the neighboring device, and the neighboring device will revoke all routes related to VP1 at one time.

Since the ARP entries in the hardware are not deleted immediately at this time, after the protocol completes the notification and sends the hardware to delete the ARP entries, these ARP entries can continue to be deleted synchronously with the protocol (since the action of quickly cutting off the traffic has been completed, the subsequent deletion of ARP synchronized by the hardware and protocol will not affect the speed of ARP fast convergence).

If the fault of port1 has been restored before ARP is deleted (that is, the port has experienced an oscillation), the correspondence between VP and port1 can be directly restored without taking any other actions, and all ARP traffic recovery can be completed at one time. Since the protocol side will accumulate one ARP deletion and one ARP addition, the device will no longer be processed for ARP deletion and addition, and no notification will be made to neighboring devices. The processing of such situations in this application can quickly respond to the oscillation of the physical port and cut off ARP traffic without generating a large number of routing announcements.

It can be seen that by using VP to replace the physical port to write into the ARP table, it is possible to complete a one-time operation on the ARP table when the physical port fails, achieving rapid convergence of the ARP table and rapid traffic cutoff. It is also possible to complete the traffic processing of the ARP table in the case of port oscillation without causing a large number of routing oscillations. It is a very efficient and simple ARP processing method when the port fails.

The routing processing method in the above example, in addition to the currently available VP solution, if there are other table entries similar to VP in the chip that can bind ports and can find ports during forwarding, they can also be used for processing in a similar manner to this method and also fall within the protection scope of the present application solution.

The application environment of this application is mainly used in the scenario where the switch or router needs to quickly converge and respond to the change of the physical port in the ARP entry, and is mainly used in the scenarios of MCLAG switching, core network connection, etc. The actual networking usage scenario is shown in Figure 5.

Refer to Figure 5, which is a schematic diagram of an actual networking application scenario of an embodiment of the present application.

As shown in FIG5 , the actual networking application scenario includes: router G, switch A, switch B, and servers C1, server C2, server C3, and server C4.

Router G learns the 32-bit mask routes of downstream servers C1, C2, C3, and C4 respectively. Router G learns the routes of downstream servers C1 and C2 pointing to switch A, and learns the routes of downstream servers C3 and C4 pointing to switch B.

On the server side, a main link and a backup link are configured. In Figure 5, the main link of server C1 is A1, and the backup link is B1; the main link of server C2 is A2, and the backup link is B2; the main link of server C3 is B3, and the backup link is A3; the main link of server C4 is B4, and the backup link is A4, as shown by the arrows in Figure 5.

At this time, switch B4 fails, and all ARP entries related to B4 need to be quickly converged, and router G should be notified immediately to withdraw related routes.

On the server side, the primary link of server C4 is B4, and the backup link is A4. If a failure occurs between server C4 and the primary link B4, server C4 switches to the backup link A4.

After the relevant routes of router G are withdrawn, router G re-learns the downstream server C4 route pointing to switch A.

From the above, we can see that the speed at which switch B's ARP entries are revoked directly affects the overall traffic switching speed.

In actual application scenarios, combined with the solution of the embodiments of the present application, very good effects will be produced in the MCLAG network fast switching, especially in the overall fast switching (S-MLAG) mode of MCLAG networking, it plays a very important role, because this mode requires all ARPs of the virtual machine to be notified to the router gateway, so it is necessary to quickly revoke all ARP table entries when the port is abnormal, and the solution of the embodiments of the present application can meet the needs of the above-mentioned scenarios where ARP entry convergence needs to be quickly completed.

As shown in FIG6 , an embodiment of the present application provides a routing device, including:

A deletion module is used to delete the corresponding physical port information in a pre-configured virtual port table of the network device when a physical port of the network device fails. The virtual port table includes the correspondence between the physical port and the virtual port of the network device. The port information in the ARP entry corresponding to the physical port is the virtual port information corresponding to the physical port corresponding to the ARP entry.

For the principle and implementation process of message forwarding implemented in this embodiment, please refer to the above embodiments and will not be repeated here.

As shown in Figure 7, an embodiment of the present application also proposes a communication device, which includes a memory, a processor, and a message forwarding program stored in the memory and executable on the processor, and when the message forwarding program is executed by the processor, it implements the message forwarding method described in the above embodiments.

The communication device may be a network device, such as a switch or a router. As shown in FIG. 7 , the communication device may include an output module 110 , a processor 120 , a memory 130 , and a communication module 140 .

The memory 130 stores a message forwarding program. The communication module 140 may include a WIFI module, a mobile communication module, a Bluetooth module, etc., and communicates with an external device or a server through the communication module 140.

When the message forwarding program in the memory 130 is executed by the processor, the message forwarding method as described in the above embodiments can be implemented.

Since all the technical solutions of all the aforementioned embodiments are adopted when the message forwarding program is executed by the processor, it has at least all the beneficial effects brought by all the technical solutions of all the aforementioned embodiments, which will not be described one by one here.

In addition, an embodiment of the present application further proposes a computer-readable storage medium, on which a message forwarding program is stored. When the message forwarding program is executed by a processor, the message forwarding method described in the above embodiments is implemented.

Compared with the prior art, the embodiment of the present application uses a virtual port (VP) to replace the physical port in the ARP table entry through the above technical solution, which can not only complete the one-time operation of the ARP table entry when the physical port fails, achieve the rapid convergence of the ARP entry and the rapid flow cutoff, but also complete the flow processing of the ARP table entry in the case of port oscillation without causing a large number of routing oscillations. It is a very efficient and simple ARP processing method when the port fails. Therefore, the use of this method can improve the response speed of network equipment to network abnormalities, improve the routing convergence speed of the entire network, and improve the routing performance of the entire network.

In this document, the terms "comprises", "includes" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system that includes a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of more restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or system that includes the element.

The serial numbers of the embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, disk, CD) as above, including a number of instructions for a communication device (which can be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the method of each embodiment of the present application.

The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

A message forwarding method, applied to a network device, comprising:

In the event that a physical port of a network device fails, the corresponding physical port information is deleted from a pre-configured virtual port table of the network device, wherein the virtual port table includes a correspondence between the physical port and the virtual port of the network device, and the port information in the ARP entry corresponding to the physical port is the virtual port information corresponding to the physical port corresponding to the ARP entry.
The method according to claim 1, before deleting the corresponding physical port information in the pre-configured virtual port table of the network device, further comprises:

Generate a first correspondence table, the first correspondence table is used to represent the correspondence between the virtual port corresponding to the physical port of the network device and the ARP entry of the physical port, the port information of the ARP entry in the first correspondence table is the virtual port information corresponding to the physical port corresponding to the ARP entry; and/or

A second correspondence table is generated, where the second correspondence table is used to characterize the correspondence between the physical port of the network device and the ARP entry, and the port information of the ARP entry in the second correspondence table is the virtual port information corresponding to the physical port corresponding to the ARP entry.
The method according to claim 2, further comprising:

Searching the virtual port table based on the failed physical port to obtain the corresponding target virtual port;

Searching the first correspondence table based on the target virtual port to obtain a target ARP entry corresponding to the target virtual port;

The target ARP entry is notified to the neighboring device of the network device through a routing protocol, so that the neighboring device deletes the corresponding target ARP entry.
The method according to claim 2, further comprising:

Searching the second correspondence table based on the failed physical port to obtain a target ARP entry corresponding to the failed physical port;

The target ARP entry is notified to the neighboring device of the network device through a routing protocol, so that the neighboring device deletes the corresponding target ARP entry.
The method according to claim 2, further comprising:

Searching the virtual port table based on the failed physical port to obtain the corresponding target virtual port;

A routing notification of invalidation of the target virtual port is sent to a neighbor device of the network device through a routing protocol, so that the neighbor device deletes all target ARP entries corresponding to the target virtual port according to the first corresponding relationship table obtained from the network device.
The method according to claim 2, further comprising:

Searching the virtual port table based on the failed physical port to obtain the corresponding target virtual port, searching the first correspondence table based on the target virtual port to obtain the target ARP entry corresponding to the target virtual port; or searching the second correspondence table based on the failed physical port to obtain the target ARP entry corresponding to the failed physical port;

The target ARP entries are deleted one by one through the routing protocol.
The method according to claim 1, before deleting the corresponding physical port information in the pre-configured virtual port table of the network device, further comprises:

Creating a virtual port table for characterizing the correspondence between virtual ports and physical ports;

The physical port information in the ARP entry of the physical port corresponding to the virtual port is replaced with the virtual port information corresponding to the physical port.
According to the method of claim 6, the physical port information includes a physical port ID, and the method further includes:

When receiving a message forwarding request, extracting the destination IP address carried in the message forwarding request;

Determine a corresponding ARP entry according to the destination IP address;

Determine the destination virtual port corresponding to the corresponding ARP entry;

Searching the corresponding destination physical port ID from the virtual port table based on the destination virtual port;

When the corresponding destination physical port ID is found, forward the message through the corresponding destination physical port;

If the corresponding destination physical port ID is not found, the message is not forwarded.
According to the method of claim 6, before the step of deleting the target ARP entries one by one through the routing protocol, the method further comprises:

When the invalid physical port of the network device becomes valid again, correspondingly add valid physical port information to the virtual port table;

In the case where it is detected that the failed physical port of the network device continues to be invalid, the step of: deleting the target ARP entries one by one through a routing protocol is performed.
According to the method of claim 1, the ARP entry includes: an IP address, a host MAC address, virtual port information, and a VLAN.
The method according to claim 10, further comprising:

When the first physical port corresponding to the ARP entry is changed to a second physical port, the port information in the ARP entry is replaced with the virtual port information corresponding to the second physical port.
A communication device, wherein the communication device includes a memory, a processor, and a message forwarding program stored in the memory and executable on the processor, wherein the message forwarding program, when executed by the processor, implements the message forwarding method as described in any one of claims 1 to 11.
A computer-readable storage medium, wherein a message forwarding program is stored on the computer-readable storage medium, and when the message forwarding program is executed by a processor, the message forwarding method according to any one of claims 1 to 11 is implemented.