CN106452992B - Method and device for realizing remote multi-homing networking - Google Patents
Method and device for realizing remote multi-homing networking Download PDFInfo
- Publication number
- CN106452992B CN106452992B CN201610831322.XA CN201610831322A CN106452992B CN 106452992 B CN106452992 B CN 106452992B CN 201610831322 A CN201610831322 A CN 201610831322A CN 106452992 B CN106452992 B CN 106452992B
- Authority
- CN
- China
- Prior art keywords
- leaf device
- message
- leaf
- devices
- identity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2869—Operational details of access network equipments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method and a device for realizing remote multi-homing networking, wherein the method comprises the following steps: the method comprises the steps that a first Leaf device is associated with a far-end second Leaf device, the first Leaf device determines a main Leaf device and a standby Leaf device from the second Leaf device, identity confirmation parameters are notified to the second Leaf device, and the second Leaf device determines the identity type of the second Leaf device associated with the first Leaf device, so that the far-end multi-homing access of the first Leaf device is achieved, and the access reliability is improved.
Description
Technical Field
The present invention relates to the field of network communication technologies, and in particular, to a method and an apparatus for implementing remote multi-homing networking.
Background
An EVPN (Ethernet Virtual Private Network) is a two-layer VPN technology, where a control plane uses MP-BGP (multi-Protocol-Border Gateway Protocol) to announce EVPN routing information, and a data plane uses VXLAN (Virtual eXtensible local area Network) encapsulation to forward a packet. The EVPN may provide two-layer interconnection for the same subnet of the same tenant, and three-layer interconnection for different subnets of the same tenant through an EVPN gateway, and provide three-layer interconnection with an external network for the same subnet, based on an existing service provider or an enterprise IP (internet protocol) network. Currently, EVPN networks do not support remote multi-homing networking of Leaf devices.
Disclosure of Invention
The invention aims to provide a method and a device for realizing remote multi-homing networking, which are used for realizing remote multi-homing access of Leaf equipment.
In order to realize the purpose, the invention provides the technical scheme that:
the invention provides a method for realizing remote multi-homing networking, which is applied to first Leaf equipment and comprises the following steps:
determining a main Leaf device from remote second Leaf devices associated with the first Leaf device, and determining Leaf devices except the main Leaf device in the second Leaf devices as standby Leaf devices;
and sending an announcement message, wherein the announcement message carries an identity confirmation parameter, so that the second Leaf device confirms the identity type of the second Leaf device associated with the first Leaf device according to the identity confirmation parameter, and the identity type is a main Leaf device or a standby Leaf device.
The invention also provides a method for realizing the remote multi-homing networking, which is applied to the second Leaf device and comprises the following steps:
receiving an announcement message sent by a first Leaf device at a far end, wherein the first Leaf device is associated with at least two second Leaf devices, and the announcement message carries an identity confirmation parameter;
and determining the identity type of a second Leaf device associated with the first Leaf device according to the identity confirmation parameters, wherein the identity type is a main Leaf device or a standby Leaf device.
The invention also provides a device for realizing the remote multi-homing networking, which is applied to the first Leaf equipment, and the device comprises:
a determining unit, configured to determine a master Leaf device from remote second Leaf devices associated with the first Leaf device, and determine Leaf devices other than the master Leaf device in the second Leaf devices as standby Leaf devices;
and the sending unit is used for sending an announcement message, wherein the announcement message carries an identity confirmation parameter so that the second Leaf device confirms the identity type of the second Leaf device associated with the first Leaf device according to the identity confirmation parameter, and the identity type is a main Leaf device or a standby Leaf device.
The invention also provides a device for realizing the remote multi-homing networking, which is applied to the second Leaf equipment, and the device comprises:
a receiving unit, configured to receive an announcement message sent by a first Leaf device at a remote end, where the first Leaf device is associated with at least two second Leaf devices, and the announcement message carries an identity confirmation parameter;
and the determining unit is used for determining the identity type of a second Leaf device associated with the first Leaf device according to the identity confirmation parameter, wherein the identity type is a main Leaf device or a standby Leaf device.
As can be seen from the above description, the present invention associates the first Leaf device with a remote second Leaf device, determines a master Leaf device and a standby Leaf device from the second Leaf devices, and notifies the second Leaf device of an identity confirmation parameter, so that the second Leaf device determines the identity types of itself and other second Leaf devices for the first Leaf, thereby implementing remote multi-homing access of the first Leaf device and improving access reliability.
Drawings
Fig. 1 is a schematic diagram of an EVPN network shown in an embodiment of the present invention;
fig. 2 is a flowchart illustrating a method for implementing the remote multihoming networking according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a method for implementing the remote multihoming networking according to another embodiment of the present invention;
fig. 4 is a schematic structural diagram of a first Leaf device or a second Leaf device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram illustrating an apparatus for implementing remote multihoming networking according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an apparatus for implementing remote multihoming networking according to another embodiment of the present invention.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present invention. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The embodiment of the invention provides a method for realizing remote multi-homing networking, which associates a first Leaf device with a remote second Leaf device, wherein the first Leaf device determines a main Leaf device and a standby Leaf device from the second Leaf device, and informs the second Leaf device of an identity confirmation parameter, so that the second Leaf device determines the identity types of the second Leaf device and other second Leaf devices aiming at the first Leaf, and the remote multi-homing access of the first Leaf device is realized.
Referring to fig. 1, a schematic diagram of an EVPN network according to an embodiment of the present invention is shown. Configuring an EVPN instance on each Leaf device that specifies a Leaf1 as a first Leaf device and a Leaf2 and a Leaf3 as remote second Leaf devices associated with a Leaf 1; spine1 is a core device; leaf4 is a remote Leaf device not associated with Leaf 1; host 1-Host 4 are user hosts. The second Leaf device at the far end associated with Leaf1 may be a Leaf device directly connected to Leaf1, i.e., in this example, Leaf2 and Leaf3 are Leaf devices directly connected to Leaf1, respectively.
Referring to fig. 2, a flowchart of an embodiment of a method for implementing a remote multihoming networking according to the present invention is shown, where the embodiment describes an implementation process of the remote multihoming networking from a first Leaf device side.
Step 201, determining a main Leaf device from remote second Leaf devices associated with the first Leaf device, and determining Leaf devices other than the main Leaf device in the second Leaf devices as standby Leaf devices.
In the invention, the first Leaf device at least relates to two remote second Leaf devices, and the main Leaf device and the standby Leaf device are determined from the second Leaf devices. Specifically, the priority of the associated second Leaf device is obtained; and determining the main Leaf device according to the priority of the second Leaf device. For example, in one embodiment, the priority of the second Leaf device associated with the first Leaf device may be configured on the first Leaf device, the second Leaf device with the highest priority may be determined as the master Leaf device, and the second Leaf devices other than the master Leaf device may be determined as the standby Leaf devices.
Step 202, sending an announcement message, where the announcement message carries an identity confirmation parameter, so that the second Leaf device confirms an identity type of the second Leaf device associated with the first Leaf device according to the identity confirmation parameter, where the identity type is a primary Leaf device or a standby Leaf device.
When a second Leaf device associated with the first Leaf device is specified, a BGP (Border Gateway Protocol) neighbor may be established between the first Leaf device and the second Leaf device, and the advertisement message may be a BGP Protocol message (e.g., an update message in the BGP Protocol).
In this step, the first Leaf device triggers the second Leaf device to determine the identity type by sending an announcement message, where the identity type includes the identity type of itself and other second Leaf devices associated with the first Leaf device, that is, who is the primary Leaf device and who is the standby Leaf device in all the second Leaf devices associated with the first Leaf device.
In an embodiment, when the advertisement message is a priority advertisement message, the identity confirmation parameter carried in the advertisement message is the priority of the second Leaf device, so that the second Leaf device confirms the identity type corresponding to the first Leaf device according to the priorities of all the second Leaf devices associated with the first Leaf device.
In another embodiment, when the notification message is an abnormal notification message (for example, when the primary Leaf device fails or the tunnel connection between the first Leaf device and the primary Leaf device is disconnected, the first Leaf device may detect an abnormality and send the abnormal notification message), the identity confirmation parameter carried by the notification message is the identifier of the primary Leaf device in which the abnormality occurs, so that the second Leaf device reconfirms the identity type of the second Leaf device associated with the first Leaf device according to the priority of the standby Leaf device associated with the first Leaf device, that is, reconfirming the primary Leaf device from the standby Leaf devices.
It should be noted that, when the abnormal master Leaf device returns to normal, the identity type of the original master Leaf device may be restored according to a preset policy, or the existing master Leaf device may be maintained.
And finishing the remote multi-homing networking of the Leaf equipment.
Under the remote multi-attribution networking, the first Leaf device receives a message sent by the local user host and determines the type of the message. And when the message is a broadcast message or a first unicast message, forwarding the message to the main Leaf device, so that the main Leaf device sends the received broadcast message to the local user host and other Leaf devices, or forwarding the first unicast message according to a forwarding table entry stored by the main Leaf device. The first unicast message is a unicast message of which the destination address does not hit the local forwarding table entry. For the first Leaf device, the first unicast message is a unicast message whose destination address does not hit the forwarding table stored in the first Leaf device. And forwarding the unicast message hitting the forwarding table entry according to the forwarding table entry.
It should be added that, in the present invention, the first Leaf device does not store the forwarding table entry matching with the remote user host. When the local user host of the first Leaf device accesses the remote user host, the local user host can be forwarded to the main Leaf device (the main Leaf device usually stores forwarding table entries of all user hosts) in a first unicast message manner to forward, so as to reduce resource occupation of the first Leaf device, that is, the first Leaf device can adopt a device with a weak specification and performance, thereby reducing the cost of accessing the network.
In addition, when the first Leaf device receives the broadcast message from the main Leaf device, the broadcast message is broadcasted to the local user host; and when receiving the unicast message from the associated second Leaf equipment, forwarding the unicast message to the local user host according to the local forwarding table entry.
Referring to fig. 3, a flowchart of another embodiment of the method for implementing a remote multi-homing networking according to the present invention is shown, where the embodiment describes an implementation process of the remote multi-homing networking from the second Leaf device side.
Step 301, receiving an announcement message sent by a first Leaf device at a remote end, where the first Leaf device is associated with at least two second Leaf devices, and the announcement message carries an identity confirmation parameter.
Step 302, determining an identity type of a second Leaf device associated with the first Leaf device according to the identity confirmation parameter, where the identity type is a primary Leaf device or a standby Leaf device.
As can be seen from the description of step 202 on the first Leaf device side, the notification packet sent by the first Leaf device may be a priority notification packet or an exception notification packet, and both of the above packets may trigger the second Leaf device to determine the identity type of the second Leaf device associated with the first Leaf device.
And when the notification message is a priority notification message, the identity confirmation parameter carried by the notification message is the priority of the second Leaf device. The second Leaf device determines the identity type of the second Leaf device according to the priority of all the second Leaf devices associated with the first Leaf device, including the identity type of the second Leaf device and the identity types of other second Leaf devices associated with the first Leaf device.
When the notification message is an abnormal notification message, the identity confirmation parameter carried by the notification message is the identifier of the main Leaf device with the abnormal condition, and the second Leaf device reconfirms the identity type of the second Leaf device associated with the first Leaf device according to the priority of the standby Leaf device associated with the first Leaf device. For details, refer to the description of the first Leaf device side, and are not described herein again.
After the remote multi-homing networking is completed, each second Leaf device associated with the first Leaf device executes message forwarding according to the identity type of the second Leaf device.
When the second Leaf device associated with the first Leaf device determines that the identity type of the second Leaf device is the main Leaf device, the message forwarding process is as follows:
the method comprises the steps that a main Leaf device receives a message sent by a first Leaf device; and when the message is a broadcast message or a second unicast message, sending the message to the local user host and other Leaf devices, so that the other Leaf devices broadcast the message to the respective local user hosts. And the second unicast message is a unicast message of which the destination address does not hit the local forwarding table entry. For the main Leaf device, the second unicast message is a unicast message whose destination address does not hit the forwarding table stored in the main Leaf device. And forwarding the unicast message hitting the forwarding table entry according to the forwarding table entry.
The main Leaf device receives messages sent by other Leaf devices except the first Leaf device, determines the message type, and sends the messages to the local user host and the first Leaf device when the messages are broadcast messages or second unicast messages, so that the first Leaf device broadcasts the messages to the local user host. And the second unicast message is a unicast message of which the destination address does not hit the local forwarding table entry. And forwarding the unicast message hitting the forwarding table entry according to the forwarding table entry.
In addition, the main Leaf device receives the message sent by the local user host, and when the message is a broadcast message or a second unicast message, the main Leaf device sends the broadcast message or the second unicast message to other Leaf devices, so that the other Leaf devices broadcast to the respective local user hosts. And forwarding the unicast message hitting the forwarding table entry according to the forwarding table entry.
When the second Leaf device associated with the first Leaf device determines that the identity type of the second Leaf device is the standby Leaf device, the message forwarding process is as follows:
receiving a message sent by a local user host by standby Leaf equipment; when the message is a broadcast message or a second unicast message, the message is sent to other Leaf devices except the first Leaf device, so that the other Leaf devices except the first Leaf device broadcast the message to respective local user hosts, and simultaneously, the main Leaf device sends the message to the first Leaf device, and the first Leaf device broadcasts the message to the local user hosts. And the second unicast message is a unicast message of which the destination address does not hit the local forwarding table entry. For the standby Leaf device, the second unicast message is a unicast message whose destination address does not hit the forwarding table stored in the standby Leaf device. And forwarding the unicast message hitting the forwarding table entry according to the forwarding table entry.
In addition, the standby Leaf device receives messages sent by other Leaf devices except the first Leaf device, determines the message type, and broadcasts the message to the local user host when the message is a broadcast message or a second unicast message. And the second unicast message is a unicast message of which the destination address does not hit the local forwarding table entry. And forwarding the unicast message hitting the forwarding table entry according to the forwarding table entry.
As can be seen from the foregoing description, according to the present invention, a first Leaf device is associated with a second Leaf device, and the first Leaf device determines a primary Leaf device and a standby Leaf device from the second Leaf device, and notifies the second Leaf device of an identity confirmation parameter, so that the second Leaf device determines the identity types of itself and other second Leaf devices for the first Leaf, thereby implementing remote multi-homing access of the first Leaf device, and improving reliability of access. Meanwhile, the first Leaf device does not need to store the forwarding table entry of the remote user host, so that the requirement on the specification of the first Leaf device can be reduced, and the cost of accessing the network is further reduced.
Still taking the EVPN network shown in fig. 1 as an example, Leaf1 associates with Leaf2 and Leaf3 at remote locations and establishes BGP neighbors with Leaf2 and Leaf 3.
Leaf2 and Leaf3 are configured on Leaf1 with priorities of 7 and 1, respectively (higher priority with higher value). The Leaf1 determines that Leaf2 is the primary Leaf device and Leaf3 is the standby Leaf device according to the priority of Leaf2 and Leaf 3. Meanwhile, priority notification messages are sent to the Leaf2 and the Leaf3, and the priority of the Leaf2 and the priority of the Leaf3 are carried in the priority notification messages, so that the Leaf2 and the Leaf3 determine a main Leaf device and a standby Leaf device according to the priorities. The priority announcement message can be implemented by using a BGP protocol message extension.
After receiving the priority announcement message, the Leaf2 confirms that the message is a main Leaf device according to the priorities of the Leaf2 and the Leaf 3; similarly, after receiving the priority announcement message, the Leaf3 confirms that the Leaf3 is a standby Leaf device and the Leaf2 is a main Leaf device according to the priorities of the Leaf2 and the Leaf 3.
In the case of the remote multi-homing networking, the message forwarding process is described by taking an example that the Host1 accesses the Host4 in a Ping manner. Assume that IP (Internet Protocol) addresses of Host1 to Host4 are IP1 to IP4, respectively, and MAC (Media Access Control) addresses are MAC1 to MAC4, respectively.
First, Host1 needs to obtain the MAC address of Host 4. The Host1 sends an ARP (Address resolution protocol) request message, where the ARP request message is a broadcast message, and the destination IP Address is IP4, and is used to request to obtain the MAC Address of the Host 4.
And the Leaf1 receives the ARP request message sent by the Host1, performs EVPN tunnel encapsulation on the ARP request message, and forwards the ARP request message to the Leaf 2. Meanwhile, Leaf1 learns ARP information (MAC1 and IP1) of the Host1, locally generates a forwarding table entry of the Host1, and because the Leaf1 establishes BGP neighbors with the Leaf2 and the Leaf3, the ARP information of the Host1 can be notified to the Leaf2 and the Leaf3 through BGP protocol messages (e.g., update messages in the BGP protocol).
After receiving the EVPN tunnel message of Leaf1, Leaf2 releases the tunnel encapsulation, broadcasts the ARP request message to local Host2, and performs EVPN tunnel encapsulation to transmit to other Leaf devices (Leaf1, Leaf3, Leaf 4). Meanwhile, the Leaf2 receives a BGP protocol message carrying the ARP information of the Host1 sent by the Leaf1, learns the ARP information of the Host1, locally generates a forwarding table entry of the Host1, and notifies the Leaf4 of the ARP information of the Host1 through the BGP protocol message, and the next hop is the self.
After receiving the EVPN tunnel message of the Leaf2, the Leaf3 releases the tunnel encapsulation and broadcasts an ARP request message to the local Host 3. Meanwhile, the Leaf3 receives a BGP protocol message carrying the ARP information of the Host1 sent by the Leaf1, learns the ARP information of the Host1, locally generates a forwarding table entry of the Host1, and notifies the Leaf4 of the ARP information of the Host1 through the BGP protocol message, and the next hop is the self.
After receiving the EVPN tunnel message of Leaf2, Leaf1 releases the tunnel encapsulation, and if there are other user hosts besides Host1, it broadcasts ARP request message to other user hosts.
After receiving the EVPN tunnel message of the Leaf2, the Leaf4 releases the tunnel encapsulation and broadcasts an ARP request message to the local Host 4. Meanwhile, Leaf4 receives BGP protocol messages carrying the ARP information of Host1 sent by Leaf2 and Leaf3, learns the ARP information of Host1, locally generates forwarding table entries of Host1, and considers Leaf2 and Leaf3 as next hops to Host 1.
After receiving the ARP request message of the Host1, the Host4 learns the ARP information of the Host1 and sends an ARP response message, wherein the destination IP address is IP 1.
After receiving the ARP reply message, the Leaf4 queries the forwarding table entry according to the destination IP address to find the next hop to be Leaf2 and Leaf3, selects the next hop to be Leaf3 according to a preset algorithm (for example, hash operation), performs EVPN tunnel encapsulation on the ARP reply message, and forwards the ARP reply message to Leaf 3. Meanwhile, Leaf4 learns ARP information (MAC4 and IP4) of Host4, locally generates a forwarding table entry of Host4, and notifies ARP information of Host4 to Leaf2 and Leaf3 through BGP protocol messages.
The Leaf2 receives the BGP protocol message which is sent by the Leaf4 and carries ARP information of the Host4, learns the ARP information of the Host4 and locally generates a forwarding table entry of the Host 4.
The Leaf3 receives the BGP protocol message which is sent by the Leaf4 and carries ARP information of the Host4, learns the ARP information of the Host4 and locally generates a forwarding table entry of the Host 4.
Meanwhile, the Leaf3 receives the EVPN tunnel message of the Leaf4, and can forward the EVPN tunnel message based on the following two ways: the method is that the EVPN tunnel message is sent to a Leaf2 after being repackaged, and then forwarded to a Leaf1 by a Leaf2 (as a main Leaf device); in the second mode, the Leaf3 queries the forwarding table entry according to the destination IP address of the inner-layer ARP reply message to find the next hop to be Leaf1, repackages the EVPN tunnel and forwards the EVPN tunnel to the Leaf 1.
After receiving the EVPN tunnel message of Leaf2 or Leaf3, Leaf1 removes the tunnel encapsulation, and queries the forwarding table entry according to the destination IP address of the inner layer ARP reply message and forwards the forwarding table entry to Host 1. It is emphasized that Leaf1 does not learn the ARP information carried by the received message from the tunnel.
After receiving the ARP response message, the Host1 learns the ARP information of the Host 4. To this end, the Host1 acquires the MAC address of the Host 4.
The Host1 sends a Ping Packet to the Host4, where the Ping Packet is a unicast message (the source MAC address is MAC1, the source IP address is IP1, the destination MAC is MAC4, and the destination IP address is IP4), and is marked as Packet 1.
After receiving Packet1, Leaf1 queries a local forwarding table entry, and no forwarding table entry of Host4 exists, so that the Packet is forwarded to Leaf2 after EVPN tunnel encapsulation.
After receiving the EVPN tunnel message of Leaf1, Leaf2 decapsulates the tunnel, matches the forwarding table entry of Host4 according to the destination IP address of inner layer Packet1, finds the next hop to be Leaf4, and forwards the Leaf4 after EVPN tunnel encapsulation.
After receiving the EVPN tunnel message of the Leaf2, the Leaf4 de-tunnels the Packet, matches the forwarding table entry of the Host4 according to the destination IP address of the inner layer Packet1, and forwards the Packet to the Host 4.
The Host4 sends a response Packet2 for Packet1 (the source MAC address is MAC4, the source IP address is IP4, the destination MAC is MAC1, and the destination IP address is IP 1). The forwarding process is the same as above, and forwarding is performed according to the forwarding table entry, which is not described herein again.
When the Leaf2 associated with the Leaf1 fails, the Leaf1 sends an exception notification message carrying the identification of the Leaf 2. After receiving the exception notification message, the Leaf3 obtains the priority of the Leaf device associated with the Leaf1, and since only the Leaf3 is currently associated with the Leaf1, the Leaf3 determines that the Leaf is the main Leaf device associated with the Leaf 1. Leaf1 also determines Leaf3 as the master Leaf device based on the Leaf device with which it is associated. And subsequently, the message is forwarded through the redetermined main Leaf equipment, and the specific forwarding process is not described any more.
Corresponding to the embodiment of the method for implementing the remote multi-homing networking, the invention also provides an embodiment of an implementation device for the remote multi-homing networking.
The embodiment of the apparatus for implementing remote multi-homing networking of the present invention may be applied to the first Leaf device or the second Leaf device. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. A software implementation is taken as an example, and a logical means is formed by a processor of the device in which it is located running corresponding computer program instructions in a memory. From a hardware aspect, as shown in fig. 4, the hardware structure diagram of the device for implementing the remote multihoming networking of the present invention is shown, except for the processor and the nonvolatile memory shown in fig. 4, the device where the apparatus is located in the embodiment may also include other hardware according to the actual function of the device, which is not described again.
Fig. 5 is a schematic structural diagram of an apparatus for implementing a remote multihoming networking according to an embodiment of the present invention. The apparatus for implementing the remote multi-homing networking comprises a determining unit 501 and a sending unit 502, wherein:
a determining unit 501, configured to determine a master Leaf device from remote second Leaf devices associated with the first Leaf device, and determine Leaf devices other than the master Leaf device in the second Leaf devices as standby Leaf devices;
a sending unit 502, configured to send an announcement message, where the announcement message carries an identity confirmation parameter, so that the second Leaf device confirms an identity type of the second Leaf device associated with the first Leaf device according to the identity confirmation parameter, where the identity type is a primary Leaf device or a standby Leaf device.
Further, the air conditioner is provided with a fan,
the determining unit 501 is specifically configured to obtain a priority of the associated second Leaf device; and determining the main Leaf equipment according to the priority of the second Leaf equipment.
Further, the air conditioner is provided with a fan,
the sending unit 502 is specifically configured to, when the notification packet is a priority notification packet, determine that the identity confirmation parameter is the priority of the second Leaf device, so that the second Leaf device confirms the identity type of the second Leaf device associated with the first Leaf device according to the priorities of all the second Leaf devices associated with the first Leaf device.
Further, the air conditioner is provided with a fan,
the sending unit 502 is specifically configured to, when the notification packet is an abnormal notification packet, determine that the identity confirmation parameter is an identifier of a primary Leaf device that is abnormal, so that a second Leaf device reconfirms an identity type of a second Leaf device associated with a first Leaf device according to a priority of a standby Leaf device associated with the first Leaf device.
Further, the apparatus further comprises:
the processing unit is used for receiving a message sent by the local user host; and when the message is a broadcast message or a first unicast message, forwarding the message to the main Leaf device, wherein the first unicast message is a unicast message of which the destination address does not hit a local forwarding table item, so that the main Leaf device sends the broadcast message to a local user host and other Leaf devices, or forwards the first unicast message according to a forwarding table item stored by the main Leaf device, wherein the first Leaf device does not store the forwarding table item matched with a remote user host.
Fig. 6 is a schematic structural diagram of an apparatus for implementing a remote multihoming networking according to another embodiment of the present invention. The apparatus for implementing the remote multi-homing networking comprises a receiving unit 601 and a determining unit 602, wherein:
a receiving unit 601, configured to receive an announcement packet sent by a first Leaf device at a remote end, where the first Leaf device is associated with at least two second Leaf devices, and the announcement packet carries an identity confirmation parameter;
a determining unit 602, configured to determine, according to the identity confirmation parameter, an identity type of a second Leaf device associated with the first Leaf device, where the identity type is a primary Leaf device or a standby Leaf device.
Further, the air conditioner is provided with a fan,
the receiving unit 601 is specifically configured to, when the notification packet is a priority notification packet, set the identity confirmation parameter as the priority of the second Leaf device.
Further, the air conditioner is provided with a fan,
the receiving unit 601 is specifically configured to, when the notification message is an abnormal notification message, determine that the identity confirmation parameter is an identifier of a main Leaf device that is abnormal;
the determining unit 602 is specifically configured to re-confirm the identity type of the second Leaf device associated with the first Leaf device according to the priority of the standby Leaf device associated with the first Leaf device.
Further, the apparatus further comprises:
the processing unit is specifically configured to receive a message sent by a first Leaf device when the identity type of the processing unit is determined to be the main Leaf device; and when the message is a broadcast message or a second unicast message, sending the message to a local user host and other Leaf devices, wherein the second unicast message is a unicast message of which the destination address does not hit a local forwarding table item, so that the other Leaf devices broadcast the message to the respective local user hosts.
Further, the apparatus further comprises:
the processing unit is specifically configured to receive, when it is determined that the identity type of the processing unit is the master Leaf device, a message sent by a Leaf device other than the first Leaf device; and when the message is a broadcast message or a second unicast message, sending the message to a local user host and the first Leaf device so that the first Leaf device broadcasts the message to the local user host, wherein the second unicast message is a unicast message of which the destination address does not hit a local forwarding table item.
Further, the apparatus further comprises:
the processing unit is specifically used for receiving a message sent by a local user host when the identity type of the processing unit is determined to be standby Leaf equipment; when the message is a broadcast message or a second unicast message, the message is sent to other Leaf devices except the first Leaf device, so that the other Leaf devices except the first Leaf device broadcast the message to respective local user hosts, and simultaneously, the main Leaf device sends the message to the first Leaf device, so that the first Leaf device broadcasts the message to the local user hosts, wherein the second unicast message is a unicast message of which the destination address does not hit a local forwarding table item.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and 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 modules can be selected according to actual needs to achieve the purpose of the scheme of the invention. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (22)
1. A method for implementing remote multi-homing networking is applied to a first branch Leaf device, and is characterized in that the method comprises the following steps:
determining a main Leaf device from remote second Leaf devices associated with the first Leaf device, and determining Leaf devices except the main Leaf device in the second Leaf devices as standby Leaf devices;
and sending an announcement message, wherein the announcement message carries an identity confirmation parameter, so that the second Leaf device confirms the identity type of the second Leaf device associated with the first Leaf device according to the identity confirmation parameter, and the identity type is a main Leaf device or a standby Leaf device.
2. The method as recited in claim 1, wherein determining a master Leaf device from among remote second Leaf devices associated with the first Leaf device comprises:
acquiring the priority of the associated second Leaf equipment;
and determining the main Leaf equipment according to the priority of the second Leaf equipment.
3. The method of claim 1, wherein:
and when the notification message is a priority notification message, the identity confirmation parameter is the priority of the second Leaf device, so that the second Leaf device confirms the identity type of the second Leaf device associated with the first Leaf device according to the priorities of all the second Leaf devices associated with the first Leaf device.
4. The method of claim 1, wherein:
and when the notification message is an abnormal notification message, the identity confirmation parameter is the identifier of the main Leaf device with the abnormal condition, so that the second Leaf device reconfirms the identity type of the second Leaf device associated with the first Leaf device according to the priority of the standby Leaf device associated with the first Leaf device.
5. The method of claim 1, wherein:
receiving a message sent by a local user host;
and when the message is a broadcast message or a first unicast message, forwarding the message to the main Leaf device, wherein the first unicast message is a unicast message of which the destination address does not hit a local forwarding table item, so that the main Leaf device sends the broadcast message to a local user host and other Leaf devices, or forwards the first unicast message according to a forwarding table item stored by the main Leaf device, wherein the first Leaf device does not store the forwarding table item matched with a remote user host.
6. A method for implementing remote multi-homing networking is applied to a second branch Leaf device, and is characterized in that the method comprises the following steps:
receiving an announcement message sent by a first Leaf device at a far end, wherein the first Leaf device is associated with at least two second Leaf devices, and the announcement message carries an identity confirmation parameter;
and determining the identity type of a second Leaf device associated with the first Leaf device according to the identity confirmation parameters, wherein the identity type is a main Leaf device or a standby Leaf device.
7. The method of claim 6, wherein:
and when the notification message is a priority notification message, the identity confirmation parameter is the priority of the second Leaf device.
8. The method of claim 6, wherein:
when the notification message is an abnormal notification message, the identity confirmation parameter is the identifier of the main Leaf device with the abnormal condition;
the determining the identity type of the second Leaf device associated with the first Leaf device according to the identity confirmation parameter includes:
and re-confirming the identity type of a second Leaf device associated with the first Leaf device according to the priority of the standby Leaf device associated with the first Leaf device.
9. The method of claim 6, wherein:
when the identity type of the device is determined to be the main Leaf device, receiving a message sent by the first Leaf device;
and when the message is a broadcast message or a second unicast message, sending the message to a local user host and other Leaf devices, wherein the second unicast message is a unicast message of which the destination address does not hit a local forwarding table item, so that the other Leaf devices broadcast the message to the respective local user hosts.
10. The method of claim 6, wherein the method further comprises:
when the identity type of the device is determined to be the main Leaf device, receiving messages sent by other Leaf devices except the first Leaf device;
and when the message is a broadcast message or a second unicast message, sending the message to a local user host and the first Leaf device so that the first Leaf device broadcasts the message to the local user host, wherein the second unicast message is a unicast message of which the destination address does not hit a local forwarding table item.
11. The method of claim 6, wherein:
when the identity type of the user is determined to be standby Leaf equipment, receiving a message sent by a local user host;
when the message is a broadcast message or a second unicast message, the message is sent to other Leaf devices except the first Leaf device, so that the other Leaf devices except the first Leaf device broadcast the message to respective local user hosts, and simultaneously, the main Leaf device sends the message to the first Leaf device, so that the first Leaf device broadcasts the message to the local user hosts, wherein the second unicast message is a unicast message of which the destination address does not hit a local forwarding table item.
12. An apparatus for implementing remote multi-homing networking, applied to a first branch Leaf device, the apparatus comprising:
a determining unit, configured to determine a master Leaf device from remote second Leaf devices associated with the first Leaf device, and determine Leaf devices other than the master Leaf device in the second Leaf devices as standby Leaf devices;
and the sending unit is used for sending an announcement message, wherein the announcement message carries an identity confirmation parameter so that the second Leaf device confirms the identity type of the second Leaf device associated with the first Leaf device according to the identity confirmation parameter, and the identity type is a main Leaf device or a standby Leaf device.
13. The apparatus of claim 12, wherein:
the determining unit is specifically configured to obtain a priority of the associated second Leaf device; and determining the main Leaf equipment according to the priority of the second Leaf equipment.
14. The apparatus of claim 12, wherein:
the sending unit is specifically configured to, when the notification packet is a priority notification packet, determine that the identity confirmation parameter is the priority of the second Leaf device, so that the second Leaf device confirms the identity type of the second Leaf device associated with the first Leaf device according to the priorities of all the second Leaf devices associated with the first Leaf device.
15. The apparatus of claim 12, wherein:
the sending unit is specifically configured to, when the notification packet is an abnormal notification packet, determine that the identity confirmation parameter is an identifier of a primary Leaf device that is abnormal, so that a second Leaf device reconfirms an identity type of a second Leaf device associated with the first Leaf device according to a priority of a standby Leaf device associated with the first Leaf device.
16. The apparatus of claim 12, wherein the apparatus further comprises:
the processing unit is used for receiving a message sent by the local user host; and when the message is a broadcast message or a first unicast message, forwarding the message to the main Leaf device, wherein the first unicast message is a unicast message of which the destination address does not hit a local forwarding table item, so that the main Leaf device sends the broadcast message to a local user host and other Leaf devices, or forwards the first unicast message according to a forwarding table item stored by the main Leaf device, wherein the first Leaf device does not store the forwarding table item matched with a remote user host.
17. An apparatus for implementing remote multi-homing networking, applied to a second branch Leaf device, the apparatus comprising:
a receiving unit, configured to receive an announcement message sent by a first Leaf device at a remote end, where the first Leaf device is associated with at least two second Leaf devices, and the announcement message carries an identity confirmation parameter;
and the determining unit is used for determining the identity type of a second Leaf device associated with the first Leaf device according to the identity confirmation parameter, wherein the identity type is a main Leaf device or a standby Leaf device.
18. The apparatus of claim 17, wherein:
the receiving unit is specifically configured to, when the notification packet is a priority notification packet, set the identity confirmation parameter as the priority of the second Leaf device.
19. The apparatus of claim 17, wherein:
the receiving unit is specifically configured to, when the notification message is an abnormal notification message, identify the identity confirmation parameter as an identifier of a main Leaf device that is abnormal;
the determining unit is specifically configured to re-confirm the identity type of the second Leaf device associated with the first Leaf device according to the priority of the standby Leaf device associated with the first Leaf device.
20. The apparatus of claim 17, wherein the apparatus further comprises:
the processing unit is specifically configured to receive a message sent by a first Leaf device when the identity type of the processing unit is determined to be the main Leaf device; and when the message is a broadcast message or a second unicast message, sending the message to a local user host and other Leaf devices, wherein the second unicast message is a unicast message of which the destination address does not hit a local forwarding table item, so that the other Leaf devices broadcast the message to the respective local user hosts.
21. The apparatus of claim 17, wherein the apparatus further comprises:
the processing unit is specifically configured to receive, when it is determined that the identity type of the processing unit is the master Leaf device, a message sent by a Leaf device other than the first Leaf device; and when the message is a broadcast message or a second unicast message, sending the message to a local user host and the first Leaf device so that the first Leaf device broadcasts the message to the local user host, wherein the second unicast message is a unicast message of which the destination address does not hit a local forwarding table item.
22. The apparatus of claim 17, wherein the apparatus further comprises:
the processing unit is specifically used for receiving a message sent by a local user host when the identity type of the processing unit is determined to be standby Leaf equipment; when the message is a broadcast message or a second unicast message, the message is sent to other Leaf devices except the first Leaf device, so that the other Leaf devices except the first Leaf device broadcast the message to respective local user hosts, and simultaneously, the main Leaf device sends the message to the first Leaf device, so that the first Leaf device broadcasts the message to the local user hosts, wherein the second unicast message is a unicast message of which the destination address does not hit a local forwarding table item.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610831322.XA CN106452992B (en) | 2016-09-19 | 2016-09-19 | Method and device for realizing remote multi-homing networking |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610831322.XA CN106452992B (en) | 2016-09-19 | 2016-09-19 | Method and device for realizing remote multi-homing networking |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106452992A CN106452992A (en) | 2017-02-22 |
| CN106452992B true CN106452992B (en) | 2020-02-11 |
Family
ID=58165539
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610831322.XA Active CN106452992B (en) | 2016-09-19 | 2016-09-19 | Method and device for realizing remote multi-homing networking |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106452992B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108600099B (en) * | 2018-04-19 | 2020-04-03 | 新华三技术有限公司 | Message forwarding method and device and leaf equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104410570A (en) * | 2014-12-16 | 2015-03-11 | 北京东土科技股份有限公司 | VRRP (virtual router redundancy protocol) based data transmission method and device |
| CN104580338A (en) * | 2013-10-29 | 2015-04-29 | 华为技术有限公司 | Service processing method, system and equipment |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20060098360A (en) * | 2003-08-19 | 2006-09-18 | 각고호우징 게이오기주크 | Wireless communication device, AD HOC system and communication system |
| CN100502400C (en) * | 2005-09-30 | 2009-06-17 | 华为技术有限公司 | Double-attach/multi-attach logical packet network method and supplier equipment |
| CN102143060B (en) * | 2010-12-23 | 2015-07-08 | 北京华为数字技术有限公司 | Method and device for building primary pseudowire and spare pseudowire |
| CN102281155A (en) * | 2011-08-01 | 2011-12-14 | 中兴通讯股份有限公司 | PTN-based PW switching method, and system and device thereof |
-
2016
- 2016-09-19 CN CN201610831322.XA patent/CN106452992B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104580338A (en) * | 2013-10-29 | 2015-04-29 | 华为技术有限公司 | Service processing method, system and equipment |
| CN104410570A (en) * | 2014-12-16 | 2015-03-11 | 北京东土科技股份有限公司 | VRRP (virtual router redundancy protocol) based data transmission method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106452992A (en) | 2017-02-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9369304B2 (en) | Subnet scoped multicast/broadcast packet distribution over a routed network | |
| US10050877B2 (en) | Packet forwarding method and apparatus | |
| JP5069356B2 (en) | Techniques for address resolution in data transmission networks. | |
| US20180287990A1 (en) | Layer 3 convergence for evpn link failure | |
| CN102859973B (en) | Method, apparatus and system for address resolution | |
| US8724583B2 (en) | Neighbor discovery message handling to support roaming of wireless mobile client devices | |
| WO2017114196A1 (en) | Packet processing method, related apparatus and nvo3 network system | |
| CN110798403B (en) | Communication method, communication device and communication system | |
| US20110032939A1 (en) | Network system, packet forwarding apparatus, and method of forwarding packets | |
| US9628435B2 (en) | Duplicate address detection based on distributed bloom filter | |
| US9866522B2 (en) | Method to control dynamic host configuration protocol pool exhaustion in dynamic network environments | |
| CN105812259A (en) | Packet forwarding method and device | |
| WO2015167462A1 (en) | Network re-convergence point | |
| CN105791072A (en) | Access method and device of Ethernet virtual network | |
| US9756148B2 (en) | Dynamic host configuration protocol release on behalf of a user | |
| CN107094110B (en) | DHCP message forwarding method and device | |
| US9893907B2 (en) | Managing multiple virtual area network memberships | |
| CN108337158B (en) | Unicast message forwarding method and device | |
| CN114465776B (en) | A flood attack defense method and related devices | |
| WO2017107871A1 (en) | Access control method and network device | |
| US9438475B1 (en) | Supporting relay functionality with a distributed layer 3 gateway | |
| CN110300057B (en) | Method, computer readable medium and provider edge device for agent advertisement | |
| US10530873B1 (en) | Techniques for optimizing EVPN-IRB for IPv6-enabled data centers with top-of-rack deployments | |
| CN106452992B (en) | Method and device for realizing remote multi-homing networking | |
| CN110620715B (en) | Virtual extended local area network communication method, tunnel endpoint and controller |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |