CN114401324A - Message forwarding method, network equipment and system - Google Patents

Message forwarding method, network equipment and system Download PDF

Info

Publication number
CN114401324A
CN114401324A CN202111668873.6A CN202111668873A CN114401324A CN 114401324 A CN114401324 A CN 114401324A CN 202111668873 A CN202111668873 A CN 202111668873A CN 114401324 A CN114401324 A CN 114401324A
Authority
CN
China
Prior art keywords
loop
erps
network device
mac address
destination mac
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202111668873.6A
Other languages
Chinese (zh)
Other versions
CN114401324B (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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202111668873.6A priority Critical patent/CN114401324B/en
Publication of CN114401324A publication Critical patent/CN114401324A/en
Application granted granted Critical
Publication of CN114401324B publication Critical patent/CN114401324B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08Protocols for interworking; Protocol conversion

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

The application discloses a message forwarding method, network equipment and a system. In this embodiment of the present application, a first network device receives a first packet sent by a second network device belonging to the same ERPS loop. When the first network device determines that the first destination MAC address in the first message is different from the destination MAC address corresponding to the loop identifier of the ERPS loop, it is described that the version of the ERPS protocol supported by the second network device is different from the version of the ERPS protocol supported by the first network device, and the second network device can only identify the message including the first destination MAC address. And the first network equipment sends a second message comprising the first destination MAC address to the network equipment included in the ERPS loop. The second network device is capable of processing a second packet including the first destination MAC address sent by the first network device. In this way, normal communication between the first network device and the second network device supporting different protocol versions in the same ERPS loop can be realized.

Description

Message forwarding method, network equipment and system
Technical Field
The present application relates to the field of communications, and in particular, to a method, a network device, and a system for forwarding a packet.
Background
In an ethernet switching network, redundant links are usually used to implement link backup, thereby improving the reliability of the network. However, the redundant link may generate a loop on the network, which may cause problems such as a broadcast storm and unstable Media Access Control (MAC) address table, and affect the communication quality.
Currently, Ethernet Ring Protection Switching (ERPS) technology is used to avoid the generation of loops in the Ethernet link layer of the network. The basic unit of the ERPS protocol (g.8032 protocol) is an ERPS loop. The ERPS loop is constituted by network devices.
The network equipment in the ERPS loop transmits port information by using an ERPS protocol message. The ERPS protocol message includes the destination MAC address. The network equipment judges whether the ERPS protocol message is sent by the network equipment in the ERPS loop or not based on the destination MAC address in the ERPS protocol message. However, the destination MAC address defined in the different versions of the ERPS protocol is different. When the same ERPS loop includes network devices supporting different versions of the ERPS protocol, the destination MAC address of the packet transmitted in the same ERPS loop may have various forms. This may cause the network devices in the ERPS loop to determine that the packet is not sent by the network devices in the same ERPS loop, which affects normal processing of the packet by the network devices, and causes the network devices in the same ERPS loop to fail to communicate normally. Therefore, how to implement the interworking between network devices supporting different versions of g.8032 protocol in the same ERPS loop is a problem to be solved.
Disclosure of Invention
The application provides a message forwarding method, network equipment and a system, which can realize normal communication between the network equipment supporting different protocol versions in the same ERPS loop.
In a first aspect, the present application provides a method for forwarding a packet, where the method may be applied to an ERPS loop. When the message forwarding method provided by the application is executed, a first network device in the ERPS loop receives a first message sent by a second network device in the ERPS loop. The first message comprises a first destination MAC address. The first network device can determine that the first destination MAC address is different from a destination MAC address corresponding to the ERPS loop. This means that the ERPS loop includes a network device, such as the second network device, capable of processing the packet including the first destination MAC address. The destination MAC addresses included in the packets that can be normally processed by the second network device and the first network device may be different, that is, the ERPS protocols supported by the second network device and the first network device may be different. And the first network equipment sends a second message to the network equipment included in the ERPS loop. Wherein the second message is a message including the first destination MAC address. The ERPS loop includes a network device capable of processing a packet including the first destination MAC address, and is capable of processing a second packet including the first destination MAC address. Based on the second packet including the first destination MAC address, communication between the first network device and a network device included in the ERPS loop, such as the second network device, capable of processing the packet including the first destination MAC address can be achieved. Therefore, the interworking between the network devices supporting different versions of ERPS protocols in the same ERPS loop can be realized.
In some possible implementations, the first network device may obtain a destination MAC address corresponding to the ERPS loop, i.e., the second destination MAC address. The first network device can determine that the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop by determining that the first destination MAC address is different from the second destination MAC address.
As an example, there is a correspondence between the second destination MAC address and the loop identification of the ERPS loop, i.e. the first correspondence. The first network device may obtain the loop identifier of the ERPS loop, and obtain the second destination MAC address based on the loop identifier of the ERPS loop and the first corresponding relationship.
As another example, the second destination MAC address includes an ERPS loop identification. The first network device can obtain the ERPS loop identification. Based on the obtained ERPS loop identification, the first network device obtains a second destination MAC address including the ERPS loop identification.
In some possible implementations, the destination MAC address corresponding to the ERPS loop may include a loop identification of the ERPS loop. The first network device can acquire the loop identifier of the ERPS loop, and determine that the first destination MAC address does not include the loop identifier of the ERPS loop according to the acquired loop identifier of the ERPS loop and the first destination MAC address. In this way, it can be determined that the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop.
In some possible implementations, the identifier of the VLAN has a correspondence with a loop identifier of the ERPS loop, that is, a second correspondence. The first network device can obtain the loop identifier of the ERPS loop based on the identifier of the VLAN included in the first packet and the second correspondence.
In some possible implementations, the first network device can obtain the loop identifier of the ERPS loop according to the ERPS loop to which the first network device belongs.
In some possible implementations, the first network device can obtain the loop identifier of the ERPS loop according to the VLAN to which the first network device belongs.
In some possible implementations, the network devices included in the ERPS loop in which the first network device is located can all normally process the destination MAC address corresponding to the ERPS loop. In this case, the first network device can send the third packet to the network device of the ERPS loop. The third message includes a destination MAC address corresponding to the ERPS loop. And the third message is sent by the first network equipment, so that the destination MAC address of the message transmitted in the ERPS loop can be flexibly adjusted based on the version of the ERPS protocol supported by the network equipment in the ERPS loop, and the normal communication between the network equipment in the ERPS loop is realized.
In some possible implementations, the third message may be an NR-RB message. The destination MAC address corresponding to the ERPS loop and included in the NR-RB message comprises a loop identification of the ERPS loop.
In a second aspect, the present application provides a network device, which is applied to a first network device belonging to an ERPS loop. The network device includes: the device comprises a receiving unit, a processing unit and a first sending unit. The receiving unit is configured to receive a first packet sent by a second network device included in the ERPS loop. The first message includes a first destination media access control, MAC, address. And the processing unit is used for determining that the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop. And the first sending unit is used for sending the second message to the network equipment included in the ERPS loop. The second message includes the first destination MAC address.
In some possible implementations, the processing unit is configured to obtain a second destination MAC address, and determine that the first destination MAC address is different from the second destination MAC address. Wherein the second destination MAC address is a destination MAC address corresponding to the ERPS loop.
In some possible implementations, the processing unit obtaining the second destination MAC address includes: the processing unit obtains a loop identifier of the ERPS loop, and obtains the second destination MAC address according to a first corresponding relationship and the loop identifier of the ERPS loop, wherein the first corresponding relationship comprises the second destination MAC address and the loop identifier of the ERPS loop.
In some possible implementations, the processing unit obtaining the second destination MAC address includes: and the processing unit acquires the loop identifier of the ERPS loop, and acquires the second destination MAC address according to the loop identifier of the ERPS loop, wherein the second destination MAC address comprises the loop identifier of the ERPS loop.
In some possible implementations, the processing unit is configured to obtain a loop identifier of the ERPS loop, and determine, based on the first destination MAC address and the loop identifier of the ERPS loop, that the first destination MAC address does not include the loop identifier of the ERPS loop.
In some possible implementations, the first packet further includes an identifier of a virtual local area network VLAN, and the acquiring, by the processing unit, the loop identifier of the ERPS loop includes: and the processing unit acquires the loop identifier of the ERPS loop based on a second corresponding relation and the identifier of the VLAN, wherein the second corresponding relation comprises the identifier of the VLAN and the loop identifier of the ERPS loop.
In some possible implementations, the processing unit obtains a loop identifier of the ERPS loop, including: the processing unit acquires a loop identifier of an ERPS loop based on the ERPS loop to which the first network equipment belongs;
or, the processing unit obtains the loop identifier of the ERPS loop based on the VLAN to which the first network device belongs.
In some possible implementations, the network device further includes: and a second transmitting unit. A second sending unit, configured to send a third packet to the network device of the ERPS loop. And the third message comprises a destination MAC address corresponding to the ERPS loop.
In some possible implementations, the third message is a no request-eco link blocking NR-RB message. The destination MAC address corresponding to the ERPS loop comprises the loop identification of the ERPS loop.
In a third aspect, the present application provides a network device, where the network device includes a processor chip and a memory, where the memory is used to store instructions or program codes, and the processor chip is used to call and execute the instructions or the program codes from the memory, so as to execute the packet forwarding method described in the first aspect or any one of the possible implementations of the first aspect.
In a fourth aspect, the present application provides a network system, where the network system includes a first network device and a second network device, and the first network device and the second network device belong to an ERPS loop.
The second network device is configured to send a first packet to a first network device, where the first packet includes a first destination MAC address;
the first network device receives the first message sent by a second network device, determines that the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop, and sends a second message to other network devices included in the ERPS loop, wherein the second message includes the first destination MAC address.
In a fifth aspect, a system for forwarding a packet is provided, where the system includes a first network device and a second network device that belong to an ERPS loop, where the first network device is the network device provided in the third aspect.
In a sixth aspect, the present application provides a computer-readable storage medium, which is characterized by instructions, programs, or codes, and when executed on a computer, the instructions, the programs, or the codes cause the computer to execute the packet forwarding method described in the first aspect or any one of the possible implementations of the first aspect.
In a seventh aspect, the present application provides a computer program product, which when run on a network device, causes the network device to execute the packet forwarding method described in the first aspect or any one of the possible implementations of the first aspect.
Drawings
FIG. 1 is a schematic diagram of an ERPS loop;
FIG. 2 is a schematic diagram of another ERPS loop provided by an embodiment of the present application;
fig. 3 is a schematic flowchart of a message forwarding method 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;
fig. 5 is a schematic structural diagram of a message forwarding system provided in the embodiment of the present application;
FIG. 6 is a schematic structural diagram of an apparatus provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of an apparatus provided in an embodiment of the present application.
Detailed Description
For a better understanding of the present disclosure, embodiments of the present disclosure will be described in further detail below with reference to the accompanying drawings and embodiments.
The ERPS protocol is a standard ring network protocol special for an Ethernet link layer, and has the standard number of International telecommunication standardization sector (ITU-T) G.8032/Y1344, which is also called as G.8032 protocol. The g.8032 protocol uses the ERPS loop as a basic unit. One ERPS loop corresponds to one ring connected ethernet topology. An ERPS loop comprises at least two network devices, and each network device can only have two ports to access the same ERPS loop. A Ring Protection Link (RPL) may be used between network devices in the ERPS loop. There is a master node in the ERPS loop. The master node is a decision and control node on the ERPS loop that controls blocking and unblocking ports on the master node that are located on RPL, i.e., RPL owner, to prevent the loop from forming. Referring to fig. 1, a schematic diagram of an ERPS loop is shown. The ERPS loop includes four network devices, which are network device 101, network device 102, network device 103, and network device 104. Each network device has two ports to access the ERPS ring. Wherein, the link between the network device 101 and the network device 102 is RPL. The network device 101 is a master node and is configured to control the state of ports of the RPL on the master node. When the ERPS loop normally operates, the main node controls the RPL owner port to be in a blocking state, and the ERPS loop is eliminated. When the link except the RPL in the ERPS loop breaks down, the main node controls the RPL owner port to be opened, so that the flow is transmitted through the RPL, and the communication between the network devices in the EPRS loop is recovered.
And the network equipment in the ERPS loop transmits information through messages. The destination MAC address in the message is determined by the ERPS loop to which the network device belongs. Each network device in the ERPS loop stores a destination MAC address and sends a message carrying the destination MAC address. After the network equipment in the ERPS loop acquires the message, whether the message is from the network equipment belonging to the same ERPS loop is determined by judging whether the destination MAC address in the message is the same as the destination MAC address stored by the network equipment. If the destination MAC address in the message is the same as the destination MAC address stored by the network equipment, the network equipment determines that the message is from the network equipment belonging to the same ERPS loop, and processes the message. If the destination MAC address in the message is different from the destination MAC address stored by the network equipment, the network equipment determines that the message is not from the network equipment belonging to the same ERPS loop, and does not process the message.
The destination MAC address defined by g.8032-200806(g.8032v1) is a fixed value. Taking the ERPS loop in fig. 1 as an example, the network device 101-the network device 104 included in the ERPS loop both support g.8032-200806. The destination MAC address that network device 101-network device 104 can recognize is a fixed value. Wherein the destination MAC address may be 0119-a 700-0001. Network device 101-network device 104 store destination MAC addresses of 0119-a 700-0001. And, network device 101-network device 104 send the packet including 0119-a700-0001 to network devices in the same ERPS loop. After receiving the message, the network device 101-network device 104 may identify whether the destination MAC address carried in the message is 0119-a 700-0001. If the destination MAC address included in the received packet is 0119-a700-0001, then network device 101-network device 104 can confirm that the packet is sent by a network device included in the same ERPS loop, and process the packet. If the destination MAC address carried by the packet is not 0119-a700-0001, then network device 101-network device 104 can confirm that the packet is not sent by network devices included in the same ERPS loop, and do not process the packet. G.8032-201003(g.8032v2) extends the format of the destination MAC address. The extended destination MAC address may include a loop (Ring) Identification (ID). For example, the destination MAC address is 0119-a700-00[ Ring ID ]. The Ring ID is the Ring identification of the ERPS to which the network equipment belongs. Wherein the loop identification is used to distinguish between different ERPS loops. Taking the ERPS loop in fig. 1 as an example, assume that the loop identifier of the ERPS loop is 02. Network device 101-network device 104 store destination MAC addresses 0119-a 700-0002. And, network device 101-network device 104 send messages including 0119-a700-0002 to network devices in the same ERPS loop. After receiving the message, the network device 101-network device 104 may identify whether the destination MAC address carried in the message is 0119-a 700-0002. If the destination MAC address carried by the received packet is 0119-a700-0002, then network device 101-network device 104 can confirm that the packet is sent by network devices included in the same ERPS loop, and process the packet. If the destination MAC address carried in the packet is not 0119-a700-0002, the network device 101-network device 104 determines that the packet is not sent by a network device included in the same ERPS loop, and does not process the packet.
In some possible scenarios, such as in a network device upgrade scenario, or a scenario of networking network devices of different enterprises, network devices that form the same ERPS loop may support different versions of the g.8032 protocol. That is, the destination MAC addresses that can be recognized by network devices included in the same ERPS loop are different.
It can be seen that the network device can only identify the destination MAC address defined by the supported g.8032 protocol version, but cannot identify the destination MAC address defined by the unsupported g.8032 protocol version. When network devices supporting different g.8032 protocol versions are included in the same ERPS loop, the ERPS loop may transmit a packet including destination MAC addresses defined by multiple g.8032 protocol versions. This may cause that the network devices in the ERPS loop may not normally process the packet sent by the network devices in the same ERPS loop, and affect the communication between the network devices in the same ERPS loop.
In view of the foregoing problems, an embodiment of the present application provides a message forwarding method. In this embodiment of the present application, a first network device receives a first packet sent by a second network device belonging to the same ERPS loop. When the first network device determines that the first destination MAC address in the first message is different from the destination MAC address corresponding to the loop identifier of the ERPS loop, it is described that the version of the ERPS protocol supported by the second network device is different from the version of the ERPS protocol supported by the first network device, and the second network device can only identify the message including the first destination MAC address. And the first network equipment sends a second message comprising the first destination MAC address to the network equipment included in the ERPS loop. The second network device is capable of processing a second packet including the first destination MAC address sent by the first network device. Therefore, the first network device can process the target MAC address defined by the version of the unsupported ERPS protocol, normal communication between the first network device and the second network device supporting the ERPS protocols of different versions in the same ERPS loop is realized, and compatibility of different ERPS protocol versions is realized.
The message forwarding method provided by the embodiment of the application is applied to an ERPS loop. With reference to fig. 2, an application scenario of the message forwarding method provided in the embodiment of the present application is first introduced. Referring to fig. 2, a schematic diagram of another ERPS loop provided in the embodiment of the present application is shown. Therein, network device 201, network device 202, network device 203, and network device 204 form an ERPS loop 210. The network device 201-the network device 204 may be, for example, a router, a switch, or other network devices with a message forwarding function. The destination MAC addresses that can be recognized by the network device 201 and the network device 202 are different from the destination MAC addresses that can be recognized by the network device 203 and the network device 204. For example, network device 201 and network device 202 may be g.8032-201003-enabled network devices capable of recognizing destination MAC addresses defined by g.8032-201003. Network device 203 and network device 204 may be g.8032-200806 enabled network devices capable of recognizing destination MAC addresses defined by g.8032-200806. Taking the ring identifier of the ERPS ring as 02 as an example, the network device 201 and the network device 202 can send messages with destination MAC addresses of 0119-a700-0002, and can recognize messages including 0119-a 700-0002. Network device 203 and network device 204 can send messages with destination MAC addresses of 0119-a700-0001 and can identify messages that include 0119-a 700-0001. Network device 201 and network device 202 may send messages including 0119-a700-0002 to network devices in the ERPS loop. Network device 203 and network device 204 may send messages comprising 0119-a700-0001 to network devices in the ERPS loop.
A detailed description is given below of a message forwarding method provided in an embodiment of the present application with reference to the accompanying drawings. Referring to fig. 3, the figure is a schematic flow chart of a message forwarding method provided in the embodiment of the present application, and includes S301 to S303.
S301, the first network equipment receives a first message sent by the second network equipment.
The first network device and the second network device belong to the same ERPS loop. Wherein the first network device may be directly connected with the second network device. For example, as shown in connection with fig. 2, the first network device may be, for example, network device 201, and the second network device may be, for example, network device 203. The first network device may also be indirectly connected to the second network device. For example, as shown in connection with fig. 2, the first network device may be network device 201 and the second network device may be network device 204. The first network equipment acquires a first message sent by the second network equipment. When the first network device is indirectly connected to the second network device, other network devices in the ERPS loop may obtain the first packet sent by the second network device, and forward the first packet to the first network device. The first packet acquired by the first network device may be an ERPS protocol packet. The first message includes a first destination MAC address. The first destination MAC address is determined based on a version of an ERPS protocol supported by the second network device. As an example, when the second network device is a g.8032-200806-enabled network device, the first destination MAC address is 0119-a 700-0001.
S302: the first network device determines that the first destination MAC address is different from a destination MAC address corresponding to the ERPS loop.
The first network device obtains a destination MAC address corresponding to the ERPS loop. Wherein the ERPS loop is an ERPS loop to which the first network device and the second network device belong together. The first network device acquires a first destination MAC address in the first message, and compares the first destination MAC address with a destination MAC address corresponding to the ERPS loop. The embodiment of the present application provides two possible specific implementations for comparing the first destination MAC address with the destination MAC address corresponding to the ERPS loop.
The first method comprises the following steps: the second destination MAC address is the destination MAC address corresponding to the ERPS loop. The first network device obtains the second destination MAC address and compares the first destination MAC address with the second destination MAC address. The second destination MAC address may be associated with a loop identification of the ERPS loop. The first network device is capable of obtaining the second destination MAC address based on the loop identification of the ERPS loop. Wherein the loop identification is used to identify the ERPS loop. Each ERPS loop has a corresponding loop identification. The loop identification of the ERPS loop may be configured in the process of establishing the ERPS loop. The loop identification may be a positive integer.
Three possible methods of obtaining the loop id are described below.
The method comprises the following steps: and the first network equipment acquires the loop identification of the ERPS loop based on the ERPS loop to which the first network equipment belongs. After acquiring the first message sent by the second network device, the first network device can determine an ERPS loop to which the first network device and the second network device belong together. The first network equipment acquires the loop identification of the ERPS loop according to the ERPS loop to which the first network equipment and the second network equipment belong together. In one possible implementation, when the first network device belongs to only one ERPS loop, the first network device can determine the ERPS loop to which the first network device belongs. In another possible implementation, the first network device may belong to multiple ERPS loops. The first network device may determine, based on the ERPS loop to which the port that acquires the first packet belongs, an ERPS loop to which the first network device and the second network device belong together. In another possible implementation manner, the first message may carry a Virtual Local Area Network (VLAN) identifier ID. The first network device may determine, based on the VLAN ID, an ERPS loop to which the first network device and the second network device belong in common. Specifically, in the same ERPS loop, it is also possible to transmit traffic of multiple VLANs at the same time. In order to distinguish traffic belonging to different VLANs, multiple ERPS instances may be configured in the ERPS loop, with different ERPS instances transporting traffic of different VLANs. Different ERPS instances have corresponding control VLANs. The control VLAN is used for transmitting ERPS protocol messages. The VLAN ID is used to identify the control VLAN. The VLAN ID may be determined by configuration information. The first network device may pre-store a correspondence relationship between the VLAN ID and the ERPS loop. After the first network device obtains the VLAN ID carried by the first packet, the ERPS loop to which the first network device and the second network device belong together can be determined based on the VLAN ID carried by the first packet and the correspondence between the VLAN ID and the ERPS loop. The first network device may pre-store a loop identification of the ERPS loop. And after determining the ERPS loop, acquiring the loop identification of the ERPS loop. In one possible implementation, the first network device may obtain the loop identifier of the ERPS loop in advance based on the configuration instruction. For example, when the first network device is a master node in an ERPS loop, the loop identifier of the ERPS loop may be acquired based on the configuration instruction. In another possible implementation, the first network device may also obtain the loop identifier of the ERPS loop in advance based on the ERPS protocol packet. The first network device may be a network device supporting the g.8032-201003 protocol. The destination MAC address in the ERPS protocol message is 0119-a700-00[ Ring ID ]. The first network equipment acquires the ERPS protocol messages sent by other network equipment in the ERPS loop, and can determine the loop identification of the ERPS loop according to the destination MAC address carried by the ERPS protocol messages. The ERPS protocol packet sent by the other network device may specifically be an ERPS protocol packet of No Request-No protection link blocking (No Request-RPL Block, NR-RB) type. The NR-RB type ERPS protocol packet may be sent by the master node in the ERPS loop to other network devices, and is used to notify the other network devices that the RPL port is blocked. After acquiring the ERPS protocol message of the NR-RB type, the first network device releases the fault-free port of the first network device, and can update the MAC address table item and determine the loop identification of the ERPS loop based on the target MAC address of the ERPS protocol message of the NR-RB type. For example, when the first network device acquires the ERPS protocol packet of the NR-RB type, the loop identifier of the ERPS loop may be determined to be 02 according to the destination MAC address of 0119-a700-0002 in the ERPS protocol packet of the NR-RB type.
The second method comprises the following steps: and the first network equipment acquires the loop identification of the ERPS loop according to the VLAN to which the first network equipment belongs. The first network device has a VLAN to which it belongs. In this VLAN, the first network device belongs to an ERPS loop. The first network device may obtain the loop identifier of the ERPS loop based on the VLAN to which the first network device belongs. In one possible implementation, the port of the first network device may be configured to transmit only messages of a particular VLAN. The first network device may determine a VLAN to which it belongs based on the port on which the first packet is transmitted. The first network device may establish a correspondence between the VLAN and the loop identifier of the ERPS loop in advance based on the loop identifier of the ERPS loop to which the VLAN belongs. After the first message is obtained and the VLAN to which the first network device belongs is determined, the loop identifier of the ERPS loop is obtained based on the VLAN to which the first message belongs and the corresponding relationship between the VLAN and the loop identifier of the ERPS loop.
The third method comprises the following steps: and the first network equipment acquires the loop identification of the ERPS loop according to the VLAN ID carried by the first message and the second corresponding relation. The second correspondence is a correspondence between the VLAN ID and the loop identification of the ERPS loop. The first network device can obtain the loop identifier of the ERPS loop based on the VLAN ID carried by the first message and the second corresponding relation. The second correspondence may be established by the first network device based on the correspondence between the VLAN ID and the ERPS loop, and the loop identifier of the ERPS loop. The first network device may store the second correspondence in advance. And after the first network equipment acquires the first message, acquiring a loop identifier of the ERPS loop according to the VLAN ID carried by the first message and the stored second corresponding relation.
Based on the above three methods, the first network device can obtain the loop identifier of the ERPS loop. After obtaining the loop identifier of the ERPS loop, the first network device may obtain the second destination MAC address according to the loop identifier of the ERPS loop.
Two possible ways of obtaining the second destination MAC address based on the loop identification of the ERPS loop are provided below.
The first method is as follows: and the first network equipment acquires the second destination MAC address according to the first corresponding relation and the loop identifier of the ERPS loop. Wherein the first corresponding relationship comprises the corresponding relationship between the second destination MAC address and the loop identifier of the ERPS loop. The first correspondence may be established in advance based on the configuration instruction. The first corresponding relationship may also be established by the first network device based on the corresponding relationship between the ERPS loop and the loop identifier, and the corresponding relationship between the ERPS loop and the second destination MAC address. After acquiring the loop identifier of the ERPS loop, the first network device may acquire the second destination MAC address according to the ERPS loop identifier and the first corresponding relationship.
The second method comprises the following steps: and the first network equipment acquires the second destination MAC address according to the loop identifier. The second destination MAC address may include a loop identification. The first network device may generate the second destination MAC address based on the loop identifier, so as to obtain the second destination MAC address. Taking the g.8032-201003 protocol as an example, the second destination MAC address may be 0119-a700-00[ Ring ID ]. The first network device may generate the second destination MAC address according to the acquired loop identification. For example, if the loop id obtained by the first network device is 02, the second destination MAC address may be generated. Wherein the second destination MAC address is 0119-a 700-0002.
The method judges whether the first destination MAC address is the same as the destination MAC address corresponding to the ERPS loop based on the acquired second destination MAC address. Another method of determining whether the first destination MAC address is the same as the destination MAC address corresponding to the ERPS loop is described below.
And the second method comprises the following steps: the first network device may determine whether the first destination MAC address is the same as a destination MAC address corresponding to the ERPS loop by determining whether the first destination MAC address includes a loop identification.
In one possible implementation, the destination MAC address corresponding to the ERPS loop includes a loop identification. The first network device obtains a first destination MAC address in the first message. When the first destination MAC address includes a loop identification, it may be determined that the first destination MAC address is the same as a destination MAC address corresponding to the ERPS loop. When the first destination MAC address does not include a loop identification, it may be determined that the first destination MAC address is different from a destination MAC address corresponding to an ERPS loop.
The method for obtaining the loop identifier may refer to the methods one to three described above, and is not described herein again.
As an example, the destination MAC address corresponding to the ERPS loop that can be identified by the first network device supporting the G.8032-201003 protocol is in the format of 0119-a700-00[ Ring ID ]. That is, the last two bits of the destination MAC address corresponding to the ERPS loop are the loop id. If the second network device supports g.8032-200806, the first destination MAC address included in the first message is 0119-a 700-0001. The first network device determines that the last two bits of the first destination MAC address are 01. When 01 is not a loop identification, then the first destination MAC address does not include a loop identification. The first network device may determine that the first destination MAC address is different from a destination MAC address corresponding to the ERPS loop.
Based on the two judgment methods, whether the first destination MAC address in the first message is the same as the destination MAC address corresponding to the ERPS loop can be determined. If the first destination MAC address is the same as the destination MAC address corresponding to the ERPS loop, it indicates that the second network device that sends the first packet can also process the packet including the destination MAC address corresponding to the loop identifier. The first network equipment and the second network equipment can normally communicate with each other. If the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop, it indicates that the second network device sending the first packet can process the packet carrying the first destination MAC address, and cannot process the packet carrying the destination MAC address corresponding to the ERPS loop. The version of the ERPS protocol supported by the second network device is different from the version of the ERPS protocol supported by the first network device. The first network device needs to adjust a destination MAC address carried in the transmitted packet, thereby implementing communication with the second network device.
It should be noted that, after determining that the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop, the first network device may continue to normally process the first packet including the first destination MAC address according to the local configuration information of the first network device. Specifically, the first network device may process the first packet according to a packet including a destination MAC address corresponding to the ERPS loop. Therefore, the first network device can process the first message sent by the second network device, and the situation that the first message is discarded because the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop is avoided.
S303: and the first network equipment sends a second message comprising the first destination MAC address to the network equipment included in the ERPS loop.
After determining that the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop, the first network device may send a second packet including the first destination MAC address to the network device in the ERPS loop. A network device, such as the second network device, in the ERPS loop, which can process the packet including the first destination MAC address, can process the second packet, so as to implement communication with the first network device. The first network equipment sends the second message including the first target MAC address, so that the intercommunication among the network equipment supporting different versions of ERPS protocols can be realized, and the compatibility of the ERPS protocols of different versions is realized.
When the ERPS loop includes a plurality of network devices capable of processing a packet including a destination MAC address corresponding to the ERPS loop, each network device capable of processing a packet including a destination MAC address corresponding to the ERPS loop can send a packet including a first destination MAC address based on the acquired packet including the first destination MAC address. Moreover, the network device capable of processing the message including the destination MAC address corresponding to the ERPS loop can process the message including the first destination MAC address in a manner of processing the message including the destination MAC address corresponding to the ERPS loop. Only messages including the first destination MAC address are transmitted in the ERPS loop. The network devices in the ERPS loop can process the message including the first destination MAC address, and the intercommunication among the network devices in the ERPS loop is realized.
As an example, referring to fig. 2, the network device 201 and the network device 202 are network devices capable of processing packets including a destination MAC address corresponding to an ERPS loop, and the network device 203 and the network device 204 are network devices capable of processing packets including a first destination MAC address. Wherein the first network device may be network device 201 and the second network device may be network device 203. The network device 201 sends a second packet including the first destination MAC address to other network devices in the ERPS loop based on the first packet sent by the network device 203. Network device 203 and network device 204 can process the second packet. After acquiring the second packet including the first destination MAC address, the network device 202 may send a packet including the first destination MAC address to other network devices in the ERPS loop based on the first destination MAC address different from the destination MAC address corresponding to the ERPS loop in the second packet. In this way, the network device 202 can also interact with the network device 203 and the network device 204, and normal communication between the network devices in the ERPS loop is realized.
Further, in some scenarios, as the network device in the ERPS loop is upgraded or replaced, the network device in the ERPS loop can process the packet including the destination MAC address corresponding to the loop identifier.
In this case, the messages sent by the network device in the ERPS loop may be uniformly adjusted without transmitting the messages including the first destination MAC address in the ERPS loop.
In a possible implementation manner, the first network device sends the third packet to the network device in the ERPS loop. And the third message comprises a destination MAC address corresponding to the ERPS loop. The network device receiving the third packet can send the destination MAC address carrying the destination MAC address corresponding to the ERPS loop based on the destination MAC address carrying the third packet and corresponding to the ERPS loop.
Wherein, the first network device may be a master node or a common node in the ERPS loop. The third message may be an ERPS protocol message of NR-RB type. The NR-RB type ERPS protocol packet can be used to configure a destination MAC address included in a packet sent by a network device in an ERPS loop.
When the first network device is a master node in the ERPS loop, the first network device may send the third packet to other network devices in the ERPS loop based on the acquired configuration instruction. The first network device may obtain a destination MAC address corresponding to the ERPS loop based on the configuration instruction.
Specifically, the destination MAC address corresponding to the ERPS loop may be a destination MAC address including a loop identification of the ERPS loop. The first network device may determine the destination MAC address corresponding to the ERPS loop based on the loop identification included in the configuration instruction.
When the first network device is a common node in the ERPS loop, the first network device can send a third message to other network devices in the ERPS loop based on the obtained message which is sent by other network devices and carries the destination MAC address corresponding to the ERPS loop.
Based on the above, when the network device in the ERPS loop can process the packet including the destination MAC address corresponding to the loop identifier, the destination MAC address included in the packet sent by the network device may be adjusted, and the sending of the packet including the first destination MAC address may be stopped. By adopting the method, the destination MAC address of the message transmitted in the ERPS loop can be flexibly adjusted based on the version of the ERPS protocol supported by the network equipment in the ERPS loop, and the normal communication between the network equipment in the ERPS loop is realized.
Fig. 4 shows a schematic diagram of a possible structure of the network device involved in the above embodiments, and the network device 400 can implement the function of the first network device in the example shown in fig. 3. Referring to fig. 4, the network device 400 includes: a receiving unit 401, a processing unit 402 and a transmitting unit 403. These units may perform the respective functions of the first network device in the above-described method example. An obtaining unit 401, configured to support the network device 400 to perform S301 in fig. 3; a processing unit 302, configured to support the network device 400 to execute S302 in fig. 3; a sending unit 403, configured to support the network device 400 to perform S303 in fig. 3; and/or other processes performed by the first network device in the techniques described herein.
For example, the obtaining unit 401 is configured to perform various obtaining operations performed by the first network device in the foregoing method embodiment; a processing unit 402, configured to perform operations of various processes of the first network device in the foregoing method embodiment; a sending unit 403, configured to perform various sending operations of the first network device in the foregoing method embodiment. For example, the obtaining unit 401 is configured to obtain a first packet sent by a second network device; a processing unit 402, configured to determine that the first destination MAC address is different from a destination MAC address corresponding to the ERPS loop; a sending unit 403, configured to send the second packet to the network device included in the ERPS loop. For a specific execution process, please refer to the detailed description of the corresponding steps in the embodiment shown in fig. 3, which is not repeated here.
It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. Each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. For example, in the above embodiments, the acquiring unit and the processing unit may be the same unit or different units. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
Referring to fig. 5, an embodiment of the present invention provides a message processing system 500, where the system 500 is configured to implement the message forwarding method in the foregoing method embodiment. The system 500 includes a network device 501 and a network device 502. Network device 501 may implement the functionality of the first network device in the embodiment shown in fig. 3 or network device 400 in fig. 4, and network device 502 may implement the functionality of the second network device in the embodiment shown in fig. 3. For a specific execution process, please refer to the detailed description of the corresponding steps in the embodiment shown in fig. 3, which is not repeated here.
Fig. 6 is a schematic structural diagram of an apparatus 600 according to an embodiment of the present disclosure. The first network device in fig. 3 or the network device 400 in fig. 4 may be implemented by the device shown in fig. 6. Referring to fig. 6, the device 600 includes at least one processor 601, a communication bus 602, and at least one network interface 604, and optionally, the device 600 may also include a memory 603. The processor 601 may be a general processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more Integrated Circuits (ICs) for controlling the execution of programs according to the present disclosure. The processor may be configured to process the packet to implement the packet forwarding method provided in this embodiment. For example, when the first network device in fig. 3 is implemented by the device shown in fig. 6, the processor may be configured to obtain the first packet sent by the second network device, and determine that the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop, where the specific function is implemented by referring to the processing portion corresponding to the first network device in the method embodiment. The communication bus 602 is used to transfer information between the processor 601, the network interface 604, and the memory 603. Memory 603 may be, but is not limited to, a read-only Memory (ROM) or other type of static storage device that may store static information and instructions, Memory 603 may also be a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, a compact disc read-only Memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 603 may be separate and coupled to the processor 601 through a communication bus 602. The memory 603 may also be integrated with the processor 601. Optionally, the memory 603 is used for storing program codes or instructions for executing the scheme of the present application, and is controlled to be executed by the processor 601. The processor 601 is used to execute program code or instructions stored in the memory 603. One or more software modules may be included in the program code. Alternatively, the processor 601 may also store program code or instructions for performing aspects of the present application, in which case the processor 601 need not read the program code or instructions into the memory 603. Network interface 604 may be a transceiver or the like for communicating with other devices or a communication network, such as an ethernet, a Radio Access Network (RAN), or a Wireless Local Area Network (WLAN). In this embodiment, the network interface 604 may be configured to receive a packet sent by another node in the segment routing network, and may also send a packet to another node in the segment routing network. The network interface 604 may be an ethernet (ethernet) interface, a Fast Ethernet (FE) interface, or a Gigabit Ethernet (GE) interface. In particular implementations, device 600 may include multiple processors, such as processor 601 and processor 605 shown in FIG. 6, for one embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).
Fig. 7 is a schematic structural diagram of an apparatus 700 according to an embodiment of the present disclosure. The first network device and the second network device in fig. 3 may be implemented by the devices shown in fig. 7. Referring to the schematic device configuration shown in fig. 7, a device 700 includes a main control board and one or more interface boards. The main control board is in communication connection with the interface board. The main control board, also called Main Processing Unit (MPU) or route processor card (route processor card), includes a CPU and a memory, and is responsible for controlling and managing various components in the device 700, including routing computation, device management, and maintenance functions. An interface board is also called a Line Processing Unit (LPU) or a line card (line card) and is used for receiving and transmitting messages. In some embodiments, the master control board communicates with the interface board or the interface board communicates with the interface board through a bus. In some embodiments, the interface boards communicate with each other through a switch board, in which case the device 700 also includes a switch board, the switch board is communicatively connected to the main control board and the interface boards, the switch board is used for forwarding data between the interface boards, and the switch board may also be referred to as a Switch Fabric Unit (SFU). The interface board includes a CPU, memory, a forwarding engine, and Interface Cards (ICs), which may include one or more network interfaces. The network interface can be an Ethernet interface, an FE interface or a GE interface. The CPU is in communication connection with the memory, the forwarding engine and the interface card respectively. The memory is used for storing a forwarding table. The forwarding engine is used for forwarding the received message based on the forwarding table stored in the memory. The forwarding engine may be a Network Processor (NP). The interface card is also called a daughter card and can be installed on an interface board and is responsible for converting photoelectric signals into data frames, and forwarding the data frames to a forwarding engine for processing or an interface board CPU after validity check is carried out on the data frames. In some embodiments, the CPU may also perform the functions of a forwarding engine, such as implementing soft forwarding based on a general purpose CPU, so that no forwarding engine is needed in the interface board. In some embodiments, the forwarding engine may be implemented by an ASIC or a Field Programmable Gate Array (FPGA). In some embodiments, the memory storing the forwarding table may also be integrated into the forwarding engine as part of the forwarding engine.
An embodiment of the present application further provides a chip system, including: a processor coupled to a memory, the memory for storing a program or instructions, which when executed by the processor, causes the system-on-chip to implement the method of the first network device or the second network device in the embodiment of fig. 3 described above.
Optionally, the system on a chip may have one or more processors. The processor may be implemented by hardware or by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.
Optionally, the memory in the system-on-chip may also be one or more. The memory may be integrated with the processor or may be separate from the processor, which is not limited in this application. For example, the memory may be a non-transitory processor, such as a read only memory ROM, which may be integrated with the processor on the same chip or separately disposed on different chips, and the type of the memory and the arrangement of the memory and the processor are not particularly limited in this application.
The system on chip may be, for example, an FPGA, an ASIC, a system on chip (SoC), a CPU, an NP, a digital signal processing circuit (DSP), a Micro Controller Unit (MCU), a Programmable Logic Device (PLD) or other integrated chips.
It will be appreciated that the steps of the above described method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.
The embodiment of the present application further provides a computer-readable storage medium, which includes instructions, when executed on a computer, cause the computer to execute the method in the foregoing embodiment
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In the present application, "at least one item(s)" means one or more, "a plurality" means two or more. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple. In the present application, "A and/or B" is considered to include A alone, B alone, and A + B.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical module division, and other division manners may be available in actual implementation, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be obtained according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, each module unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a hardware form, and can also be realized in a software module unit form.
The integrated unit, if implemented as a software module unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Those skilled in the art will recognize that in one or more of the examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The above-described embodiments are intended to provide further details of the objects, technical solutions and advantages of the present application, and it should be understood that the above-described embodiments are merely exemplary embodiments of the present application.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims (19)

1. A message forwarding method is applied to an Ethernet Ring Protection Switching (ERPS) loop, and comprises the following steps:
a first network device included in the ERPS loop receives a first message sent by a second network device included in the ERPS loop, wherein the first message includes a first destination Media Access Control (MAC) address;
and the first network equipment determines that the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop, and sends a second message to the network equipment included in the ERPS loop, wherein the second message includes the first destination MAC address.
2. The method of claim 1, wherein the first network device determining that the first destination MAC address is different from a destination MAC address corresponding to the ERPS loop comprises:
the first network equipment acquires a second destination MAC address, wherein the second destination MAC address is a destination MAC address corresponding to the ERPS loop;
the first network device determines that the first destination MAC address is different from the second destination MAC address.
3. The method of claim 2, wherein the first network device obtaining the second destination MAC address comprises:
the first network equipment acquires a loop identifier of the ERPS loop;
and the first network equipment acquires the second destination MAC address according to a first corresponding relation and the loop identifier of the ERPS loop, wherein the first corresponding relation comprises the second destination MAC address and the loop identifier of the ERPS loop.
4. The method of claim 2, wherein the first network device obtaining the second destination MAC address comprises:
the first network equipment acquires a loop identifier of the ERPS loop;
and the first network equipment acquires the second destination MAC address according to the loop identifier of the ERPS loop, wherein the second destination MAC address comprises the loop identifier of the ERPS loop.
5. The method of claim 1, wherein the first network device determining that the first destination MAC address is different from a destination MAC address corresponding to the ERPS loop comprises:
the first network equipment acquires a loop identifier of the ERPS loop;
the first network device determines that the first destination MAC address does not include the loop identifier of the ERPS loop based on the first destination MAC address and the loop identifier of the ERPS loop.
6. The method according to any one of claims 3 to 5, wherein the first packet further includes an identifier of a Virtual Local Area Network (VLAN), and the obtaining, by the first network device, the loop identifier of the ERPS loop includes:
and the first network equipment acquires the loop identifier of the ERPS loop based on a second corresponding relation and the identifier of the VLAN, wherein the second corresponding relation comprises the identifier of the VLAN and the loop identifier of the ERPS loop.
7. The method according to any of claims 3 to 5, wherein the obtaining, by the first network device, the loop identifier of the ERPS loop comprises:
the first network equipment acquires the loop identification of the ERPS loop based on the ERPS loop to which the first network equipment belongs; or
And the first network equipment acquires the loop identification of the ERPS loop based on the VLAN to which the first network equipment belongs.
8. The method according to any one of claims 1 to 7, further comprising:
and the first network equipment sends a third message to the network equipment of the ERPS loop, wherein the third message comprises a destination MAC address corresponding to the ERPS loop.
9. The method according to claim 8, wherein the third packet is a no request-protect link blocking (NR-RB) packet, and the destination MAC address corresponding to the ERPS loop includes a loop identifier of the ERPS loop.
10. A network device, wherein the network device is a first network device in an Ethernet Ring Protection Switching (ERPS) loop, and the network device comprises:
a receiving unit, configured to receive a first packet sent by a second network device included in the ERPS loop, where the first packet includes a first destination media access control MAC address;
a processing unit, configured to determine that the first destination MAC address is different from a destination MAC address corresponding to the ERPS loop;
a first sending unit, configured to send a second packet to a network device included in the ERPS loop, where the second packet includes the first destination MAC address.
11. The network device of claim 10, wherein the processing unit is configured to obtain a second destination MAC address, determine that the first destination MAC address is different from the second destination MAC address, and the second destination MAC address is a destination MAC address corresponding to the ERPS loop.
12. The network device of claim 11, wherein the processing unit configured to obtain the second destination MAC address comprises:
the processing unit obtains a loop identifier of the ERPS loop, and obtains the second destination MAC address according to a first corresponding relationship and the loop identifier of the ERPS loop, wherein the first corresponding relationship comprises the second destination MAC address and the loop identifier of the ERPS loop.
13. The network device of claim 11, wherein the processing unit configured to obtain the second destination MAC address comprises:
the processing unit obtains a loop identifier of the ERPS loop, and obtains the second destination MAC address according to the loop identifier of the ERPS loop, wherein the second destination MAC address comprises the loop identifier of the ERPS loop.
14. The network device of claim 10, wherein the processing unit is configured to obtain a loop id of the ERPS loop, and determine that the first destination MAC address does not include the loop id of the ERPS loop based on the first destination MAC address and the loop id of the ERPS loop.
15. The network device according to any one of claims 12 to 14, wherein the first packet further includes an identifier of a virtual local area network VLAN, and the acquiring, by the processing unit, the loop identifier of the ERPS loop includes:
the processing unit obtains a loop identifier of the ERPS loop based on a second corresponding relationship and the identifier of the VLAN, wherein the second corresponding relationship comprises the identifier of the VLAN and the loop identifier of the ERPS loop.
16. The network device according to any of claims 12 to 15, wherein the processing unit obtaining the loop identifier of the ERPS loop comprises:
the processing unit acquires a loop identifier of the ERPS loop based on the ERPS loop to which the first network equipment belongs;
alternatively, the first and second electrodes may be,
the processing unit acquires the loop identification of the ERPS loop based on the VLAN to which the first network device belongs.
17. The network device of any of claims 10 to 16, wherein the network device further comprises:
a second sending unit, configured to send a third packet to the network device of the ERPS loop, where the third packet includes a destination MAC address corresponding to the ERPS loop.
18. The network device according to claim 17, wherein the third packet is a no request-protect link blocking NR-RB packet, and the destination MAC address corresponding to the ERPS loop includes a loop identifier of the ERPS loop.
19. A message forwarding system is characterized in that the system comprises a first network device and a second network device, wherein the first network device and the second network device belong to an Ethernet Ring Protection Switching (ERPS) loop;
the second network device is configured to send a first packet to the first network device, where the first packet includes a first destination MAC address;
the first network device is configured to receive the first packet sent by the second network device, determine that the first destination MAC address is different from the destination MAC address corresponding to the ERPS loop, and send a second packet to other network devices included in the ERPS loop, where the second packet includes the first destination MAC address.
CN202111668873.6A 2021-12-30 2021-12-30 Message forwarding method, network equipment and system Active CN114401324B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111668873.6A CN114401324B (en) 2021-12-30 2021-12-30 Message forwarding method, network equipment and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111668873.6A CN114401324B (en) 2021-12-30 2021-12-30 Message forwarding method, network equipment and system

Publications (2)

Publication Number Publication Date
CN114401324A true CN114401324A (en) 2022-04-26
CN114401324B CN114401324B (en) 2024-03-01

Family

ID=81229563

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111668873.6A Active CN114401324B (en) 2021-12-30 2021-12-30 Message forwarding method, network equipment and system

Country Status (1)

Country Link
CN (1) CN114401324B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4346173A1 (en) * 2022-09-28 2024-04-03 Adtran, Inc. Communication resilience in a ring network topology

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012120528A1 (en) * 2011-03-07 2012-09-13 Tejas Networks Ltd Ethernet chain protection switching
CN104079462A (en) * 2014-07-16 2014-10-01 北京华为数字技术有限公司 Ring network configuration detection method and device
CN104702444A (en) * 2015-03-27 2015-06-10 杭州华三通信技术有限公司 Method and device for handling ERPS (Ethernet Ring Protection Switching) protocol message
CN105847147A (en) * 2016-03-17 2016-08-10 浙江宇视科技有限公司 Data transmission method and device
CN106571936A (en) * 2015-10-08 2017-04-19 中兴通讯股份有限公司 Loop network protection data configuration method and device
CN112003783A (en) * 2020-08-21 2020-11-27 烽火通信科技股份有限公司 Method and device for preventing ring of Ethernet two-layer
CN113794656A (en) * 2021-08-25 2021-12-14 新华三信息安全技术有限公司 Message forwarding method and device

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012120528A1 (en) * 2011-03-07 2012-09-13 Tejas Networks Ltd Ethernet chain protection switching
CN104079462A (en) * 2014-07-16 2014-10-01 北京华为数字技术有限公司 Ring network configuration detection method and device
CN104702444A (en) * 2015-03-27 2015-06-10 杭州华三通信技术有限公司 Method and device for handling ERPS (Ethernet Ring Protection Switching) protocol message
CN106571936A (en) * 2015-10-08 2017-04-19 中兴通讯股份有限公司 Loop network protection data configuration method and device
CN105847147A (en) * 2016-03-17 2016-08-10 浙江宇视科技有限公司 Data transmission method and device
CN112003783A (en) * 2020-08-21 2020-11-27 烽火通信科技股份有限公司 Method and device for preventing ring of Ethernet two-layer
CN113794656A (en) * 2021-08-25 2021-12-14 新华三信息安全技术有限公司 Message forwarding method and device

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4346173A1 (en) * 2022-09-28 2024-04-03 Adtran, Inc. Communication resilience in a ring network topology

Also Published As

Publication number Publication date
CN114401324B (en) 2024-03-01

Similar Documents

Publication Publication Date Title
CN111865779B (en) Route synchronization method and cross-device link aggregation group
EP2725749B1 (en) Method, apparatus and system for processing service flow
US10560550B1 (en) Automatic configuration of a replacement network device in a high-availability cluster
EP3316555B1 (en) Mac address synchronization method, device and system
US20190260640A1 (en) Port auto-negotiation method and device
US11750496B2 (en) Method for multi-cloud interconnection and device
US20140112205A1 (en) System and method for pinning virtual machine adapters to physical adapters in a network environment
CN114401324B (en) Message forwarding method, network equipment and system
US8108736B2 (en) Multi-partition computer system, failure handling method and program therefor
CN114826918A (en) Message forwarding method, message processing method and device
WO2023116457A1 (en) Packet processing method and apparatus, and communication system
CN115152192B (en) PCE controlled network reliability
US11916768B2 (en) Information sharing method and apparatus in redundancy network, and computer storage medium
CN106657355B (en) Cluster management method and device
CN114640615B (en) Route notification method, route generation method and device
CN110995502B (en) Network configuration management method, device, switching equipment and readable storage medium
CN116132299A (en) Processing method and device
CN116584078A (en) Method and apparatus for mobile communication system
CN114531319A (en) Message sending method, equipment and system
CN108965126B (en) Message forwarding method and device
CN113452543B (en) Detection of multi-host misconfiguration
US20160036717A1 (en) Determining an active management uplink
CN117527533A (en) Backup method, device and system for network address translation service
JP3691679B2 (en) Network with dual transmission path
CN114124753A (en) Message sending method and equipment

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