WO2015124041A1 - 虚拟子网中的主机路由处理方法及相关设备和通信系统 - Google Patents

虚拟子网中的主机路由处理方法及相关设备和通信系统 Download PDF

Info

Publication number
WO2015124041A1
WO2015124041A1 PCT/CN2015/070045 CN2015070045W WO2015124041A1 WO 2015124041 A1 WO2015124041 A1 WO 2015124041A1 CN 2015070045 W CN2015070045 W CN 2015070045W WO 2015124041 A1 WO2015124041 A1 WO 2015124041A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac address
virtual
source
address
packet
Prior art date
Application number
PCT/CN2015/070045
Other languages
English (en)
French (fr)
Inventor
徐小虎
张大成
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2016553302A priority Critical patent/JP6456398B2/ja
Priority to EP15751835.8A priority patent/EP3110087B1/en
Publication of WO2015124041A1 publication Critical patent/WO2015124041A1/zh
Priority to US15/242,087 priority patent/US10148568B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/741—Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6
    • 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/18—Loop-free operations
    • 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
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • 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/58—Association of routers
    • H04L45/586—Association of routers of virtual routers
    • 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/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • 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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a local host route processing method in a virtual subnet, and related devices and communication systems.
  • the carrier boundary (PE, Provider Edge) devices in the virtual subnet (VS) usually use a routing protocol of Layer 3 Virtual Private Network (L3VPN) to exchange local customer boundaries (CE, Customer Edge) Host routing, which in turn implements a subnet extension.
  • L3VPN Layer 3 Virtual Private Network
  • the PE device can record the local CE host information in the cache table of the address resolution protocol (ARP) or the neighbor discovery (ND, Neighbor Discovery) protocol to generate an IP address of the local CE host.
  • ARP address resolution protocol
  • ND neighbor discovery
  • the local CE host routes, and the local CE host routes are distributed to the virtual subnet based on the L3VPN routing protocol.
  • the other PE devices in the virtual subnet can learn the local CE host routes accordingly.
  • PE devices can be equipped with ARP or ND protocol proxy (Proxy) capabilities.
  • the PE device in the virtual subnet receives an ARP request packet from the local CE host for inquiring the MAC address of a remote CE host, if the PE device is currently If the CE host route corresponding to the IP address of the remote CE host is learned, the PE device can use the ARP response packet to return the virtual media access address (VMAC) of the PE device to the request.
  • VMAC virtual media access address
  • CE host routing loop There are multiple sites in the virtual subnet. In practice, it is often easy to form a CE host routing loop when multiple PE devices exist in a site of a virtual subnet. In the case of a CE host routing loop, the packet is usually increased. The length of the forwarding path may further affect the efficiency of transmitting data packets between CE hosts.
  • the embodiment of the present invention provides a method for processing a host route in a virtual subnet, and a related device and a communication system, so as to avoid forming a CE host routing loop in a scenario where multiple PE devices exist in some sites of the virtual subnet. Improve the efficiency of transmitting data packets between CE hosts.
  • the embodiment of the present invention provides the following technical solutions:
  • a first aspect of the embodiments of the present invention provides a method for processing a host route in a virtual subnet, including:
  • the first carrier border device receives the packet for address resolution, and the virtual subnet site where the first carrier border device is located further includes at least one second carrier border device;
  • the at least one of the following operations is performed: the local client boundary CE host routing entry corresponding to the source Internet Protocol IP address carried in the packet is saved, based on the third layer.
  • the routing protocol of the virtual private network VPN distributes the local CE host route corresponding to the IP address in the virtual subnet.
  • the method further includes:
  • the source MAC address is not a virtual MAC address, perform at least one of the following operations: saving a local CE host routing entry corresponding to the source IP address, and distributing the virtual host subnet in the virtual subnet based on the routing protocol The local CE host route corresponding to the IP address.
  • the method further includes:
  • At least one of the following operations is not performed: saving the local corresponding to the source IP address Distributing, by the CE host routing entry, a local CE host route corresponding to the IP address in the virtual subnet based on the routing protocol;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the whitelist, perform at least one of the following operations: saving the local corresponding to the source IP address
  • the CE host routing entry, the local CE host route corresponding to the IP address is distributed in the virtual subnet based on the routing protocol.
  • the method further includes:
  • the source MAC address is not a virtual MAC address, and the source MAC address is different from any one of the MAC addresses recorded in the blacklist, perform at least one of the following operations: saving the local corresponding to the source IP address Distributing, by the CE host routing entry, a local CE host route corresponding to the IP address in the virtual subnet based on the routing protocol;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the blacklist, at least one of the following operations is not performed: saving the source IP address corresponding to The local CE host routing entry, the local CE host route corresponding to the IP address is distributed in the virtual subnet based on the routing protocol.
  • Determining whether the source medium access control MAC address carried in the packet is a virtual MAC address includes: determining, if the source MAC address carried in the packet is equal to the virtual MAC address corresponding to the first carrier border device, determining The source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the first carrier border device, The source MAC address is not a virtual MAC address.
  • the virtual MAC address corresponding to the first carrier border device is specifically the first carrier border device The virtual MAC address corresponding to the associated virtual router.
  • Determining whether the source medium access control MAC address carried in the packet is a virtual MAC address includes:
  • Querying a virtual MAC address corresponding to the at least one second carrier border device if the source MAC address carried in the packet is equal to one of the at least one second carrier border device that is queried Determining, by the virtual MAC address corresponding to the quotient device, the source MAC address is a virtual MAC address; if the source MAC address carried in the packet is different from the queried at least one second carrier boundary device A virtual MAC address corresponding to a second carrier border device determines that the source MAC address is not a virtual MAC address.
  • the virtual MAC address corresponding to the second carrier border device is specifically the second carrier border device The virtual MAC address corresponding to the associated virtual router.
  • the packet is an address resolution protocol ARP packet or a neighbor discovery ND protocol packet.
  • a second aspect of the embodiments of the present invention provides a carrier border device, which may include:
  • a receiving unit configured to receive a packet for address resolution, where the virtual subnet site where the carrier border device is located further includes at least one second carrier border device;
  • a processing unit configured to determine whether the source media access control MAC address carried in the packet is a virtual MAC address; if the source MAC address is determined to be a virtual MAC address, do not perform at least one of the following operations: saving the The local client border CE host routing entry corresponding to the IP address of the source Internet Protocol protocol carried by the packet, and the routing protocol based on the Layer 3 virtual private network VPN distributes the local CE host route corresponding to the IP address in the virtual subnet.
  • the processing unit is further configured to: if it is determined that the source MAC address is not a virtual MAC address, perform at least one of the following operations: saving The local CE host routing entry corresponding to the source IP address, and the local CE host route corresponding to the IP address is distributed in the virtual subnet based on the routing protocol.
  • the processing unit is further configured to
  • At least one of the following operations is not performed: saving the local corresponding to the source IP address Distributing, by the CE host routing entry, a local CE host route corresponding to the IP address in the virtual subnet based on the routing protocol;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the whitelist, perform at least one of the following operations: saving the local corresponding to the source IP address
  • the CE host routing entry, the local CE host route corresponding to the IP address is distributed in the virtual subnet based on the routing protocol.
  • the processing unit is further configured to
  • the source MAC address is not a virtual MAC address, and the source MAC address is different from any one of the MAC addresses recorded in the blacklist, perform at least one of the following operations: saving the local corresponding to the source IP address Distributing, by the CE host routing entry, a local CE host route corresponding to the IP address in the virtual subnet based on the routing protocol;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the blacklist, at least one of the following operations is not performed: saving the source IP address corresponding to The local CE host routing entry, the local CE host route corresponding to the IP address is distributed in the virtual subnet based on the routing protocol.
  • the processing unit is specifically configured to: if the source MAC address carried in the packet is equal to the carrier border device, in the aspect of determining whether the source media access control MAC address carried in the packet is a virtual MAC address, And determining, by the corresponding virtual MAC address, the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the operator border device, determining that the source MAC address is not a virtual MAC address.
  • the virtual MAC address corresponding to the carrier border device is specifically the virtual router associated with the carrier border device.
  • the corresponding virtual MAC address is specifically the virtual router associated with the carrier border device.
  • the processing unit is configured to: query the virtual MAC address corresponding to the at least one second carrier border device, if the source media access control MAC address carried in the packet is a virtual MAC address, Determining that the source MAC address is virtual, if the source MAC address of the packet is the same as the virtual MAC address corresponding to one of the at least one second carrier border device. Determining the source if the source MAC address carried by the packet is different from the virtual MAC address corresponding to any one of the at least one second carrier border device that is queried The MAC address is not a virtual MAC address.
  • the virtual MAC address corresponding to the second carrier border device is specifically a virtual MAC address corresponding to the virtual router associated with the second carrier border device.
  • the packet is an address resolution protocol ARP packet or a neighbor discovery ND protocol packet.
  • a third aspect of the embodiments of the present invention provides a communication system, which may include:
  • a plurality of carrier border devices wherein at least one of the plurality of carrier border devices is any one of the operator border devices provided by the embodiment of the present invention.
  • the first PE device determines whether the source MAC address carried in the packet for address resolution is If the source MAC address is a virtual MAC address, the local CE host routing entry corresponding to the source IP address carried in the ARP packet is not saved, and/or the routing protocol not based on the Layer 3 VPN is in the virtual sub-address.
  • the local CE host route corresponding to the foregoing IP address is distributed in the network, where the virtual subnet site where the first PE device is located further includes at least one second PE device.
  • the packet used for address resolution with the source MAC address being the virtual MAC address is usually sent by the other PE device in the virtual subnet site where the first PE is located as the address resolution proxy. Therefore, the first PE device pair Whether the source MAC address carried in the received packet is a virtual MAC address for identification and confirmation, and whether the packet used for address resolution is another PE in the virtual subnet site where the first PE is located.
  • the identification of the situation that the device sends as the address resolution proxy, and corresponding to the situation ie, if the source MAC address is determined to be a virtual MAC address)
  • the first PE device does not save the source IP address carried in the packet used for address resolution.
  • the local CE host routing entry, and/or the routing protocol not based on the Layer 3 VPN distributes the local CE host route corresponding to the IP address in the virtual subnet, which is beneficial to eliminate the PE device pair error at the root source.
  • Storage and/or distribution of CE host routes In addition, in a scenario where multiple PE devices exist in some sites of the virtual subnet, the CE host routing loop is avoided as much as possible, thereby improving the efficiency of transmitting data packets between the CE hosts, thereby reducing the waste of network resources.
  • FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for processing a host route in a virtual subnet according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a method for processing a host route in another virtual subnet according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a method for processing a host route in another virtual subnet according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of a method for processing a host route in another virtual subnet according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of a method for processing a host route in another virtual subnet according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of a method for processing a host route in another virtual subnet according to an embodiment of the present disclosure
  • FIG. 8 is a schematic flowchart of a method for processing a host route in another virtual subnet according to an embodiment of the present disclosure
  • FIG. 9 is a schematic structural diagram of a PE device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another PE device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of another PE device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram of a communication system according to an embodiment of the present invention.
  • the embodiment of the present invention provides a method for processing a host route in a virtual subnet, and a related device and a communication system, so as to avoid forming a CE host routing loop in a scenario where multiple PE devices exist in some sites of the virtual subnet. Improve the efficiency of transmitting data packets between CE hosts.
  • FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention.
  • the virtual subnet site A includes PE device PE-1, PE device PE-2, switching device T1, CE host #001, and CE host #002, where CE host #001 and CE host# 002 is interconnected with the PE device PE-1 and the PE device PE-2 through the switching device T1.
  • Virtual subnet site B includes PE devices PE-4, switching device T2, and CE host #004, wherein CE host #004 is interconnected with PE device PE-4 through switching device T2.
  • the virtual subnet site C includes the PE device PE-3, the switching device T3, and the CE host #003.
  • the CE host #003 is interconnected by the switching device T3 and the PE device PE-3.
  • the PE device PE-1, the PE device PE-2, the PE device PE-3, and the PE device PE-4 are interconnected through an internetwork.
  • the switching device may be a switch or a hub.
  • a scenario in which the inventor of the present invention analyzes and forms a host routing loop is introduced.
  • the ND protocol scenario can be deduced by analogy.
  • PE-1 has the ARP Proxy function.
  • PE-1 has learned (for example, from PE-4) the CE host route corresponding to the IP address of CE host #004.
  • the PE-1 receives the ARP request packet from the local CE host #001 for inquiring the MAC address of the remote CE host #004
  • the PE-1 has learned the CE host corresponding to the IP address of the CE host #004. Therefore, the PE device can send an ARP response packet for responding to the ARP request packet as an ARP proxy to return the VMAC address corresponding to the virtual router associated with the PE-1 to the CE host through the ARP response packet.
  • 001 wherein the VMAC corresponding to PE-1 is used as the source MAC address of the above ARP response message).
  • the PE-2 can receive the ARP response packet.
  • the PE-2 directly stores the ARP response packet in the CE host routing entry.
  • the local CE host routing entry corresponding to the source IP address (where the source IP address is the IP address of the CE host #004) (that is, the PE-2 error is the default for the CE host #004 to be in the virtual subnet site. Local CE host within A).
  • the PE-2 may further distribute the local CE host route corresponding to the source IP address in the virtual subnet based on the routing protocol of the Layer 3 VPN. The behavior of the PE-2 distributing the local CE host route in the virtual subnet may be This allows other PE devices (such as PE-3, PE-5, etc.) to learn the wrong CE host route.
  • PE-2 cause the CE host routing loop to form, for example, PE-3 (assuming that the PE-3 learns the above-mentioned erroneous CE host route) may send the CE host #003 to the CE host #004 packet.
  • PE-2 forwards the packet to switching device T1 (due to PE-2 If the wrong local CE host routing entry is stored, the switching device T1 forwards the data packet to PE-1, and PE-1 forwards the data packet to PE-4, and PE-4 finally forwards the data packet to the CE host. #004, the packet has been turned to CE host #004.
  • the best path of the data packet is generally directly routed to PE-4 through PE-3 (without PE-1 and PE-2), and then quickly reach CE host #004. It can be seen that after the CE host routing loop is formed, the routing path length of the data packet is increased, which may greatly affect the efficiency of transmitting data packets between CE hosts.
  • the technical solution of the embodiment of the present invention focuses on how to avoid the formation of a CE host routing loop and shorten the forwarding path length of the data packets transmitted between the CE hosts in the scenario where multiple PE devices exist in some sites of the virtual subnet, thereby improving the length of the forwarding path of the data packets transmitted between the CE hosts.
  • the host route processing method in the virtual subnet may include: the first PE device receives the packet for address resolution, where the first PE device is located.
  • the subnet site further includes at least one second PE device; the first PE device determines whether the source media access control MAC address carried in the packet is a virtual MAC address; if the source MAC address is determined to be a virtual MAC address, the foregoing A PE device does not perform at least one of the following operations: storing a local CE host routing entry corresponding to the source Internet Protocol IP address carried in the packet, and a routing protocol based on the Layer 3 virtual private network VPN in the virtual subnet.
  • the local CE host route corresponding to the above IP address is distributed.
  • FIG. 2 is a schematic flowchart diagram of a method for processing a host route in a virtual subnet according to an embodiment of the present invention.
  • a host route processing method in a virtual subnet provided by an embodiment of the present invention may include the following contents:
  • the first PE device receives the packet for address resolution, where the virtual subnet site where the first PE device is located further includes at least one second PE device.
  • the packet received by the first PE device for address resolution may be from a certain second PE device, or may be from a certain CE in the virtual subnet site where the first PE device is located. device.
  • the packet used for address resolution may be an ARP packet or an ND protocol packet or other packet used for address resolution.
  • the first PE device determines whether the source MAC address carried in the packet is a virtual MAC address. If the source MAC address is determined to be a virtual MAC address, the method does not perform at least one of the following operations: saving the packet carrying the packet.
  • the local client boundary CE host routing entry corresponding to the IP address of the source network protocol, and the routing protocol based on the Layer 3 virtual private network VPN distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the ARP packet may be an ARP request packet or an ARP response packet.
  • the ND protocol message may be a Neighbor Solicitation (NS) message or a Neighbor Advertisement (NA) message.
  • the first PE device may not save the ARP entry or the ND protocol entry, where the ARP entry records the mapping between the source IP address and the source MAC address carried in the ARP packet. relationship. The mapping relationship between the source IP address and the source MAC address carried in the ND protocol packet is recorded in the ND protocol entry.
  • the first PE device determines whether the source MAC address carried in the packet for address resolution is If the source MAC address is a virtual MAC address, the local CE host routing entry corresponding to the source IP address carried in the ARP packet is not saved, and/or the routing protocol not based on the Layer 3 VPN is in the virtual sub-address.
  • the local CE host route corresponding to the foregoing IP address is distributed in the network, where the virtual subnet site where the first PE device is located further includes at least one second PE device.
  • the packet used for address resolution with the source MAC address being the virtual MAC address is usually sent by the other PE device in the virtual subnet site where the first PE is located as the address resolution proxy. Therefore, the first PE device pair Whether the source MAC address carried in the received packet is a virtual MAC address for identification and confirmation, and whether the packet used for address resolution is another PE in the virtual subnet site where the first PE is located.
  • the identification of the situation that the device sends as the address resolution proxy, and corresponding to the situation ie, if the source MAC address is determined to be a virtual MAC address)
  • the first PE device does not save the source IP address carried in the packet used for address resolution.
  • Corresponding local CE host routing entries, and/or routing protocols not based on Layer 3 VPNs distribute the local CE host routes corresponding to the foregoing IP addresses among the virtual subnets, In this way, it is advantageous to eliminate the storage and/or distribution of the faulty CE host route by the PE device at the root source, thereby facilitating the formation of a CE host routing loop in a scenario where multiple PE devices exist in some sites of the virtual subnet. In turn, the efficiency of transmitting data packets between CE hosts is improved, thereby reducing the waste of network resources.
  • the virtual MAC address corresponding to the PE device may be a virtual MAC address corresponding to the virtual router associated with the PE device.
  • the local CE host routing entry saved by the PE device points to the CE host within the site where the PE device is located.
  • the local CE host route distributed by the PE device points to the CE host within the site where the PE device is located.
  • the local CE host routing entry saved by the PE device may include an IP address and a next hop address of the CE host.
  • the local CE host route distributed by the PE device may include an IP address and a next hop address of the CE host.
  • the method for processing a host route in the virtual subnet may further include: if it is determined that the source MAC address is not a virtual MAC address, the first PE device may perform at least one of the following operations: The local CE host routing entry corresponding to the source IP address is saved, and the local CE host route corresponding to the IP address is distributed in the virtual subnet based on the routing protocol of the Layer 3 VPN.
  • the method for processing the host route in the virtual subnet may further include: if it is determined that the source MAC address is not a virtual MAC address, and the source MAC address is different from any one recorded in the whitelist.
  • the first PE device may not perform at least one of the following operations: storing a local CE host routing entry corresponding to the source IP address, and distributing the IP address in the virtual subnet based on the routing protocol of the Layer 3 VPN. Corresponding local CE host route.
  • the first PE device may perform at least one of the following operations: saving the foregoing
  • the local CE host routing entry corresponding to the source IP address and the routing protocol based on the Layer 3 VPN are distributed in the virtual subnet. Local CE host route corresponding to the address.
  • the introduction of the whitelist control mechanism further facilitates more flexible implementation of route distribution control.
  • the first PE device may further update the whitelist according to the instruction.
  • the method for processing the host route in the virtual subnet may further include: if it is determined that the source MAC address is not a virtual MAC address, and the source MAC address is different from any one recorded in the blacklist.
  • a MAC address the first PE device may perform at least one of the following operations: storing a local CE host routing entry corresponding to the source IP address, and distributing the local address corresponding to the IP address in the virtual subnet based on the routing protocol CE host route.
  • the first PE device may not perform at least one of the following operations: saving the foregoing The local CE host routing entry corresponding to the source IP address, and the local CE host route corresponding to the IP address is distributed in the virtual subnet based on the routing protocol.
  • the introduction of the blacklist control mechanism further facilitates more flexible implementation of route distribution control.
  • the first PE device may further update the blacklist according to the instruction.
  • the determining whether the source media access control MAC address carried in the packet is a virtual MAC address may include: if the source MAC address carried in the packet is equal to the virtuality corresponding to the first PE device The MAC address may determine that the source MAC address is a virtual MAC address. If the source MAC address is different from the virtual MAC address corresponding to the first PE device, the source MAC address may be determined to be not a virtual MAC address.
  • the example in this example is as follows: For example, each PE device in the same virtual subnet site corresponds to the same virtual MAC address (that is, each PE device in the same virtual subnet site is associated with the same virtual router).
  • the determining whether the source medium access control MAC address carried in the packet is a virtual MAC address may include: the first PE device querying the foregoing Having a virtual MAC address corresponding to the second PE device, if the source MAC address carried in the packet is equal to the virtual MAC address corresponding to one of the at least one second PE device, Determining that the source MAC address is a virtual MAC address; if the source MAC address carried in the packet is different from the virtual MAC address corresponding to any one of the at least one second PE device that is queried, the source is determined.
  • the MAC address is not a virtual MAC address.
  • the foregoing first PE device may also determine, by other manners, whether the source medium access control MAC address carried in the packet is a virtual MAC address.
  • FIG. 3 is a schematic flowchart diagram of a method for processing a host route in a virtual subnet according to another embodiment of the present invention.
  • a host route processing method in a virtual subnet provided by another embodiment of the present invention may include the following contents:
  • the CE host #001 sends an ARP request message q11 for requesting the MAC address of the CE host #004.
  • the ARP request packet q11 carries the IP address (ie, the source IP address) and the MAC address (that is, the source MAC address) of the CE host #001, and the ARP request packet q11 also carries the IP address of the CE host #004.
  • the PE-1 receives the ARP request packet q11.
  • the PE-1 has learned the CE host route corresponding to the CE host #004 through the PE-4. Therefore, the PE-1 can serve as an ARP proxy and send an ARP response packet q12 for responding to the ARP request packet q11.
  • the source MAC address of the ARP response packet q12 is the virtual MAC address corresponding to the virtual router associated with the PE-1, and the source IP address of the ARP response packet q12 is the IP address of the CE host #004.
  • the switching device T1 floods the received ARP response packet q12.
  • PE-2 and CE host #001 will receive the above ARP response message q12.
  • the PE-2 determines whether the source MAC address carried in the ARP response packet q12 is a virtual MAC address.
  • the PE-2 determines that the source MAC address of the ARP response packet q12 is a virtual MAC address, the PE-2 does not perform at least one of the following operations: storing the source IP address carried in the ARP response packet q12.
  • the local CE host routing entry and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 determines that the source MAC address of the ARP response packet q12 is not a virtual MAC address, the PE-2 performs at least one of the following operations: saving the source IP address carried by the ARP response packet q12.
  • the local CE host routing entry and the routing protocol based on the Layer 3 VPN distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the determining, by the PE-2, whether the source MAC address carried in the ARP response packet q12 is a virtual MAC address may include: if the source MAC address carried in the ARP response packet q12 is equal to the PE-2 association.
  • the virtual MAC address corresponding to the virtual router the PE-2 may determine that the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the virtual router associated with the PE-2, the PE-2 determines The above source MAC address is not a virtual MAC address. In this scenario, it is assumed that each PE device in the same virtual subnet site is associated with the same virtual router as an example.
  • the PE-2 determines whether the source medium access control MAC address carried in the ARP response packet q12 is a virtual MAC address, and may include: the PE-2 querying the virtual router associated with the PE-1.
  • the virtual MAC address if the source MAC address carried in the ARP response packet q12 is the same as the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine the source carried by the ARP response packet q12.
  • the MAC address is a virtual MAC address. If the source MAC address of the ARP response packet q12 is different from the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 can determine that the ARP response packet is carried.
  • the source MAC address is not a virtual MAC address.
  • the foregoing PE-2 may also determine, by other means, whether the source medium access control MAC address carried by the ARP response packet q12 is a virtual MAC address.
  • the PE-2 determines whether the source MAC address carried in the ARP packet is a virtual MAC address; If the MAC address is a virtual MAC address, the PE-2 does not store the local CE host routing entry corresponding to the source IP address carried in the ARP response packet, and/or the PE-2 does not use the routing protocol based on the Layer 3 VPN in the virtual sub-node.
  • the local CE host route corresponding to the source IP address is distributed in the network, where at least one other PE device is included in the virtual subnet site where the PE-2 is located.
  • the ARP response packet with the source MAC address being the virtual MAC address is usually sent by the other PE device in the virtual subnet site where the PE-2 is located as the ARP proxy. Therefore, the PE-2 responds to the received ARP. Whether the source MAC address carried in the packet is a virtual MAC address for identification, and whether the ARP response packet is sent by the other PE device in the virtual subnet site where the PE-2 is located as an ARP proxy.
  • the PE-2 determines that the source MAC address is a virtual MAC address, the PE-2 does not save the local CE host routing entry corresponding to the source IP address carried in the ARP packet, and/or is not based on The routing protocol of the Layer 3 VPN distributes the local CE host route corresponding to the source IP address in the virtual subnet, so that the PE device can save (use) and/or distribute the incorrect CE host route at the root source.
  • the CE host routing loop is avoided as much as possible, thereby improving the efficiency of transmitting data packets between the CE hosts and reducing the waste of network resources.
  • FIG. 4 is a schematic flowchart diagram of a method for processing a host route in a virtual subnet according to another embodiment of the present invention.
  • a host route processing method in a virtual subnet provided by another embodiment of the present invention may include the following contents:
  • the PE-1 functions as the ARP Proxy, and the proxy CE host #004 sends an ARP request packet q21.
  • the source IP address of the ARP request packet q21 is the IP address of the CE host #004. It is assumed that the PE-1 has learned the CE host route corresponding to the CE host #004. Therefore, the source MAC address carried in the ARP request packet q21 can be the virtual MAC address corresponding to the PE-1.
  • the switching device T1 floods the received ARP request message q21.
  • the PE-2 will receive the above ARP request message q21.
  • the PE-2 determines whether the source MAC address carried in the ARP request packet q21 is a virtual MAC address.
  • the source MAC address carried in the ARP request packet q21 is a virtual MAC.
  • the address of the PE-2 does not perform at least one of the following operations: the local CE host routing entry corresponding to the source IP address carried in the ARP request packet q21, and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol).
  • the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet.
  • the PE-2 determines that the source MAC address of the ARP request packet q21 is not a virtual MAC address, the PE-2 performs at least one of the following operations: saving the local CE corresponding to the source IP address carried in the ARP request packet q21.
  • the host routing entry and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • determining whether the source MAC address carried in the ARP request packet q21 is a virtual MAC address may include: if the source MAC address carried in the ARP request packet q21 is equal to the PE-2 association.
  • the virtual MAC address corresponding to the virtual router the PE-2 may determine that the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the virtual router associated with the PE-2, the PE-2 determines The above source MAC address is not a virtual MAC address. In this scenario, it is assumed that each PE device in the same virtual subnet site is associated with the same virtual router as an example.
  • the PE-2 determines whether the source media access control MAC address carried in the ARP request packet q21 is a virtual MAC address, and may include: the PE-2 querying the virtual router associated with the PE-1.
  • the virtual MAC address if the source MAC address carried in the ARP request packet q21 is the same as the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine the source carried by the ARP request packet q21.
  • the MAC address is a virtual MAC address. If the source MAC address of the ARP request packet q21 is different from the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine that the ARP request packet q21 is carried.
  • the source MAC address is not a virtual MAC address.
  • the foregoing PE-2 may determine, by other means, whether the source medium access control MAC address carried by the ARP request packet q21 is a virtual MAC address.
  • the PE-2 determines whether the source MAC address carried in the ARP packet is a virtual MAC address, and if the source MAC address is determined to be The virtual MAC address does not store the source IP address carried in the ARP request packet.
  • the local CE host routing entry corresponding to the address, and/or the PE-2 does not distribute the local CE host route corresponding to the source IP address in the virtual subnet without using the routing protocol of the Layer 3 VPN, where the PE-2 is located At least one other PE device is also included in the virtual subnet site.
  • the ARP request packet with the source MAC address being the virtual MAC address is usually sent by the other PE device in the virtual subnet site where the PE-2 is located as the ARP proxy. Therefore, the PE-2 receives the received ARP request. Whether the source MAC address carried in the packet is a virtual MAC address for identification, and whether the ARP request packet is sent by the other PE device in the virtual subnet site where the PE-2 is located as an ARP proxy.
  • the PE-2 determines that the source MAC address is a virtual MAC address, the PE-2 does not save the local CE host routing entry corresponding to the source IP address carried in the ARP packet, and/or is not based on The routing protocol of the Layer 3 VPN distributes the local CE host route corresponding to the source IP address in the virtual subnet, so that the PE device can save (use) and/or distribute the incorrect CE host route at the root source.
  • the CE host routing loop is avoided as much as possible, thereby improving the efficiency of transmitting data packets between the CE hosts and reducing the waste of network resources.
  • FIG. 5 is a schematic flowchart of a method for processing a host route in a virtual subnet according to another embodiment of the present invention.
  • a host route processing method in a virtual subnet provided by another embodiment of the present invention may include the following contents:
  • the CE host #002 sends an ARP request message q31 for requesting the MAC address of the CE host #004.
  • the ARP request packet q31 carries the IP address (ie, the source IP address) and the MAC address (that is, the source MAC address) of the CE host #002, and the ARP request packet q31 also carries the IP address of the CE host #004.
  • the switching device T1 floods the received ARP request packet q31.
  • PE-1 and PE-2 will receive the above ARP request message q31.
  • the PE-2 determines whether the source MAC address carried in the ARP request packet q31 is a virtual MAC address.
  • the PE-2 determines that the source MAC address of the ARP request packet q31 is a virtual MAC address, the PE-2 does not perform at least one of the following operations: saving the ARP request packet q31.
  • the local CE host routing entry corresponding to the source IP address and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 determines that the source MAC address of the ARP request packet q31 is not a virtual MAC address, the PE-2 performs at least one of the following operations: saving the local CE corresponding to the source IP address carried in the ARP request packet q31.
  • the host routing entry and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the determining, by the PE-2, whether the source MAC address carried in the ARP request packet q31 is a virtual MAC address may include: if the source MAC address carried in the ARP request packet q31 is equal to the PE-2 association.
  • the virtual MAC address corresponding to the virtual router the PE-2 may determine that the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the virtual router associated with the PE-2, the PE-2 determines The above source MAC address is not a virtual MAC address. In this scenario, it is assumed that each PE device in the same virtual subnet site is associated with the same virtual router as an example.
  • the PE-2 determines whether the source media access control MAC address carried in the ARP request packet q31 is a virtual MAC address, and may include: the PE-2 querying the virtual router associated with the PE-1.
  • the virtual MAC address if the source MAC address carried in the ARP request packet q31 is the same as the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine the source carried in the ARP request packet q31.
  • the MAC address is a virtual MAC address. If the source MAC address of the ARP request packet q31 is different from the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine that the ARP request packet q31 is carried.
  • the source MAC address is not a virtual MAC address.
  • the foregoing PE-2 may also determine, by other means, whether the source medium access control MAC address carried by the ARP request packet q31 is a virtual MAC address.
  • the PE-1 receives the ARP request packet q31.
  • the PE-1 has learned the CE host route corresponding to the CE host #004 through the PE-4. Therefore, the PE-1 can serve as an ARP proxy and send an ARP response packet q32 for responding to the ARP request packet q31.
  • the source MAC address carried in the ARP response packet q32 is the virtual MAC address corresponding to the virtual router associated with the PE-1, and the ARP response.
  • the source IP address carried in the packet q32 is the IP address of the CE host #004.
  • the switching device T1 floods the received ARP response packet q32.
  • the PE-2 and CE host #002 will receive the above ARP response message q32.
  • the PE-2 determines whether the source MAC address carried in the ARP response packet q32 is a virtual MAC address.
  • the PE-2 determines that the source MAC address of the ARP response packet q32 is a virtual MAC address, the PE-2 does not perform at least one of the following operations: storing the source IP address carried by the ARP response packet q32.
  • the local CE host routing entry and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 determines that the source MAC address of the ARP response packet q32 is not a virtual MAC address, the PE-2 performs at least one of the following operations: saving the local CE corresponding to the source IP address carried in the ARP response packet q32.
  • the host routing entry and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the determining, by the PE-2, whether the source MAC address carried in the ARP request packet q31 is a virtual MAC address may include: if the source MAC address carried in the ARP request packet q31 is equal to the PE-2 association.
  • the virtual MAC address corresponding to the virtual router the PE-2 may determine that the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the virtual router associated with the PE-2, the PE-2 determines The above source MAC address is not a virtual MAC address. In this scenario, it is assumed that each PE device in the same virtual subnet site is associated with the same virtual router as an example.
  • the PE-2 determines whether the source media access control MAC address carried in the ARP response packet q32 is a virtual MAC address, and may include: the PE-2 querying the virtual router associated with the PE-1.
  • the virtual MAC address if the source MAC address carried in the ARP response packet q32 is the same as the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine the source carried in the ARP response packet q32.
  • the MAC address is a virtual MAC address.
  • the PE-2 can determine The source MAC address carried in the ARP response packet q32 is not a virtual MAC address.
  • the foregoing PE-2 may also determine, by other means, whether the source medium access control MAC address carried by the ARP response packet q32 is a virtual MAC address.
  • the PE-2 determines whether the source MAC address carried in the ARP packet is a virtual MAC address; if the source MAC address is determined to be virtual
  • the MAC address does not store the local CE host routing entry corresponding to the source IP address carried in the ARP packet, and/or the PE-2 does not distribute the source in the virtual subnet based on the routing protocol of the Layer 3 VPN.
  • the local CE host route corresponding to the IP address, wherein the virtual subnet site where the PE-2 is located further includes at least one other PE device.
  • the PE-2 carries the received ARP packet. Whether the source MAC address is identified and confirmed by the virtual MAC address, and the identification of the case where the ARP packet is sent by the other PE device in the virtual subnet site where the PE-2 is located is used as the ARP proxy, and the corresponding The situation is that the PE-2 determines that the source MAC address is a virtual MAC address.
  • the PE-2 does not store the local CE host routing entry corresponding to the source IP address carried in the ARP packet, and/or the route that is not based on the Layer 3 VPN.
  • the protocol distributes the local CE host route corresponding to the source IP address in the virtual subnet, so that the PE device can save (use) and/or distribute the wrong CE host route at the root source, thereby facilitating the virtual
  • the CE host routing loop is avoided as much as possible. This improves the efficiency of transmitting data packets between CE hosts and reduces the waste of network resources.
  • FIG. 6 is a schematic flowchart diagram of a method for processing a host route in a virtual subnet according to another embodiment of the present invention.
  • a method for processing a host route in a virtual subnet according to another embodiment of the present invention may include the following contents:
  • the CE host #001 sends an ARP request message q11 for requesting to obtain the MAC address of the CE host #004.
  • the ARP request packet q11 carries the IP address (ie, the source IP address) and the MAC address (that is, the source MAC address) of the CE host #001, and the ARP request packet q11 also carries the IP address of the CE host #004.
  • the PE-1 receives the ARP request packet q11.
  • the PE-1 has learned the CE host route corresponding to the CE host #004 through the PE-4. Therefore, the PE-1 can serve as an ARP proxy and send an ARP response packet q12 for responding to the ARP request packet q11.
  • the source MAC address of the ARP response packet q12 is the virtual MAC address corresponding to the virtual router associated with the PE-1, and the source IP address of the ARP response packet q12 is the IP address of the CE host #004.
  • the switching device T1 floods the received ARP response packet q12.
  • PE-2 and CE host #001 will receive the above ARP response message q12.
  • the PE-2 determines whether the source MAC address carried in the ARP response packet q12 is a virtual MAC address.
  • step 605 is performed.
  • the PE-2 determines that the source MAC address of the ARP response packet q12 is a virtual MAC address, the PE-2 does not perform at least one of the following operations: storing the source IP address carried in the ARP response packet q12.
  • the local CE host routing entry and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 determines whether the source MAC address carried in the ARP response packet q12 is different from any MAC address recorded in the whitelist. address.
  • the PE-2 may perform at least one of the following operations: saving the local source corresponding to the source IP address.
  • the CE host routing entry and the routing protocol based on the Layer 3 VPN distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 may perform at least one of the following operations: saving the corresponding source IP address.
  • the introduction of the whitelist control mechanism further facilitates more flexible implementation of route distribution control.
  • the above PE-2 may also enter the white list according to the instruction. Line updates.
  • determining whether the source MAC address carried in the ARP request packet q21 is a virtual MAC address may include: if the source MAC address carried in the ARP request packet q21 is equal to the PE-2 association.
  • the virtual MAC address corresponding to the virtual router the PE-2 may determine that the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the virtual router associated with the PE-2, the PE-2 determines The above source MAC address is not a virtual MAC address. In this scenario, it is assumed that each PE device in the same virtual subnet site is associated with the same virtual router as an example.
  • the PE-2 determines whether the source media access control MAC address carried in the ARP request packet q21 is a virtual MAC address, and may include: the PE-2 querying the virtual router associated with the PE-1.
  • the virtual MAC address if the source MAC address carried in the ARP request packet q21 is the same as the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine the source carried by the ARP request packet q21.
  • the MAC address is a virtual MAC address. If the source MAC address of the ARP request packet q21 is different from the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine that the ARP request packet q21 is carried.
  • the source MAC address is not a virtual MAC address.
  • the PE-2 may determine whether the source MAC address carried in the ARP request packet q21 is a virtual MAC address by using other methods.
  • the PE-2 determines whether the source MAC address carried in the ARP packet is a virtual MAC address; if the source MAC address is determined to be The virtual MAC address does not store the local CE host routing entry corresponding to the source IP address carried in the ARP response packet, and/or the PE-2 does not distribute the routing protocol based on the Layer 3 VPN in the virtual subnet.
  • the local CE host route corresponding to the source IP address, wherein the virtual subnet site where the PE-2 is located further includes at least one other PE device.
  • the ARP response packet with the source MAC address being the virtual MAC address is usually sent by the other PE device in the virtual subnet site where the PE-2 is located as the ARP proxy. Therefore, the PE-2 responds to the received ARP. Whether the source MAC address carried in the packet is a virtual MAC address for identification and confirmation, thereby implementing ARP Whether the response message is an identifier of a situation in which another PE device in the virtual subnet site where the PE-2 is located is sent as an ARP proxy, and corresponds to the case (ie, if the PE-2 determines that the source MAC address is a virtual MAC address) The PE-2 does not store the local CE host routing entry corresponding to the source IP address carried in the ARP packet, and/or the routing protocol corresponding to the Layer 3 VPN does not distribute the source IP address in the virtual subnet.
  • the CE host routing loop is avoided, which improves the efficiency of transmitting data packets between CE hosts and reduces the waste of network resources.
  • FIG. 7 is a schematic flowchart diagram of a method for processing a host route in a virtual subnet according to another embodiment of the present invention.
  • a host route processing method in a virtual subnet provided by another embodiment of the present invention may include the following contents:
  • the PE-1 functions as the ARP Proxy, and the proxy CE host #004 sends an ARP request packet q21.
  • the source IP address of the ARP request packet q21 is the IP address of the CE host #004. It is assumed that the PE-1 has learned the CE host route corresponding to the CE host #004. Therefore, the source MAC address carried in the ARP request packet q21 can be the virtual MAC address corresponding to the PE-1.
  • the switching device T1 floods the received ARP request message q21.
  • the PE-2 will receive the above ARP request message q21.
  • the PE-2 determines whether the source MAC address carried in the ARP request packet q21 is a virtual MAC address.
  • step 704 is performed.
  • the PE-2 determines that the source MAC address of the ARP request packet q21 is a virtual MAC address, the PE-2 does not perform at least one of the following operations: storing the source IP address carried by the ARP request packet q21.
  • the local CE host routing entry and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 determines whether the source MAC address carried in the ARP request packet q21 is different from any MAC address recorded in the whitelist. address.
  • the PE-2 may perform at least one of the following operations: saving the local source corresponding to the source IP address.
  • the CE host routing entry and the routing protocol based on the Layer 3 VPN distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 may perform at least one of the following operations: saving the corresponding source IP address.
  • the introduction of the whitelist control mechanism further facilitates more flexible implementation of route distribution control.
  • the PE-2 may further update the white list according to the instruction.
  • determining whether the source MAC address carried in the ARP request packet q21 is a virtual MAC address may include: if the source MAC address carried in the ARP request packet q21 is equal to the PE-2 association.
  • the virtual MAC address corresponding to the virtual router the PE-2 may determine that the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the virtual router associated with the PE-2, the PE-2 determines The above source MAC address is not a virtual MAC address. In this scenario, it is assumed that each PE device in the same virtual subnet site is associated with the same virtual router as an example.
  • the PE-2 determines whether the source media access control MAC address carried in the ARP request packet q21 is a virtual MAC address, and may include: the PE-2 querying the virtual router associated with the PE-1.
  • the virtual MAC address if the source MAC address carried in the ARP request packet q21 is the same as the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine the source carried by the ARP request packet q21.
  • the MAC address is a virtual MAC address. If the source MAC address of the ARP request packet q21 is different from the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine that the ARP request packet q21 is carried.
  • the source MAC address is not a virtual MAC address.
  • the foregoing PE-2 may also determine the foregoing ARP request packet by other means. Whether the source MAC address carried in q21 is a virtual MAC address.
  • the PE-2 determines whether the source MAC address carried in the ARP packet is a virtual MAC address, and if the source MAC address is determined to be The virtual MAC address does not store the local CE host routing entry corresponding to the source IP address carried in the ARP request packet, and/or the PE-2 does not distribute the routing table based on the Layer 3 VPN in the virtual subnet.
  • the local CE host route corresponding to the source IP address, wherein the virtual subnet site where the PE-2 is located further includes at least one other PE device.
  • the ARP request packet with the source MAC address being the virtual MAC address is usually sent by the other PE device in the virtual subnet site where the PE-2 is located as the ARP proxy. Therefore, the PE-2 receives the received ARP request. Whether the source MAC address carried in the packet is a virtual MAC address for identification, and whether the ARP request packet is sent by the other PE device in the virtual subnet site where the PE-2 is located as an ARP proxy.
  • the PE-2 determines that the source MAC address is a virtual MAC address, the PE-2 does not save the local CE host routing entry corresponding to the source IP address carried in the ARP packet, and/or is not based on The routing protocol of the Layer 3 VPN distributes the local CE host route corresponding to the source IP address in the virtual subnet, so that the PE device can save (use) and/or distribute the incorrect CE host route at the root source.
  • the CE host routing loop is avoided as much as possible, thereby improving the efficiency of transmitting data packets between the CE hosts and reducing the waste of network resources.
  • FIG. 8 is a schematic flowchart of a method for processing a host route in a virtual subnet according to another embodiment of the present invention.
  • a host route processing method in a virtual subnet provided by another embodiment of the present invention may include the following contents:
  • the CE host #002 sends an ARP request message q31 for requesting to obtain the MAC address of the CE host #004.
  • the ARP request packet q31 carries the IP address (ie, the source IP address) and the MAC address (that is, the source MAC address) of the CE host #002, and the ARP request packet q31 also carries the IP address of the CE host #004.
  • the switching device T1 floods the received ARP request message q31.
  • PE-1 and PE-2 will receive the above ARP request message q31.
  • the PE-2 determines whether the source MAC address carried in the ARP request packet q31 is a virtual MAC address.
  • step 804 is performed.
  • the PE-2 determines that the source MAC address of the ARP request packet q31 is a virtual MAC address, the PE-2 does not perform at least one of the following operations: storing the source IP address carried by the ARP request packet q31.
  • the local CE host routing entry and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 determines whether the source MAC address carried in the ARP request packet q31 is different from any MAC address recorded in the whitelist. address,
  • the PE-2 may perform at least one of the following operations: saving the local source corresponding to the source IP address.
  • the CE host routing entry and the routing protocol based on the Layer 3 VPN distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 may perform at least one of the following operations: saving the corresponding source IP address.
  • the introduction of the whitelist control mechanism further facilitates more flexible implementation of route distribution control.
  • the PE-2 may further update the white list according to the instruction.
  • the determining, by the PE-2, whether the source MAC address carried in the ARP request packet q31 is a virtual MAC address may include: if the source MAC address carried in the ARP request packet q31 is equal to the PE-2 association.
  • the virtual MAC address corresponding to the virtual router the PE-2 may determine that the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the virtual router associated with the PE-2, the PE-2 determines
  • the above source MAC address is not a virtual MAC address. This scenario is mainly assumed to be within the same virtual subnet site.
  • Each PE device is associated with the same virtual router as an example.
  • the PE-2 determines whether the source media access control MAC address carried in the ARP request packet q31 is a virtual MAC address, and may include: the PE-2 querying the virtual router associated with the PE-1.
  • the virtual MAC address if the source MAC address carried in the ARP request packet q31 is the same as the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine the source carried in the ARP request packet q31.
  • the MAC address is a virtual MAC address. If the source MAC address of the ARP request packet q31 is different from the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine that the ARP request packet q31 is carried.
  • the source MAC address is not a virtual MAC address.
  • the foregoing PE-2 may also determine, by other means, whether the source medium access control MAC address carried by the ARP request packet q31 is a virtual MAC address.
  • the PE-1 receives the ARP request packet q31.
  • the PE-1 has learned the CE host route corresponding to the CE host #004 through the PE-4. Therefore, the PE-1 can serve as an ARP proxy and send an ARP response packet q32 for responding to the ARP request packet q31.
  • the source MAC address of the ARP response packet q32 is the virtual MAC address corresponding to the virtual router associated with the PE-1, and the source IP address of the ARP response packet q32 is the IP address of the CE host #004.
  • the switching device T1 floods the received ARP response packet q32.
  • the PE-2 and CE host #002 will receive the above ARP response message q32.
  • the PE-2 determines whether the source MAC address carried in the ARP response packet q32 is a virtual MAC address.
  • step 808 is performed.
  • the PE-2 determines that the source MAC address of the ARP request packet q31 is a virtual MAC address, the PE-2 does not perform at least one of the following operations: storing the source IP address carried by the ARP request packet q31.
  • the local CE host routing entry and the routing protocol based on the Layer 3 VPN (such as the gateway border protocol) distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 determines whether the source MAC address carried in the ARP response packet q32 is different. Any 1 MAC address recorded in the whitelist.
  • the PE-2 may perform at least one of the following operations: saving the local source corresponding to the source IP address.
  • the CE host routing entry and the routing protocol based on the Layer 3 VPN distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the PE-2 may perform at least one of the following operations: saving the corresponding source IP address.
  • determining whether the source MAC address carried by the ARP response packet q32 is a virtual MAC address may include: if the source MAC address carried in the ARP response packet q32 is equal to the PE-2 association.
  • the virtual MAC address corresponding to the virtual router the PE-2 may determine that the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the virtual router associated with the PE-2, the PE-2 determines The above source MAC address is not a virtual MAC address. In this scenario, it is assumed that each PE device in the same virtual subnet site is associated with the same virtual router as an example.
  • the PE-2 determines whether the source media access control MAC address carried in the ARP response packet q32 is a virtual MAC address, and may include: the PE-2 querying the virtual router associated with the PE-1.
  • the virtual MAC address if the source MAC address carried in the ARP response packet q32 is the same as the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 may determine the source carried in the ARP response packet q32.
  • the MAC address is a virtual MAC address. If the source MAC address of the ARP response packet q32 is different from the virtual MAC address corresponding to the virtual router associated with the PE-1, the PE-2 can determine that the ARP response packet is carried.
  • the source MAC address is not a virtual MAC address.
  • the PE-2 may determine whether the source MAC address carried in the ARP response packet q32 is a virtual MAC address by using other methods.
  • the PE-2 after the PE-2 receives the ARP packet, the PE-2 first The source MAC address of the ARP packet is a virtual MAC address. If the source MAC address is a virtual MAC address, the PE-2 does not save the local CE host routing entry corresponding to the source IP address carried in the ARP packet. And/or the PE-2 does not distribute the local CE host route corresponding to the source IP address in the virtual subnet, and the virtual subnet site where the PE-2 is located includes at least 1 Other PE devices. It is found that the ARP packet whose source MAC address is the virtual MAC address is usually sent by the other PE device in the virtual subnet site where the first PE is located as the ARP proxy.
  • the PE-2 carries the received ARP packet. Whether the source MAC address is identified and confirmed by the virtual MAC address, and the identification of the case where the ARP packet is sent by the other PE device in the virtual subnet site where the PE-2 is located is used as the ARP proxy, and the corresponding The situation is that the PE-2 determines that the source MAC address is a virtual MAC address.
  • the PE-2 does not store the local CE host routing entry corresponding to the source IP address carried in the ARP packet, and/or the route that is not based on the Layer 3 VPN.
  • the protocol distributes the local CE host route corresponding to the source IP address in the virtual subnet, so that the PE device can save (use) and/or distribute the wrong CE host route at the root source, thereby facilitating the virtual
  • the CE host routing loop is avoided as much as possible. This improves the efficiency of transmitting data packets between CE hosts and reduces the waste of network resources.
  • FIG. 3 to FIG. 8 are mainly described for the ARP scenario, and the scenario for the ND protocol is similar.
  • the NS packet is similar to the ARP request packet, and the NA packet is similar to the ARP response packet.
  • the PE-2 in the embodiment corresponding to FIG. 3 to FIG. 8 is similar to the first PE device in the embodiment corresponding to FIG. 2 .
  • Embodiments of the present invention also provide related apparatus for implementing the above solution.
  • an embodiment of the present invention provides that an operator border device 900 can include: a receiving unit 910 and a processing unit 920.
  • the receiving unit 910 is configured to receive a packet for address resolution, where the virtual subnet site where the carrier border device is located further includes at least one second carrier border device.
  • the packet used for the address resolution received by the receiving unit 910 may be from a certain second PE device, or may be from a virtual location where the carrier border device 900 is located.
  • the packet used for address resolution may be an ARP packet or an ND protocol packet or other packet used for address resolution.
  • the ARP packet may be an ARP request packet or an ARP response packet.
  • the ND protocol packet can be an NS packet or an NA packet.
  • the processing unit 920 is configured to determine whether the source MAC address carried in the packet is a virtual MAC address, and if the source MAC address is determined to be a virtual MAC address, do not perform at least one of the following operations: saving the source carried by the packet.
  • the local client boundary CE host routing entry corresponding to the IP address and the routing protocol based on the Layer 3 VPN distribute the local CE host route corresponding to the IP address in the virtual subnet.
  • the processing unit 920 may not save the ARP entry or the ND protocol entry, where the ARP entry records the mapping relationship between the source IP address and the source MAC address carried in the ARP packet. .
  • the mapping relationship between the source IP address and the source MAC address carried in the ND protocol packet is recorded in the ND protocol entry.
  • the processing unit 920 is further configured to: if it is determined that the source MAC address is not a virtual MAC address, perform at least one of the following operations: save the local CE host routing entry corresponding to the source IP address And distributing, according to the foregoing routing protocol, the local CE host route corresponding to the foregoing IP address in the virtual subnet.
  • the processing unit 920 is further configured to:
  • At least one of the following operations is not performed: saving the local CE host route corresponding to the source IP address. An entry, the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet according to the foregoing routing protocol;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the whitelist, perform at least one of the following operations: save the local CE host route corresponding to the source IP address.
  • the entry, based on the above routing protocol, is in the above virtual
  • the local CE host route corresponding to the above IP address is distributed in the subnet.
  • the processing unit 920 is further configured to:
  • the source MAC address is not a virtual MAC address, and the source MAC address is different from any one of the MAC addresses recorded in the blacklist, perform at least one of the following operations: save the local CE host route corresponding to the source IP address. An entry, the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet according to the foregoing routing protocol;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the blacklist, at least one of the following operations is not performed: saving the local CE host corresponding to the source IP address.
  • the routing entry, and the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet based on the foregoing routing protocol.
  • the processing unit 920 is specifically configured to: if the source MAC address carried in the packet is equal to the foregoing, in the aspect of determining whether the source medium access control MAC address carried in the packet is a virtual MAC address, And determining, by the virtual MAC address, the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the carrier border device, determining that the source MAC address is not a virtual MAC address.
  • the processing unit 920 is specifically configured to: query the corresponding at least one second carrier border device, in the aspect of determining whether the source medium access control MAC address carried in the packet is a virtual MAC address. Determining the source MAC address, if the source MAC address carried in the packet is equal to the virtual MAC address corresponding to one of the at least one second carrier border device of the at least one second carrier border device. The virtual MAC address is determined; if the source MAC address carried in the packet is different from the virtual MAC address corresponding to any one of the at least one second carrier border device that is queried, the source MAC address is determined. The address is not a virtual MAC address.
  • the virtual MAC address corresponding to the PE device may be specifically corresponding to the virtual router associated with the PE device.
  • Virtual MAC address may be specifically corresponding to the virtual router associated with the PE device.
  • the local CE host routing entry saved by the PE device points to the CE host within the site where the PE device is located.
  • the local CE host route distributed by the PE device points to the CE host within the site where the PE device is located.
  • the local CE host routing entry saved by the PE device may include an IP address and a next hop address of the CE host.
  • the local CE host route distributed by the PE device may include an IP address and a next hop address of the CE host.
  • the PE device 900 determines whether the source MAC address carried in the packet for address resolution is a virtual MAC address. If the source MAC address is a virtual MAC address, the local CE host routing entry corresponding to the source IP address carried in the ARP packet is not saved, and/or the routing protocol not based on the Layer 3 VPN is in the virtual subnet. And distributing the local CE host route corresponding to the foregoing IP address, where the virtual subnet site where the PE device 900 is located further includes at least one second PE device.
  • the PE device 900 receives the packet. Whether the source MAC address of the packet used for address resolution is a virtual MAC address for identification and confirmation, and whether the packet used for address resolution is another PE device in the virtual subnet site where the first PE is located.
  • the identification of the case sent by the address resolution agent, and corresponding to the case ie, if the source MAC address is determined to be a virtual MAC address
  • the PE device 900 does not store the source IP address corresponding to the packet used for address resolution.
  • the local CE host routing entry, and/or the routing protocol not based on the Layer 3 VPN distributes the local CE host route corresponding to the IP address in the virtual subnet, which is beneficial to eliminate the PE device from the wrong CE host at the root source.
  • the storage and/or distribution of routes is beneficial to the existence of multiple PE devices in some sites of the virtual subnet.
  • the quantity avoids the formation of a CE host routing loop, which improves the efficiency of transmitting data packets between CE hosts and reduces the waste of network resources.
  • FIG. 10 is a schematic diagram of a PE device 1000 according to an embodiment of the present invention.
  • the PE device 1000 may include at least one bus 1001, at least one processor 1002 connected to the bus 1001, and at least one memory 1003 connected to the bus 1001.
  • the processor 1002 calls, by using the bus 1001, the code stored in the memory 1003 to receive a message for address resolution, and determines whether the source medium access control MAC address carried in the message is a virtual MAC address; if the source is determined If the MAC address is a virtual MAC address, the device does not perform at least one of the following operations: storing the local client boundary CE host routing entry corresponding to the source Internet Protocol IP address carried in the packet, and routing based on the Layer 3 virtual private network VPN.
  • the protocol distributes the local CE host route corresponding to the foregoing IP address in the virtual subnet.
  • the virtual subnet site where the PE device 1000 is located further includes at least one second carrier border device.
  • the packet used for address resolution may be an ARP packet or an ND protocol packet or other packet used for address resolution.
  • the processor 1002 may not save the ARP entry or the ND protocol entry, where the mapping between the source IP address and the source MAC address carried in the ARP packet is recorded in the ARP entry. .
  • the mapping relationship between the source IP address and the source MAC address carried in the ND protocol packet is recorded in the ND protocol entry.
  • the processor 1002 is further configured to: if it is determined that the source MAC address is not a virtual MAC address, perform at least one of the following operations: save the local CE host routing entry corresponding to the source IP address And distributing, according to the foregoing routing protocol, the local CE host route corresponding to the foregoing IP address in the virtual subnet.
  • the processor 1002 is further configured to:
  • At least one of the following operations is not performed: saving the local CE host route corresponding to the source IP address.
  • the entry, based on the above routing protocol, is in the above virtual Distributing the local CE host route corresponding to the above IP address in the subnet;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the whitelist, perform at least one of the following operations: save the local CE host route corresponding to the source IP address.
  • the entry, the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet based on the foregoing routing protocol.
  • the processor 1002 is further configured to:
  • the source MAC address is not a virtual MAC address, and the source MAC address is different from any one of the MAC addresses recorded in the blacklist, perform at least one of the following operations: save the local CE host route corresponding to the source IP address. An entry, the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet according to the foregoing routing protocol;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the blacklist, at least one of the following operations is not performed: saving the local CE host corresponding to the source IP address.
  • the routing entry, and the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet based on the foregoing routing protocol.
  • the processor 1002 is specifically configured to: if the source MAC address carried in the packet is equal to the foregoing, in the foregoing, determining whether the source medium access control MAC address carried in the packet is a virtual MAC address. And determining, by the virtual MAC address, the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the carrier border device, determining that the source MAC address is not a virtual MAC address.
  • the processor 1002 is specifically configured to: query the corresponding at least one second carrier boundary device, in the aspect of determining whether the source medium access control MAC address carried in the packet is a virtual MAC address. Determining the source MAC address, if the source MAC address carried in the packet is equal to the virtual MAC address corresponding to one of the at least one second carrier border device of the at least one second carrier border device. The virtual MAC address is determined; if the source MAC address carried in the packet is different from the virtual MAC address corresponding to any one of the at least one second carrier border device that is queried, the source MAC address is determined. The address is not a virtual MAC address.
  • the virtual MAC address corresponding to the PE device may be a virtual MAC address corresponding to the virtual router associated with the PE device.
  • the local CE host routing entry saved by the PE device points to the CE host within the site where the PE device is located.
  • the local CE host route distributed by the PE device points to the CE host within the site where the PE device is located.
  • the local CE host routing entry saved by the PE device may include an IP address and a next hop address of the CE host.
  • the local CE host route distributed by the PE device may include an IP address and a next hop address of the CE host.
  • the PE device 1000 after the PE device 1000 receives the packet for address resolution, the PE device 1000 first determines whether the source MAC address carried in the packet used for address resolution is a virtual MAC address. If the source MAC address is a virtual MAC address, the local CE host routing entry corresponding to the source IP address carried in the ARP packet is not saved, and/or the routing protocol not based on the Layer 3 VPN is in the virtual subnet. And distributing the local CE host route corresponding to the foregoing IP address, where the virtual subnet site where the PE device 1000 is located further includes at least one second PE device.
  • the packet used for address resolution with the source MAC address being the virtual MAC address is usually sent by the other PE device in the virtual subnet site where the first PE is located as the address resolution proxy. Therefore, the PE device 1000 receives the packet. Whether the source MAC address of the packet used for address resolution is a virtual MAC address for identification and confirmation, and whether the packet used for address resolution is another PE device in the virtual subnet site where the first PE is located.
  • the PE device 1000 does not store the local CE host routing entry corresponding to the source IP address carried in the packet for the address resolution, and/or the PE device 1000 is not based on the Layer 3
  • the routing protocol of the VPN distributes the local CE host route corresponding to the IP address in the virtual subnet, so that the storage and/or distribution of the wrong CE host route by the PE device is eliminated at the root source, thereby facilitating the virtual sub-network.
  • Some sites in the network have multiple PE devices in the scenario. Try to avoid forming a CE host routing loop, which improves the efficiency of transmitting data packets between CE hosts and reduces network resource waste.
  • FIG. 11 is a structural block diagram of a PE device 1100 according to another embodiment of the present invention.
  • the PE device 1100 may include: at least one processor 1101, at least one network interface 1104 or other user interface 1103, a memory 1105, and at least one communication bus 1102. Communication bus 1102 is used to implement connection communication between these components.
  • the PE device 1100 optionally includes a user interface 1103, including a display (eg, a touch screen, LCD, CRT, Holographic or Projector, etc.), a pointing device (eg, a mouse, a trackball touch) Board or touch screen, etc.), camera and/or pickup device, etc.
  • a display eg, a touch screen, LCD, CRT, Holographic or Projector, etc.
  • a pointing device eg, a mouse, a trackball touch
  • Camera and/or pickup device etc.
  • the memory 1102 can include a read only memory and a random access memory and provides instructions and data to the processor 1101. A portion of the memory 1102 can also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1105 stores elements, executable modules or data structures, or a subset thereof, or their extended set:
  • the operating system 11051 includes various system programs for implementing various basic services and processing hardware-based tasks.
  • the application module 11052 includes various applications for implementing various application services.
  • the application module 11052 includes, but is not limited to, a collection confirmation receiving unit 910, a processing unit 920, and the like.
  • the processor 1101 is configured to receive a message for address resolution by using a program or an instruction stored in the memory 1105, and determine whether the source medium access control MAC address carried in the packet is a virtual MAC address; Determining that the source MAC address is a virtual MAC address, The at least one of the following operations is not performed: the local client boundary CE host routing entry corresponding to the source Internet Protocol IP address carried in the foregoing packet is saved, and the routing protocol based on the Layer 3 virtual private network VPN is distributed in the virtual subnet. Local CE host route corresponding to the above IP address.
  • the virtual subnet site where the PE device 1100 is located further includes at least one second carrier border device.
  • the packet used for address resolution may be an ARP packet or an ND protocol packet or other packet used for address resolution.
  • the processor 1101 may not save the ARP entry or the ND protocol entry, where the ARP entry records the mapping relationship between the source IP address and the source MAC address carried in the ARP packet. .
  • the mapping relationship between the source IP address and the source MAC address carried in the ND protocol packet is recorded in the ND protocol entry.
  • the processor 1101 is further configured to: if it is determined that the source MAC address is not a virtual MAC address, perform at least one of the following operations: save the local CE host routing entry corresponding to the source IP address And distributing, according to the foregoing routing protocol, the local CE host route corresponding to the foregoing IP address in the virtual subnet.
  • the processor 1101 is further configured to:
  • At least one of the following operations is not performed: saving the local CE host route corresponding to the source IP address. An entry, the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet according to the foregoing routing protocol;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the whitelist, perform at least one of the following operations: save the local CE host route corresponding to the source IP address.
  • the entry, the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet based on the foregoing routing protocol.
  • the processor 1101 is further configured to:
  • the source MAC address is not a virtual MAC address, and the source MAC address is different If any one of the MAC addresses is recorded in the blacklist, perform at least one of the following operations: save the local CE host routing entry corresponding to the source IP address, and distribute the IP address in the virtual subnet based on the routing protocol. Corresponding local CE host route;
  • the source MAC address is not a virtual MAC address, and the source MAC address is equal to one of the MAC addresses recorded in the blacklist, at least one of the following operations is not performed: saving the local CE host corresponding to the source IP address.
  • the routing entry, and the local CE host route corresponding to the foregoing IP address is distributed in the virtual subnet based on the foregoing routing protocol.
  • the processor 1101 is specifically configured to: if the source MAC address carried in the packet is equal to the foregoing, in the foregoing, determining whether the source media access control MAC address carried in the packet is a virtual MAC address. And determining, by the virtual MAC address, the source MAC address is a virtual MAC address; if the source MAC address is different from the virtual MAC address corresponding to the carrier border device, determining that the source MAC address is not a virtual MAC address.
  • the processor 1101 is specifically configured to: query the corresponding at least one second carrier border device, in the aspect of determining whether the source medium access control MAC address carried by the packet is a virtual MAC address. Determining the source MAC address, if the source MAC address carried in the packet is equal to the virtual MAC address corresponding to one of the at least one second carrier border device of the at least one second carrier border device. The virtual MAC address is determined; if the source MAC address carried in the packet is different from the virtual MAC address corresponding to any one of the at least one second carrier border device that is queried, the source MAC address is determined. The address is not a virtual MAC address.
  • the virtual MAC address corresponding to the PE device may be a virtual MAC address corresponding to the virtual router associated with the PE device.
  • the local CE host routing entry saved by the PE device points to the CE host within the site where the PE device is located.
  • the local CE host route distributed by the PE device points to the PE device.
  • the local CE host routing entry saved by the PE device may include an IP address and a next hop address of the CE host.
  • the local CE host route distributed by the PE device may include an IP address and a next hop address of the CE host.
  • the PE device 1100 determines whether the source MAC address carried in the packet for address resolution is a virtual MAC address. If the source MAC address is a virtual MAC address, the local CE host routing entry corresponding to the source IP address carried in the ARP packet is not saved, and/or the routing protocol not based on the Layer 3 VPN is in the virtual subnet. And distributing the local CE host route corresponding to the foregoing IP address, where the virtual subnet site where the PE device 1100 is located further includes at least one second PE device.
  • the PE device 1100 receives the packet. Whether the source MAC address of the packet used for address resolution is a virtual MAC address for identification and confirmation, and whether the packet used for address resolution is another PE device in the virtual subnet site where the first PE is located.
  • the identification of the case sent by the address resolution agent, and corresponding to the case ie, if the source MAC address is determined to be a virtual MAC address
  • the PE device 1100 does not store the source IP address corresponding to the packet carried in the address resolution.
  • the local CE host routing entry, and/or the PE device 1100 does not distribute the local CE host route corresponding to the IP address in the virtual subnet based on the routing protocol of the Layer 3 VPN, so that the PE device is eliminated at the root source.
  • the storage and/or distribution of the erroneous CE host routes is beneficial to avoid the formation of CE host routing loops in the scenario where multiple PE devices exist in some sites of the virtual subnet.
  • the road improves the efficiency of transmitting data packets between CE hosts and reduces the waste of network resources.
  • an embodiment of the present invention further provides a communication system, which may include:
  • a plurality of carrier border devices 1210 wherein at least one of the plurality of carrier border devices 1210 may be, for example, an operator border device 900 or an operator border device 1100 or an operator boundary device 1100.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium can store a program, and the program includes some or all of the steps of the host route processing method in the virtual subnet described in the foregoing method embodiment.
  • the disclosed apparatus may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or a software function list. The realization of the form of the yuan.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the instructions include a plurality of instructions for causing a computer device (which may be a personal computer, server or network device, etc., and in particular a processor in a computer device) to perform all or part of the steps of the methods of the various embodiments of the present invention.
  • the foregoing storage medium may include: a U disk, a magnetic disk, a random access memory (RAM), a read-only memory (ROM), or a mobile hard disk or an optical disk, and the like, which can store program codes. medium.

Abstract

本发明实施例公开了虚拟子网中的主机路由处理方法及相关设备和通信系统。其中，一种虚拟子网中的主机路由处理方法，包括：第一运营商边界设备接收用于地址解析的报文，第一运营商边界设备所位于的虚拟子网站点内还包括至少一个第二运营商边界设备；第一运营商边界设备确定报文携带的源MAC地址是否为虚拟MAC地址；若确定源MAC地址为虚拟MAC地址，则不执行如下操作中的至少一种：保存报文携带的源IP地址对应的本地客户边界CE主机路由表项、基于三层VPN的路由协议在虚拟子网中分发IP地址对应的本地CE主机路由。本发明实施例的方案有利于尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率。

Description

虚拟子网中的主机路由处理方法及相关设备和通信系统
本申请要求于2014年2月21日提交中国专利局、申请号为CN201410060262.7、发明名称为“虚拟子网中的主机路由处理方法及相关设备和通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，具体涉及虚拟子网中本地主机路由处理方法及相关设备和通信系统。
背景技术
虚拟子网(VS，Virtual Subnet)中的运营商边界(PE，Provider Edge)设备之间通常是利用三层虚拟私有网络(L3VPN，Layer3 Virtual Private Network)的路由协议来交换本地客户边界(CE，Customer Edge)主机路由，进而实现子网扩展(subnet extension)。
PE设备可根据地址解析协议(ARP，Address Resolution Protocol)或邻居发现(ND，Neighbor Discovery)协议缓存表中记录本地CE主机信息，生成本地CE主机的网际互联协议(IP，Internet Protocol)地址所对应的本地CE主机路由，并基于L3VPN的路由协议向虚拟子网中分发本地CE主机路由，虚拟子网中的其它PE设备可据此学习到该本地CE主机路由。此外，PE设备可具备ARP或ND协议代理(Proxy)功能。其中，以ARP的应用场景为例来说，当虚拟子网中的PE设备从本地CE主机接收到用于询问某个远端CE主机的MAC地址的ARP请求报文时，若该PE设备当前已学习到该远端CE主机的IP地址对应的CE主机路由，则该PE设备可作为Proxy通过ARP响应报文把该PE设备对应的虚拟媒介访问地址(VMAC，Virtual Media Access Address)返回给请求的本地CE主机。
虚拟子网中存在多个站点。实践发现，当虚拟子网的一些站点内存在多个PE设备实现站点多归属的情况下，经常容易形成CE主机路由环路，而形成CE主机路由环路之后通常会较大的增加数据包的转发路径长度，进而可能较大影响CE主机之间传输数据包的效率。
发明内容
本发明实施例提供一种虚拟子网中的主机路由处理方法及相关设备和通信系统，以在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率。
为解决上述技术问题，本发明实施例提供以下技术方案：
本发明实施例第一方面提供一种虚拟子网中的主机路由处理方法，包括：
第一运营商边界设备接收用于地址解析的报文，所述第一运营商边界设备所位于的虚拟子网站点内还包括至少一个第二运营商边界设备；
所述第一运营商边界设备确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址；
若确定所述源MAC地址为虚拟MAC地址，则不执行如下操作中的至少一种：保存所述报文携带的源网际互联协议IP地址对应的本地客户边界CE主机路由表项、基于三层虚拟私有网络VPN的路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
结合第一方面，在第一方面的第一种可能的实施方式中，
所述方法还包括：
若确定所述源MAC地址不是虚拟MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
结合第一方面，在第一方面的第二种可能的实施方式中，
所述方法还包括：
若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址不同于白名单中记录的任意1个MAC地址，则不执行如下操作的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由；
和/或，
若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址等同于白名单中记录的其中1个MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
结合第一方面，在第一方面的第三种可能的实施方式中，
所述方法还包括：
若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址不同于黑名单中记录的任意1个MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由；
和/或，
若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址等同于黑名单中记录的其中1个MAC地址，则不执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
结合第一方面或第一方面的第一种可能的实施方式或第一方面的第二种可能的实施方式或第一方面的第三种可能的实施方式，在第一方面的第四种可能的实施方式中，
所述确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址包括：若所述报文携带的源MAC地址等同于所述第一运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址为虚拟MAC地址；若所述源MAC地址不同于所述第一运营商边界设备对应的虚拟MAC地址，则确 定所述源MAC地址不是虚拟MAC地址。
结合第一方面的第四种可能的实施方式，在第一方面的第五种可能的实施方式中，所述第一运营商边界设备对应的虚拟MAC地址具体为所述第一运营商边界设备关联的虚拟路由器对应的虚拟MAC地址。
结合第一方面或第一方面的第一种可能的实施方式或第一方面的第二种可能的实施方式或第一方面的第三种可能的实施方式，在第一方面的第六种可能的实施方式中，
所述确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址包括：
查询所述至少一个第二运营商边界设备对应的虚拟MAC地址，若所述报文携带的源MAC地址等同于查询到的所述至少一个第二运营商边界设备之中的其中一个第二运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址为虚拟MAC地址；若所述报文携带的源MAC地址不同于查询到的所述至少一个第二运营商边界设备之中的任意一个第二运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址不是虚拟MAC地址。
结合第一方面的第六种可能的实施方式，在第一方面的第七种可能的实施方式中，所述第二运营商边界设备对应的虚拟MAC地址具体为所述第二运营商边界设备关联的虚拟路由器对应的虚拟MAC地址。
结合第一方面或第一方面的第一种可能的实施方式或第一方面的第二种可能的实施方式或第一方面的第三种可能的实施方式或第一方面的第四种可能的实施方式或第一方面的第五种可能的实施方式或第一方面的第六种可能的实施方式或第一方面的第七种可能的实施方式，在第一方面的第八种可能的实施方式中，所述报文为地址解析协议ARP报文或邻居发现ND协议报文。
本发明实施例第二方面提供一种运营商边界设备，可包括：
接收单元，用于接收用于地址解析的报文，所述运营商边界设备所位于的虚拟子网站点内还包括至少一个第二运营商边界设备；
处理单元，用于确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址；若确定所述源MAC地址为虚拟MAC地址，则不执行如下操作中的至少一种：保存所述报文携带的源网际互联协议IP地址对应的本地客户边界CE主机路由表项、基于三层虚拟私有网络VPN的路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
结合第二方面，在第二方面的第一种可能的实施方式中，所述处理单元还用于，若确定所述源MAC地址不是虚拟MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
结合第二方面，在第二方面的第二种可能的实施方式中，
所述处理单元还用于，
若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址不同于白名单中记录的任意1个MAC地址，则不执行如下操作的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由；
和/或，
若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址等同于白名单中记录的其中1个MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
结合第二方面，在第二方面的第三种可能的实施方式中，
所述处理单元还用于，
若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址不同于黑名单中记录的任意1个MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由；
和/或，
若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址等同于黑名单中记录的其中1个MAC地址，则不执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
结合第二方面或第二方面的第一种可能的实施方式或第二方面的第二种可能的实施方式或第二方面的第三种可能的实施方式，在第二方面的第四种可能的实施方式中，
在所述确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，所述处理单元具体用于：若所述报文携带的源MAC地址等同于所述运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址为虚拟MAC地址；若所述源MAC地址不同于所述运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址不是虚拟MAC地址。
结合第二方面的第四种可能的实施方式，在第二方面的第五种可能的实施方式中，所述运营商边界设备对应的虚拟MAC地址具体为所述运营商边界设备关联的虚拟路由器对应的虚拟MAC地址。
结合第二方面或第二方面的第一种可能的实施方式或第二方面的第二种可能的实施方式或第二方面的第三种可能的实施方式，在第二方面的第六种可能的实施方式中，
在所述确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，所述处理单元具体用于：查询所述至少一个第二运营商边界设备对应的虚拟MAC地址，若所述报文携带的源MAC地址等同于查询到的所述至少一个第二运营商边界设备之中的其中一个第二运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址为虚拟MAC地址；若所述报文携带的源MAC地址不同于查询到的所述至少一个第二运营商边界设备之中的任意一个第二运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址不是虚拟MAC地址。
结合第二方面的第六种可能的实施方式，在第二方面的第七种可能的 实施方式中，所述第二运营商边界设备对应的虚拟MAC地址具体为所述第二运营商边界设备关联的虚拟路由器对应的虚拟MAC地址。
结合第二方面或第二方面的第一种可能的实施方式或第二方面的第二种可能的实施方式或第二方面的第三种可能的实施方式或第二方面的第四种可能的实施方式或第二方面的第五种可能的实施方式或第二方面的第六种可能的实施方式或第二方面的第七种可能的实施方式，在第二方面的第八种可能的实施方式中，所述报文为地址解析协议ARP报文或邻居发现ND协议报文。
本发明实施例第三方面提供一种通信系统，可包括：
多个运营商边界设备，其中，所述多个运营商边界设备中的至少一个为如本发明实施例提供的任意一种运营商边界设备。
由上可见，本发明实施例的技术方案中，当第一PE设备接收到用于地址解析的报文之后，第一PE设备先确定该用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址；若确定源MAC地址为虚拟MAC地址，则不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由，其中，第一PE设备所位于的虚拟子网站点内还包括至少一个第二PE设备。研究发现，源MAC地址为虚拟MAC地址的用于地址解析的报文通常是第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的，因此，第一PE设备对接收到的用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对用于地址解析的报文是否为第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的情况的识别，而对应这种情况(即若确定上述源MAC地址为虚拟MAC地址)，第一PE设备不保存上述用于地址解析的报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网之中分发上述IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的存储和/或分发， 进而有利于在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，进而减少网络资源的浪费。
附图说明
为了更清楚地说明本发明的技术方案，下面将对实施方式中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施方式，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以如这些附图获得其他的附图。
图1是本发明实施例提供的一种网络架构的示意图；
图2是本发明实施例提供的一种虚拟子网中的主机路由处理方法的流程示意图；
图3是本发明实施例提供的另一种虚拟子网中的主机路由处理方法的流程示意图；
图4是本发明实施例提供的另一种虚拟子网中的主机路由处理方法的流程示意图；
图5是本发明实施例提供的另一种虚拟子网中的主机路由处理方法的流程示意图；
图6是本发明实施例提供的另一种虚拟子网中的主机路由处理方法的流程示意图；
图7是本发明实施例提供的另一种虚拟子网中的主机路由处理方法的流程示意图；
图8是本发明实施例提供的另一种虚拟子网中的主机路由处理方法的流程示意图；
图9是本发明实施例提供的一种PE设备的结构示意图；
图10是本发明实施例提供的另一种PE设备的结构示意图；
图11是本发明实施例提供的另一种PE设备的结构示意图；
图12是本发明实施例提供的一种通信系统的示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例提供一种虚拟子网中的主机路由处理方法及相关设备和通信系统，以在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率。
为使得本发明的发明目的、特征、优点能够更加的明显和易懂，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，下面所描述的实施例仅仅是本发明一部分实施例，而非全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”“第四”等是用于区别不同的对象，而不是用于描述特定的顺序。此外术语“包括”和“具有”以及他们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可包括没有列出的步骤或单元。
以下分别进行详细说明。
下面首先结合图1对本发明实施例的技术方案涉及的一些可能的应用场景进行举例介绍。图1为本发明实施例提供的一种网络架构示意图。
如图1举例所示，虚拟子网站点A中包括PE设备PE-1、PE设备PE-2、交换设备T1、CE主机#001和CE主机#002，其中，CE主机#001和CE主机#002通过交换设备T1与PE设备PE-1和PE设备PE-2互联。虚拟子网站点B包括PE设备 PE-4、交换设备T2、CE主机#004，其中，CE主机#004通过交换设备T2与PE设备PE-4互联。其中，虚拟子网站点C包括PE设备PE-3、交换设备T3、CE主机#003，CE主机#003通过交换设备T3和PE设备PE-3互联。
其中，PE设备PE-1、PE设备PE-2、PE设备PE-3和PE设备PE-4通过互联网络互联。
其中，交换设备可以是交换机或集线器等。
下面基于图1所示架构，介绍本发明发明人分析研究出的一种可形成主机路由环路的场景。下面主要以ARP场景为例进行描述，ND协议场景可以以此类推。
假设PE-1具备ARP Proxy功能。PE-1已经学习到了(例如从PE-4)CE主机#004的IP地址对应的CE主机路由。当PE-1接收到来自本地CE主机#001的用于询问远端CE主机#004的MAC地址的ARP请求报文时，由于PE-1已经学习到了CE主机#004的IP地址对应的CE主机路由，因此，该PE设备可作为ARP Proxy来发送用于响应上述ARP请求报文的ARP响应报文，以通过ARP响应报文把PE-1关联的虚拟路由器对应的VMAC地址返回给CE主机#001(其中，PE-1对应的VMAC被作为上述ARP响应报文的源MAC地址)。交换设备T1如果洪泛其接收到的上述ARP响应报文，PE-2将可接收到上述ARP响应报文，现有技术中PE-2直接在CE主机路由表项中保存与上述ARP响应报文携带的源IP地址(此处该源IP地址为CE主机#004的IP地址)对应的本地CE主机路由表项(即PE-2错误的将CE主机#004默认为是处于虚拟子网站点A之内的本地CE主机)。PE-2还可以进一步基于三层VPN的路由协议在虚拟子网中分发上述源IP地址对应的本地CE主机路由，其中，PE-2在虚拟子网中分发上述本地CE主机路由的行为将可能使得其它的PE设备(例如PE-3、PE-5等等)学习到错误的CE主机路由。
PE-2的上述一系列错误行为使得CE主机路由环路形成，例如PE-3(假设PE-3学习到了上述错误的CE主机路由)可能将CE主机#003发给CE主机#004的数据包转发到PE-2，而PE-2又将该数据包转发到交换设备T1(由于PE-2保 存了错误的本地CE主机路由表项)，交换设备T1将该数据包转发到PE-1，PE-1再将该数据包转发到PE-4，PE-4最终将数据包转发给CE主机#004，该数据包几经辗转才达到CE主机#004。而该数据包的最佳路径一般是通过PE-3直接路由到PE-4(无需经PE-1和PE-2)，进而快速到达CE主机#004。可见，形成CE主机路由环路之后会较大的增加数据包的路由路径长度，进而可能较大影响CE主机之间传输数据包的效率。
本发明实施例的技术方案重点探究在虚拟子网的一些站点内存在多个PE设备场景下，如何尽量避免形成CE主机路由环路，缩短CE主机之间传输数据包的转发路径长度，进而提升CE主机之间传输数据包的效率。
本发明虚拟子网中的主机路由处理方法的一个实施例，虚拟子网中的主机路由处理方法可以包括：第一PE设备接收用于地址解析的报文，上述第一PE设备所位于的虚拟子网站点内还包括至少一个第二PE设备；上述第一PE设备确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则上述第一PE设备不执行如下操作中的至少一种：保存上述报文携带的源网际互联协议IP地址对应的本地CE主机路由表项、基于三层虚拟私有网络VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
参见图2，图2是本发明的一个实施例提供的一种虚拟子网中的主机路由处理方法的流程示意图。本发明的一个实施例提供的一种虚拟子网中的主机路由处理方法可包括以下内容：
201、第一PE设备接收用于地址解析的报文，其中，上述第一PE设备所位于的虚拟子网站点内还包括至少一个第二PE设备。
其中，可以理解的是，第一PE设备接收到的用于地址解析的报文可能来自某个第二PE设备，也可能来自上述第一PE设备所位于的虚拟子网站点内的某个CE设备。
其中，上述用于地址解析的报文可为ARP报文或ND协议报文或其它用于地址解析的报文。
202、上述第一PE设备确定上述报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则不执行如下操作中的至少一种：保存上述报文携带的源网际互联协议IP地址对应的本地客户边界CE主机路由表项、基于三层虚拟私有网络VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，上述ARP报文可为ARP请求报文或ARP响应报文。上述ND协议报文可为邻居请求(NS，Neighbor Solicitation)报文或邻居通告(NA，Neighbor Advertisement)报文。
此外，若确定上述源MAC地址为虚拟MAC地址，第一PE设备也可不保存ARP条目或ND协议条目，其中，ARP条目中记录上述ARP报文携带的源IP地址和源MAC地址之间的映射关系。ND协议条目中记录上述ND协议报文携带的源IP地址和源MAC地址之间的映射关系。
由上可见，本发明实施例的技术方案中，当第一PE设备接收到用于地址解析的报文之后，第一PE设备先确定该用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址；若确定源MAC地址为虚拟MAC地址，则不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由，其中，第一PE设备所位于的虚拟子网站点内还包括至少一个第二PE设备。研究发现，源MAC地址为虚拟MAC地址的用于地址解析的报文通常是第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的，因此，第一PE设备对接收到的用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对用于地址解析的报文是否为第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的情况的识别，而对应这种情况(即若确定上述源MAC地址为虚拟MAC地址)，第一PE设备不保存上述用于地址解析的报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网之中分发上述IP地址对应的本地CE主机路由， 这样就有利于在根源上消除PE设备对错误CE主机路由的存储和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，进而减少网络资源的浪费。
在本发明一些实施例中，PE设备(如第一PE设备或第二PE设备)对应的虚拟MAC地址具体可以是，PE设备关联的虚拟路由器对应的虚拟MAC地址。
可以理解的是，PE设备保存的本地CE主机路由表项指向PE设备所处站点之内的CE主机。PE设备分发的本地CE主机路由指向该PE设备所处站点之内的CE主机。其中，在本发明实施例中，PE设备保存的本地CE主机路由表项可包含CE主机的IP地址和下一跳地址。其中，在本发明实施例中，PE设备分发的本地CE主机路由可包含CE主机的IP地址和下一跳地址。
在本发明的一些实施例中，上述虚拟子网中的主机路由处理方法还可以包括：若确定上述源MAC地址不是虚拟MAC地址，则上述第一PE设备可执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的另一些实施例中，上述虚拟子网中的主机路由处理方法还可以包括：若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址不同于白名单中记录的任意1个MAC地址，则上述第一PE设备可不执行如下操作的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。和/或若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址等同于白名单中记录的其中1个MAC地址，则上述第一PE设备可执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP 地址对应的本地CE主机路由。
可以理解的是，由于进一步引入白名单控制机制，有利于更加灵活的实现路由分发控制。进一步的，上述第一PE设备还可根据指令对上述白名单进行更新。
在本发明的又一些实施例中，上述虚拟子网中的主机路由处理方法还可以包括：若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址不同于黑名单中记录的任意1个MAC地址，则上述第一PE设备可执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。和/或若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址等同于黑名单中记录的其中1个MAC地址，则上述第一PE设备可不执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
可以理解的是，由于进一步引入黑名单控制机制，有利于更加灵活的实现路由分发控制。进一步的，上述第一PE设备还可根据指令对上述黑名单进行更新。
在本发明的一些实施例中，上述确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可以包括：若上述报文携带的源MAC地址等同于上述第一PE设备对应的虚拟MAC地址，则可确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述第一PE设备对应的虚拟MAC地址，则可确定上述源MAC地址不是虚拟MAC地址。其中，这种举例场景中主要是假设同一虚拟子网站点内的各PE设备对应相同虚拟MAC地址(即同一虚拟子网站点内的各PE设备关联相同虚拟路由器)为例进行说明的。
在本发明的另一些实施例中，上述确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可包括：上述第一PE设备查询上述至 少一个第二PE设备对应的虚拟MAC地址，若上述报文携带的源MAC地址等同于查询到的上述至少一个第二PE设备之中的其中一个第二PE设备对应的虚拟MAC地址，则可确定上述源MAC地址为虚拟MAC地址；若上述报文携带的源MAC地址不同于查询到的上述至少一个第二PE设备之中的任意一个第二PE设备对应的虚拟MAC地址，则确定上述源MAC地址不是虚拟MAC地址。
可以理解，上述第一PE设备也可能通过其它的方式来确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址。
为便于更好的理解和实施本发明实施例的上述方案，下面通过举例一些具体的应用场景进行说明。其中，下面以在图1所示网络架构中实施图3～图8所对应方法为例进行描述。
参见图3，图3是本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法的流程示意图。如图3所示，本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法可包括以下内容：
301、CE主机#001发送用于请求获得CE主机#004的MAC地址的ARP请求报文q11。其中，ARP请求报文q11携带CE主机#001的IP地址(即源IP地址)和MAC地址(即源MAC地址)，ARP请求报文q11还携带CE主机#004的IP地址等。
302、PE-1接收ARP请求报文q11。此处，假设PE-1当前已经通过PE-4学习到了CE主机#004对应的CE主机路由，因此PE-1可作为ARP代理，发送用于响应ARP请求报文q11的ARP响应报文q12。其中，ARP响应报文q12携带的源MAC地址为PE-1关联的虚拟路由器对应的虚拟MAC地址，ARP响应报文q12携带的源IP地址为CE主机#004的IP地址。
303、交换设备T1洪泛接收到的ARP响应报文q12。
PE-2和CE主机#001将可接收到上述ARP响应报文q12。
304、PE-2确定上述ARP响应报文q12携带的源MAC地址是否为虚拟MAC地址。
其中，若PE-2确定上述ARP响应报文q12携带的源MAC地址是虚拟MAC地址，PE-2不执行如下操作中的至少1种：保存上述ARP响应报文q12携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
其中，若PE-2确定上述ARP响应报文q12携带的源MAC地址不是虚拟MAC地址，则PE-2执行如下操作中的至少一种：保存上述ARP响应报文q12携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明一些实施例中，PE-2确定上述ARP响应报文q12携带的源MAC地址是否为虚拟MAC地址可包括：若上述ARP响应报文q12携带的源MAC地址等同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2可确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2确定上述源MAC地址不是虚拟MAC地址。这种场景下主要是假设同一虚拟子网站点内的各PE设备关联相同的虚拟路由器为例进行说明的。
在本发明另一些实施例中，PE-2确定上述ARP响应报文q12携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可包括：上述PE-2查询PE-1关联的虚拟路由器对应的虚拟MAC地址，若上述ARP响应报文q12携带的源MAC地址等同于查询到的上述PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP响应报文q12携带的源MAC地址为虚拟MAC地址；若上述ARP响应报文q12携带的源MAC地址不同于查询到的PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP响应报文q12携带的源MAC地址不是虚拟MAC地址。
可以理解，上述PE-2也可能通过其它的方式来确定上述ARP响应报文q12携带的源媒介访问控制MAC地址是否为虚拟MAC地址。
由上可见，本实施例的技术方案中，PE-2接收到ARP响应报文之后，PE-2先确定该ARP报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源 MAC地址为虚拟MAC地址，则PE-2不保存上述ARP响应报文携带的源IP地址对应的本地CE主机路由表项，和/或PE-2不基于三层VPN的路由协议在上述虚拟子网中分发上述源IP地址对应的本地CE主机路由，其中，上述PE-2所位于的虚拟子网站点内还包括至少一个其它PE设备。研究发现，源MAC地址为虚拟MAC地址的ARP响应报文通常是PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的，因此，PE-2对接收到的ARP响应报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对ARP响应报文是否为PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的情况的识别，而对应这种情况(即若PE-2确定上述源MAC地址为虚拟MAC地址)，PE-2不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网之中分发上述源IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的保存(使用)和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，减少网络资源的浪费。
参见图4，图4是本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法的流程示意图。本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法可包括以下内容：
401、PE-1作为ARP Proxy，代理CE主机#004发送ARP请求报文q21。
其中，ARP请求报文q21的源IP地址为CE主机#004的IP地址。此处假设PE-1当前已经学习到了CE主机#004对应的CE主机路由，因此ARP请求报文q21携带的源MAC地址可为PE-1对应的虚拟MAC地址。
402、交换设备T1洪泛其接收到的ARP请求报文q21。
PE-2将可接收到上述ARP请求报文q21。
403、PE-2确定上述ARP请求报文q21携带的源MAC地址是否为虚拟MAC地址。
其中，若PE-2确定上述ARP请求报文q21携带的源MAC地址是虚拟MAC 地址，PE-2不执行如下操作中的至少1种：保存上述ARP请求报文q21携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
若PE-2确定上述ARP请求报文q21携带的源MAC地址不是虚拟MAC地址，则PE-2执行如下操作中的至少一种：保存上述ARP请求报文q21携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明一些实施例中，PE-2确定上述ARP请求报文q21携带的源MAC地址是否为虚拟MAC地址可包括：若上述ARP请求报文q21携带的源MAC地址等同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2可确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2确定上述源MAC地址不是虚拟MAC地址。这种场景下主要是假设同一虚拟子网站点内的各PE设备关联相同的虚拟路由器为例进行说明的。
在本发明另一些实施例中，PE-2确定上述ARP请求报文q21携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可包括：上述PE-2查询PE-1关联的虚拟路由器对应的虚拟MAC地址，若上述ARP请求报文q21携带的源MAC地址等同于查询到的上述PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q21携带的源MAC地址为虚拟MAC地址；若上述ARP请求报文q21携带的源MAC地址不同于查询到的PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q21携带的源MAC地址不是虚拟MAC地址。
可以理解，上述PE-2也可能通过其它的方式来确定上述ARP请求报文q21携带的源媒介访问控制MAC地址是否为虚拟MAC地址。
由上可见，本实施例的技术方案中，PE-2接收到ARP请求报文之后，PE-2先确定该ARP报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则PE-2不保存上述ARP请求报文携带的源IP地 址对应的本地CE主机路由表项，和/或PE-2不基于三层VPN的路由协议在上述虚拟子网中分发上述源IP地址对应的本地CE主机路由，其中，上述PE-2所位于的虚拟子网站点内还包括至少一个其它PE设备。研究发现，源MAC地址为虚拟MAC地址的ARP请求报文通常是PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的，因此，PE-2对接收到的ARP请求报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对ARP请求报文是否为PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的情况的识别，而对应这种情况(即若PE-2确定上述源MAC地址为虚拟MAC地址)，PE-2不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网之中分发上述源IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的保存(使用)和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，减少网络资源的浪费。
参见图5，图5是本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法的流程示意图。本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法可包括以下内容：
501、CE主机#002发送用于请求获得CE主机#004的MAC地址的ARP请求报文q31。其中，ARP请求报文q31携带CE主机#002的IP地址(即源IP地址)和MAC地址(即源MAC地址)，ARP请求报文q31还携带CE主机#004的IP地址等。
502、交换设备T1洪泛接收到的ARP请求报文q31。
PE-1和PE-2将可接收到上述ARP请求报文q31。
503、PE-2确定上述ARP请求报文q31携带的源MAC地址是否为虚拟MAC地址。
其中，若PE-2确定上述ARP请求报文q31携带的源MAC地址是虚拟MAC地址，PE-2不执行如下操作中的至少1种：保存上述ARP请求报文q31携带的 源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
若PE-2确定上述ARP请求报文q31携带的源MAC地址不是虚拟MAC地址，则PE-2执行如下操作中的至少一种：保存上述ARP请求报文q31携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明一些实施例中，PE-2确定上述ARP请求报文q31携带的源MAC地址是否为虚拟MAC地址可包括：若上述ARP请求报文q31携带的源MAC地址等同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2可确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2确定上述源MAC地址不是虚拟MAC地址。这种场景下主要是假设同一虚拟子网站点内的各PE设备关联相同的虚拟路由器为例进行说明的。
在本发明另一些实施例中，PE-2确定上述ARP请求报文q31携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可包括：上述PE-2查询PE-1关联的虚拟路由器对应的虚拟MAC地址，若上述ARP请求报文q31携带的源MAC地址等同于查询到的上述PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q31携带的源MAC地址为虚拟MAC地址；若上述ARP请求报文q31携带的源MAC地址不同于查询到的PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q31携带的源MAC地址不是虚拟MAC地址。
可以理解，上述PE-2也可能通过其它的方式来确定上述ARP请求报文q31携带的源媒介访问控制MAC地址是否为虚拟MAC地址。
504、PE-1接收ARP请求报文q31。此处，假设PE-1当前已经通过PE-4学习到了CE主机#004对应的CE主机路由，因此PE-1可作为ARP代理，发送用于响应ARP请求报文q31的ARP响应报文q32。其中，ARP响应报文q32携带的源MAC地址为PE-1关联的虚拟路由器对应的虚拟MAC地址，ARP响应 报文q32携带的源IP地址为CE主机#004的IP地址。
505、交换设备T1洪泛接收到的ARP响应报文q32。
PE-2和CE主机#002将可接收到上述ARP响应报文q32。
506、PE-2确定上述ARP响应报文q32携带的源MAC地址是否为虚拟MAC地址。
其中，若PE-2确定上述ARP响应报文q32携带的源MAC地址是虚拟MAC地址，PE-2不执行如下操作中的至少1种：保存上述ARP响应报文q32携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
若PE-2确定上述ARP响应报文q32携带的源MAC地址不是虚拟MAC地址，则PE-2执行如下操作中的至少一种：保存上述ARP响应报文q32携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明一些实施例中，PE-2确定上述ARP请求报文q31携带的源MAC地址是否为虚拟MAC地址可包括：若上述ARP请求报文q31携带的源MAC地址等同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2可确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2确定上述源MAC地址不是虚拟MAC地址。这种场景下主要是假设同一虚拟子网站点内的各PE设备关联相同的虚拟路由器为例进行说明的。
在本发明另一些实施例中，PE-2确定上述ARP响应报文q32携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可包括：上述PE-2查询PE-1关联的虚拟路由器对应的虚拟MAC地址，若上述ARP响应报文q32携带的源MAC地址等同于查询到的上述PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP响应报文q32携带的源MAC地址为虚拟MAC地址；若上述ARP响应报文q32携带的源MAC地址不同于查询到的PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上 述ARP响应报文q32携带的源MAC地址不是虚拟MAC地址。
可以理解，上述PE-2也可能通过其它的方式来确定上述ARP响应报文q32携带的源媒介访问控制MAC地址是否为虚拟MAC地址。
由上可见，本实施例的技术方案中，PE-2接收到ARP报文之后，PE-2先确定该ARP报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则PE-2不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或PE-2不基于三层VPN的路由协议在上述虚拟子网中分发上述源IP地址对应的本地CE主机路由，其中上述PE-2所位于的虚拟子网站点内还包括至少1个其它PE设备。研究发现，源MAC地址为虚拟MAC地址的ARP报文通常是PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的，因此PE-2对接收到的ARP报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对ARP报文是否为PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的情况的识别，而对应这种情况(即PE-2确定上述源MAC地址为虚拟MAC地址)，PE-2不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网之中分发上述源IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的保存(使用)和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，减少网络资源的浪费。
参见图6，图6是本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法的流程示意图。如图6所示，本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法可包括以下内容：
601、CE主机#001发送用于请求获得CE主机#004的MAC地址的ARP请求报文q11。其中，ARP请求报文q11携带CE主机#001的IP地址(即源IP地址)和MAC地址(即源MAC地址)，ARP请求报文q11还携带CE主机#004的IP地址等。
602、PE-1接收ARP请求报文q11。此处，假设PE-1当前已经通过PE-4学习到了CE主机#004对应的CE主机路由，因此PE-1可作为ARP代理，发送用于响应ARP请求报文q11的ARP响应报文q12。其中，ARP响应报文q12携带的源MAC地址为PE-1关联的虚拟路由器对应的虚拟MAC地址，ARP响应报文q12携带的源IP地址为CE主机#004的IP地址。
603、交换设备T1洪泛接收到的ARP响应报文q12。
PE-2和CE主机#001将可接收到上述ARP响应报文q12。
604、PE-2确定上述ARP响应报文q12携带的源MAC地址是否为虚拟MAC地址。
若否，则执行步骤605。
其中，若PE-2确定上述ARP响应报文q12携带的源MAC地址是虚拟MAC地址，PE-2不执行如下操作中的至少1种：保存上述ARP响应报文q12携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
605、PE-2若确定上述ARP响应报文q12携带的源MAC地址不是虚拟MAC地址，PE-2确定上述ARP响应报文q12携带的源MAC地址是否不同于白名单中记录的任意1个MAC地址。
PE-2若确定上述ARP响应报文q12携带的源MAC地址不同于白名单中记录的任意1个MAC地址，则PE-2可不执行如下操作的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
PE-2若确定上述ARP响应报文q12携带的源MAC地址等同于白名单中记录的其中1个MAC地址，则PE-2可执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
可以理解的是，由于进一步引入白名单控制机制，有利于更加灵活的实现路由分发控制。进一步的，上述PE-2还可以根据指令对上述白名单进 行更新。
在本发明一些实施例中，PE-2确定上述ARP请求报文q21携带的源MAC地址是否为虚拟MAC地址可包括：若上述ARP请求报文q21携带的源MAC地址等同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2可确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2确定上述源MAC地址不是虚拟MAC地址。这种场景下主要是假设同一虚拟子网站点内的各PE设备关联相同的虚拟路由器为例进行说明的。
在本发明另一些实施例中，PE-2确定上述ARP请求报文q21携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可包括：上述PE-2查询PE-1关联的虚拟路由器对应的虚拟MAC地址，若上述ARP请求报文q21携带的源MAC地址等同于查询到的上述PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q21携带的源MAC地址为虚拟MAC地址；若上述ARP请求报文q21携带的源MAC地址不同于查询到的PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q21携带的源MAC地址不是虚拟MAC地址。
可以理解，上述PE-2也可能通过其它的方式来确定上述ARP请求报文q21携带的源MAC地址是否为虚拟MAC地址。
由上可见，本实施例的技术方案中，PE-2接收到ARP响应报文之后，PE-2先确定该ARP报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则PE-2不保存上述ARP响应报文携带的源IP地址对应的本地CE主机路由表项，和/或PE-2不基于三层VPN的路由协议在上述虚拟子网中分发上述源IP地址对应的本地CE主机路由，其中，上述PE-2所位于的虚拟子网站点内还包括至少一个其它PE设备。研究发现，源MAC地址为虚拟MAC地址的ARP响应报文通常是PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的，因此，PE-2对接收到的ARP响应报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对ARP 响应报文是否为PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的情况的识别，而对应这种情况(即若PE-2确定上述源MAC地址为虚拟MAC地址)，PE-2不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网之中分发上述源IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的保存(使用)和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，减少网络资源的浪费。
参见图7，图7是本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法的流程示意图。本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法可包括以下内容：
701、PE-1作为ARP Proxy，代理CE主机#004发送ARP请求报文q21。
其中，ARP请求报文q21的源IP地址为CE主机#004的IP地址。此处假设PE-1当前已经学习到了CE主机#004对应的CE主机路由，因此ARP请求报文q21携带的源MAC地址可为PE-1对应的虚拟MAC地址。
702、交换设备T1洪泛其接收到的ARP请求报文q21。
PE-2将可接收到上述ARP请求报文q21。
703、PE-2确定上述ARP请求报文q21携带的源MAC地址是否为虚拟MAC地址。
若否，则执行步骤704。
其中，若PE-2确定上述ARP请求报文q21携带的源MAC地址是虚拟MAC地址，PE-2不执行如下操作中的至少1种：保存上述ARP请求报文q21携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
704、PE-2若确定上述ARP请求报文q21携带的源MAC地址不是虚拟MAC地址，PE-2确定上述ARP请求报文q21携带的源MAC地址是否不同于白名单中记录的任意1个MAC地址。
PE-2若确定上述ARP请求报文q21携带的源MAC地址不同于白名单中记录的任意1个MAC地址，则PE-2可不执行如下操作的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
PE-2若确定上述ARP请求报文q21携带的源MAC地址等同于白名单中记录的其中1个MAC地址，则PE-2可执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
可以理解的是，由于进一步引入白名单控制机制，有利于更加灵活的实现路由分发控制。进一步的，上述PE-2还可以根据指令对上述白名单进行更新。
在本发明一些实施例中，PE-2确定上述ARP请求报文q21携带的源MAC地址是否为虚拟MAC地址可包括：若上述ARP请求报文q21携带的源MAC地址等同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2可确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2确定上述源MAC地址不是虚拟MAC地址。这种场景下主要是假设同一虚拟子网站点内的各PE设备关联相同的虚拟路由器为例进行说明的。
在本发明另一些实施例中，PE-2确定上述ARP请求报文q21携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可包括：上述PE-2查询PE-1关联的虚拟路由器对应的虚拟MAC地址，若上述ARP请求报文q21携带的源MAC地址等同于查询到的上述PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q21携带的源MAC地址为虚拟MAC地址；若上述ARP请求报文q21携带的源MAC地址不同于查询到的PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q21携带的源MAC地址不是虚拟MAC地址。
可以理解，上述PE-2也可能通过其它的方式来确定上述ARP请求报文 q21携带的源MAC地址是否为虚拟MAC地址。
由上可见，本实施例的技术方案中，PE-2接收到ARP请求报文之后，PE-2先确定该ARP报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则PE-2不保存上述ARP请求报文携带的源IP地址对应的本地CE主机路由表项，和/或PE-2不基于三层VPN的路由协议在上述虚拟子网中分发上述源IP地址对应的本地CE主机路由，其中，上述PE-2所位于的虚拟子网站点内还包括至少一个其它PE设备。研究发现，源MAC地址为虚拟MAC地址的ARP请求报文通常是PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的，因此，PE-2对接收到的ARP请求报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对ARP请求报文是否为PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的情况的识别，而对应这种情况(即若PE-2确定上述源MAC地址为虚拟MAC地址)，PE-2不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网之中分发上述源IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的保存(使用)和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，减少网络资源的浪费。
参见图8，图8是本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法的流程示意图。本发明的另一个实施例提供的一种虚拟子网中的主机路由处理方法可包括以下内容：
801、CE主机#002发送用于请求获得CE主机#004的MAC地址的ARP请求报文q31。其中，ARP请求报文q31携带CE主机#002的IP地址(即源IP地址)和MAC地址(即源MAC地址)，ARP请求报文q31还携带CE主机#004的IP地址等。
802、交换设备T1洪泛接收到的ARP请求报文q31。
PE-1和PE-2将可接收到上述ARP请求报文q31。
803、PE-2确定上述ARP请求报文q31携带的源MAC地址是否为虚拟MAC地址。
若否，则执行步骤804。
其中，若PE-2确定上述ARP请求报文q31携带的源MAC地址是虚拟MAC地址，PE-2不执行如下操作中的至少1种：保存上述ARP请求报文q31携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
804、PE-2若确定上述ARP请求报文q31携带的源MAC地址不是虚拟MAC地址，PE-2确定上述ARP请求报文q31携带的源MAC地址是否不同于白名单中记录的任意1个MAC地址，
PE-2若确定上述ARP请求报文q31携带的源MAC地址不同于白名单中记录的任意1个MAC地址，则PE-2可不执行如下操作的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
PE-2若确定上述ARP请求报文q31携带的源MAC地址等同于白名单中记录的其中1个MAC地址，则PE-2可执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
可以理解的是，由于进一步引入白名单控制机制，有利于更加灵活的实现路由分发控制。进一步的，上述PE-2还可以根据指令对上述白名单进行更新。
在本发明一些实施例中，PE-2确定上述ARP请求报文q31携带的源MAC地址是否为虚拟MAC地址可包括：若上述ARP请求报文q31携带的源MAC地址等同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2可确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2确定上述源MAC地址不是虚拟MAC地址。这种场景下主要是假设同一虚拟子网站点内 的各PE设备关联相同的虚拟路由器为例进行说明的。
在本发明另一些实施例中，PE-2确定上述ARP请求报文q31携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可包括：上述PE-2查询PE-1关联的虚拟路由器对应的虚拟MAC地址，若上述ARP请求报文q31携带的源MAC地址等同于查询到的上述PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q31携带的源MAC地址为虚拟MAC地址；若上述ARP请求报文q31携带的源MAC地址不同于查询到的PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP请求报文q31携带的源MAC地址不是虚拟MAC地址。
可以理解，上述PE-2也可能通过其它的方式来确定上述ARP请求报文q31携带的源媒介访问控制MAC地址是否为虚拟MAC地址。
805、PE-1接收ARP请求报文q31。此处，假设PE-1当前已经通过PE-4学习到了CE主机#004对应的CE主机路由，因此PE-1可作为ARP代理，发送用于响应ARP请求报文q31的ARP响应报文q32。其中，ARP响应报文q32携带的源MAC地址为PE-1关联的虚拟路由器对应的虚拟MAC地址，ARP响应报文q32携带的源IP地址为CE主机#004的IP地址。
806、交换设备T1洪泛接收到的ARP响应报文q32。
PE-2和CE主机#002将可接收到上述ARP响应报文q32。
807、PE-2确定上述ARP响应报文q32携带的源MAC地址是否为虚拟MAC地址。
若否，则执行步骤808。
其中，若PE-2确定上述ARP请求报文q31携带的源MAC地址是虚拟MAC地址，PE-2不执行如下操作中的至少1种：保存上述ARP请求报文q31携带的源IP地址对应的本地CE主机路由表项、基于三层VPN的路由协议(如网关边界协议等)在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
808、PE-2若确定上述ARP响应报文q32携带的源MAC地址不是虚拟MAC地址，PE-2确定上述ARP响应报文q32携带的源MAC地址是否不同 于白名单中记录的任意1个MAC地址。
PE-2若确定上述ARP响应报文q32携带的源MAC地址不同于白名单中记录的任意1个MAC地址，则PE-2可不执行如下操作的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
PE-2若确定上述ARP响应报文q32携带的源MAC地址等同于白名单中记录的其中1个MAC地址，则PE-2可执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明一些实施例中，PE-2确定上述ARP响应报文q32携带的源MAC地址是否为虚拟MAC地址可包括：若上述ARP响应报文q32携带的源MAC地址等同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2可确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述PE-2关联的虚拟路由器对应的虚拟MAC地址，则PE-2确定上述源MAC地址不是虚拟MAC地址。这种场景下主要是假设同一虚拟子网站点内的各PE设备关联相同的虚拟路由器为例进行说明的。
在本发明另一些实施例中，PE-2确定上述ARP响应报文q32携带的源媒介访问控制MAC地址是否为虚拟MAC地址，可包括：上述PE-2查询PE-1关联的虚拟路由器对应的虚拟MAC地址，若上述ARP响应报文q32携带的源MAC地址等同于查询到的上述PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP响应报文q32携带的源MAC地址为虚拟MAC地址；若上述ARP响应报文q32携带的源MAC地址不同于查询到的PE-1关联的虚拟路由器对应的虚拟MAC地址，则PE-2可以确定上述ARP响应报文q32携带的源MAC地址不是虚拟MAC地址。
可以理解，上述PE-2也可能通过其它的方式来确定上述ARP响应报文q32携带的源MAC地址是否为虚拟MAC地址。
由上可见，本实施例的技术方案中，PE-2接收到ARP报文之后，PE-2先 确定该ARP报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则PE-2不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或PE-2不基于三层VPN的路由协议在上述虚拟子网中分发上述源IP地址对应的本地CE主机路由，其中上述PE-2所位于的虚拟子网站点内还包括至少1个其它PE设备。研究发现，源MAC地址为虚拟MAC地址的ARP报文通常是第一PE所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的，因此PE-2对接收到的ARP报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对ARP报文是否为PE-2所位于的虚拟子网站点内的其它PE设备作为ARP代理而发送的情况的识别，而对应这种情况(即PE-2确定上述源MAC地址为虚拟MAC地址)，PE-2不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网之中分发上述源IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的保存(使用)和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，减少网络资源的浪费。
可以理解的是，上述图3～图8所对应的实施例中主要是针对ARP场景进行举例描述的，针对ND协议的场景与之类似。其中，NS报文类似于ARP请求报文，NA报文类似于ARP响应报文。其中，上述图3～图8所对应的实施例中的PE-2类似于图2所对应实施例中的第一PE设备。
本发明实施例还提供用于实施上述方案的相关装置。
参见图9，本发明实施例提供一种运营商边界设备900可包括：接收单元910和处理单元920。
接收单元910，用于接收用于地址解析的报文，上述运营商边界设备所位于的虚拟子网站点内还包括至少一个第二运营商边界设备。
其中，可以理解的是，接收单元910接收到的用于地址解析的报文可能来自某个第二PE设备，也可能来自运营商边界设备900所位于的虚拟 子网站点内的某个CE设备。
其中，上述用于地址解析的报文可为ARP报文或ND协议报文或其它用于地址解析的报文。
在本发明的一些实施例中，上述ARP报文可为ARP请求报文或ARP响应报文。上述ND协议报文可为NS报文或NA报文。
处理单元920，用于确定上述报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则不执行如下操作中的至少一种：保存上述报文携带的源IP地址对应的本地客户边界CE主机路由表项、基于三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
此外，若确定上述源MAC地址为虚拟MAC地址，处理单元920也可不保存ARP条目或ND协议条目，其中，ARP条目中记录上述ARP报文携带的源IP地址和源MAC地址之间的映射关系。ND协议条目中记录上述ND协议报文携带的源IP地址和源MAC地址之间的映射关系。
在本发明的一些实施例中，处理单元920还用于，若确定上述源MAC地址不是虚拟MAC地址，则执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，处理单元920还用于，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址不同于白名单中记录的任意1个MAC地址，则不执行如下操作的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由；
和/或，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址等同于白名单中记录的其中1个MAC地址，则执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚 拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，处理单元920还用于，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址不同于黑名单中记录的任意1个MAC地址，则执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由；
和/或，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址等同于黑名单中记录的其中1个MAC地址，则不执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，在上述确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，处理单元920具体用于：若上述报文携带的源MAC地址等同于上述运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址不是虚拟MAC地址。
在本发明的一些实施例中，在上述确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，处理单元920具体用于：查询上述至少一个第二运营商边界设备对应的虚拟MAC地址，若上述报文携带的源MAC地址等同于查询到的上述至少一个第二运营商边界设备之中的其中一个第二运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址为虚拟MAC地址；若上述报文携带的源MAC地址不同于查询到的上述至少一个第二运营商边界设备之中的任意一个第二运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址不是虚拟MAC地址。
在本发明一些实施例中，PE设备(如运营商边界设备900或第二PE设备)对应的虚拟MAC地址具体可以是，PE设备关联的虚拟路由器对应 的虚拟MAC地址。
可以理解的是，PE设备保存的本地CE主机路由表项指向PE设备所处站点之内的CE主机。PE设备分发的本地CE主机路由指向该PE设备所处站点之内的CE主机。其中，在本发明实施例中，PE设备保存的本地CE主机路由表项可包含CE主机的IP地址和下一跳地址。其中，在本发明实施例中，PE设备分发的本地CE主机路由可包含CE主机的IP地址和下一跳地址。
可以理解的是，本实施例的运营商边界设备900的各功能模块的功能可根据上述方法实施例中的方法具体实现，其具体实现过程可以参照上述方法实施例的相关描述，此处不再赘述。
由上可见，本发明实施例的技术方案中，当PE设备900接收到用于地址解析的报文之后，PE设备900先确定该用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由，其中，上述PE设备900所位于的虚拟子网站点内还包括至少一个第二PE设备。研究发现，源MAC地址为虚拟MAC地址的用于地址解析的报文通常是第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的，因此，PE设备900对接收到的用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对用于地址解析的报文是否为第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的情况的识别，而对应这种情况(即若确定上述源MAC地址为虚拟MAC地址)，PE设备900不保存上述用于地址解析的报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网之中分发上述IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的存储和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下，尽 量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，减少网络资源的浪费。
参见图10，图10为本发明实施例提供的PE设备1000的示意图，PE设备1000可包括至少一个总线1001、与总线1001相连的至少一个处理器1002以及与总线1001相连的至少一个存储器1003。
其中，处理器1002通过总线1001，调用存储器1003中存储的代码以用于接收用于地址解析的报文；确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则不执行如下操作中的至少一种：保存上述报文携带的源网际互联协议IP地址对应的本地客户边界CE主机路由表项、基于三层虚拟私有网络VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。其中上述PE设备1000所位于的虚拟子网站点内还包括至少一个第二运营商边界设备。
其中，上述用于地址解析的报文可为ARP报文或ND协议报文或其它用于地址解析的报文。
此外，若确定上述源MAC地址为虚拟MAC地址，处理器1002也可不保存ARP条目或ND协议条目，其中，ARP条目中记录上述ARP报文携带的源IP地址和源MAC地址之间的映射关系。ND协议条目中记录上述ND协议报文携带的源IP地址和源MAC地址之间的映射关系。
在本发明的一些实施例中，处理器1002还用于，若确定上述源MAC地址不是虚拟MAC地址，则执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，处理器1002还用于，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址不同于白名单中记录的任意1个MAC地址，则不执行如下操作的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚 拟子网中分发上述IP地址对应的本地CE主机路由；
和/或，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址等同于白名单中记录的其中1个MAC地址，则执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，处理器1002还用于，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址不同于黑名单中记录的任意1个MAC地址，则执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由；
和/或，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址等同于黑名单中记录的其中1个MAC地址，则不执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，在上述确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，处理器1002具体用于：若上述报文携带的源MAC地址等同于上述运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址不是虚拟MAC地址。
在本发明的一些实施例中，在上述确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，处理器1002具体用于：查询上述至少一个第二运营商边界设备对应的虚拟MAC地址，若上述报文携带的源MAC地址等同于查询到的上述至少一个第二运营商边界设备之中的其中一个第二运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址 为虚拟MAC地址；若上述报文携带的源MAC地址不同于查询到的上述至少一个第二运营商边界设备之中的任意一个第二运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址不是虚拟MAC地址。
在本发明一些实施例中，PE设备(如运营商边界设备1000或第二PE设备)对应的虚拟MAC地址具体可以是，PE设备关联的虚拟路由器对应的虚拟MAC地址。
可以理解的是，PE设备保存的本地CE主机路由表项指向PE设备所处站点之内的CE主机。PE设备分发的本地CE主机路由指向该PE设备所处站点之内的CE主机。其中，在本发明实施例中，PE设备保存的本地CE主机路由表项可包含CE主机的IP地址和下一跳地址。其中，在本发明实施例中，PE设备分发的本地CE主机路由可包含CE主机的IP地址和下一跳地址。
可以理解的是，本实施例的运营商边界设备1000的各功能模块的功能可根据上述方法实施例中的方法具体实现，其具体实现过程可以参照上述方法实施例的相关描述，此处不再赘述。
由上可见，本发明实施例的技术方案中，当PE设备1000接收到用于地址解析的报文之后，PE设备1000先确定该用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由，其中，上述PE设备1000所位于的虚拟子网站点内还包括至少一个第二PE设备。研究发现，源MAC地址为虚拟MAC地址的用于地址解析的报文通常是第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的，因此，PE设备1000对接收到的用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对用于地址解析的报文是否为第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的情况的识别，而对应这种情况(即 若确定上述源MAC地址为虚拟MAC地址)，PE设备1000不保存上述用于地址解析的报文携带的源IP地址对应的本地CE主机路由表项，和/或，PE设备1000不基于三层VPN的路由协议在上述虚拟子网之中分发上述IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的存储和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，减少网络资源的浪费。
参见图11，图11是本发明的另一个实施例提供的PE设备1100的结构框图。其中，PE设备1100可以包括：至少1个处理器1101，至少1个网络接口1104或其他用户接口1103，存储器1105，至少1个通信总线1102。通信总线1102用于实现这些组件之间的连接通信。其中，该PE设备1100可选的包含用户接口1103，包括显示器(例如，触摸屏、LCD、CRT、全息成像(Holographic)或者投影(Projector)等)、点击设备(例如鼠标、轨迹球(trackball)触感板或触摸屏等)、摄像头和/或拾音装置等。
其中，存储器1102可以包括只读存储器和随机存取存储器，并向处理器1101提供指令和数据。存储器1102中的一部分还可以包括非易失性随机存取存储器(NVRAM)。
在一些实施方式中，存储器1105存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：
操作系统11051，包含各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。
应用程序模块11052，包含各种应用程序，用于实现各种应用业务。
应用程序模块11052中包括但不限于集合确接收单元910和处理单元920等。
在本发明实施例中，通过调用存储器1105存储的程序或指令，处理器1101用于接收用于地址解析的报文；确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则 不执行如下操作中的至少一种：保存上述报文携带的源网际互联协议IP地址对应的本地客户边界CE主机路由表项、基于三层虚拟私有网络VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。其中上述PE设备1100所位于的虚拟子网站点内还包括至少一个第二运营商边界设备。
其中，上述用于地址解析的报文可为ARP报文或ND协议报文或其它用于地址解析的报文。
此外，若确定上述源MAC地址为虚拟MAC地址，处理器1101也可不保存ARP条目或ND协议条目，其中，ARP条目中记录上述ARP报文携带的源IP地址和源MAC地址之间的映射关系。ND协议条目中记录上述ND协议报文携带的源IP地址和源MAC地址之间的映射关系。
在本发明的一些实施例中，处理器1101还用于，若确定上述源MAC地址不是虚拟MAC地址，则执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，处理器1101还用于，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址不同于白名单中记录的任意1个MAC地址，则不执行如下操作的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由；
和/或，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址等同于白名单中记录的其中1个MAC地址，则执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，处理器1101还用于，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址不同 于黑名单中记录的任意1个MAC地址，则执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由；
和/或，
若确定上述源MAC地址不是虚拟MAC地址，且上述源MAC地址等同于黑名单中记录的其中1个MAC地址，则不执行如下操作中的至少一种：保存上述源IP地址对应的本地CE主机路由表项、基于上述路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由。
在本发明的一些实施例中，在上述确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，处理器1101具体用于：若上述报文携带的源MAC地址等同于上述运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址为虚拟MAC地址；若上述源MAC地址不同于上述运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址不是虚拟MAC地址。
在本发明的一些实施例中，在上述确定上述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，处理器1101具体用于：查询上述至少一个第二运营商边界设备对应的虚拟MAC地址，若上述报文携带的源MAC地址等同于查询到的上述至少一个第二运营商边界设备之中的其中一个第二运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址为虚拟MAC地址；若上述报文携带的源MAC地址不同于查询到的上述至少一个第二运营商边界设备之中的任意一个第二运营商边界设备对应的虚拟MAC地址，则确定上述源MAC地址不是虚拟MAC地址。
在本发明一些实施例中，PE设备(如运营商边界设备1100或第二PE设备)对应的虚拟MAC地址具体可以是，PE设备关联的虚拟路由器对应的虚拟MAC地址。
可以理解的是，PE设备保存的本地CE主机路由表项指向PE设备所处站点之内的CE主机。PE设备分发的本地CE主机路由指向该PE设备 所处站点之内的CE主机。其中，在本发明实施例中，PE设备保存的本地CE主机路由表项可包含CE主机的IP地址和下一跳地址。其中，在本发明实施例中，PE设备分发的本地CE主机路由可包含CE主机的IP地址和下一跳地址。
可以理解的是，本实施例的运营商边界设备1100的各功能模块的功能可根据上述方法实施例中的方法具体实现，其具体实现过程可以参照上述方法实施例的相关描述，此处不再赘述。
由上可见，本发明实施例的技术方案中，当PE设备1100接收到用于地址解析的报文之后，PE设备1100先确定该用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址；若确定上述源MAC地址为虚拟MAC地址，则不保存上述ARP报文携带的源IP地址对应的本地CE主机路由表项，和/或不基于三层VPN的路由协议在上述虚拟子网中分发上述IP地址对应的本地CE主机路由，其中，上述PE设备1100所位于的虚拟子网站点内还包括至少一个第二PE设备。研究发现，源MAC地址为虚拟MAC地址的用于地址解析的报文通常是第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的，因此，PE设备1100对接收到的用于地址解析的报文携带的源MAC地址是否为虚拟MAC地址进行识别确认，进而实现对用于地址解析的报文是否为第一PE所位于的虚拟子网站点内的其它PE设备作为地址解析代理而发送的情况的识别，而对应这种情况(即若确定上述源MAC地址为虚拟MAC地址)，PE设备1100不保存上述用于地址解析的报文携带的源IP地址对应的本地CE主机路由表项，和/或，PE设备1100不基于三层VPN的路由协议在上述虚拟子网之中分发上述IP地址对应的本地CE主机路由，这样就有利于在根源上消除PE设备对错误CE主机路由的存储和/或分发，进而有利于在虚拟子网的一些站点内存在多个PE设备场景下，尽量避免形成CE主机路由环路，进而提升CE主机之间传输数据包的效率，减少网络资源的浪费。
参见图12，本发明实施例还提供一种通信系统，可包括：
多个运营商边界设备1210，其中，上述多个运营商边界设备1210中的至少一个可如运营商边界设备900或者运营商边界设备1100或者运营商边界设备1100。
本发明实施例还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时包括上述方法实施例中记载的虚拟子网中的主机路由处理方法的部分或全部步骤。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置，可通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单 元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等，具体可以是计算机设备中的处理器)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质可包括：U盘、磁碟、随机存取存储器(RAM，random access memory)、只读存储器(ROM，read-only memory)或移动硬盘或光盘等各种可以存储程序代码的介质。
以上所述，以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims (15)

  1. 一种虚拟子网中的主机路由处理方法，其特征在于，包括：
    第一运营商边界设备接收用于地址解析的报文，所述第一运营商边界设备所位于的虚拟子网站点内还包括至少一个第二运营商边界设备；
    所述第一运营商边界设备确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址；
    若确定所述源MAC地址为虚拟MAC地址，则不执行如下操作中的至少一种：保存所述报文携带的源网际互联协议IP地址对应的本地客户边界CE主机路由表项、基于三层虚拟私有网络VPN的路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
  2. 根据权利要求1所述的方法，其特征在于，
    所述方法还包括：
    若确定所述源MAC地址不是虚拟MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
  3. 根据权利要求1所述的方法，其特征在于，
    所述方法还包括：
    若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址不同于白名单中记录的任意1个MAC地址，则不执行如下操作的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由；
    和/或，
    若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址等同于白名单中记录的其中1个MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
  4. 根据权利要求1所述的方法，其特征在于，
    所述方法还包括：
    若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址不同于黑名单中记录的任意1个MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由；
    和/或，
    若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址等同于黑名单中记录的其中1个MAC地址，则不执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，
    所述确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址包括：若所述报文携带的源MAC地址等同于所述第一运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址为虚拟MAC地址；若所述源MAC地址不同于所述第一运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址不是虚拟MAC地址。
  6. 根据权利要求1至4任一项所述的方法，其特征在于，
    所述确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址包括：
    查询所述至少一个第二运营商边界设备对应的虚拟MAC地址，若所述报文携带的源MAC地址等同于查询到的所述至少一个第二运营商边界设备之中的其中一个第二运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址为虚拟MAC地址；若所述报文携带的源MAC地址不同于查询到的所述至少一个第二运营商边界设备之中的任意一个第二运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址不是虚拟MAC地址。
  7. 根据权利要求1至6任一项所述的方法，其特征在于，所述报文为 地址解析协议ARP报文或邻居发现ND协议报文。
  8. 一种运营商边界设备，其特征在于，包括：
    接收单元，用于接收用于地址解析的报文，所述运营商边界设备所位于的虚拟子网站点内还包括至少一个第二运营商边界设备；
    处理单元，用于确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址；若确定所述源MAC地址为虚拟MAC地址，则不执行如下操作中的至少一种：保存所述报文携带的源网际互联协议IP地址对应的本地客户边界CE主机路由表项、基于三层虚拟私有网络VPN的路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
  9. 根据权利要求8所述的运营商边界设备，其特征在于，所述处理单元还用于，若确定所述源MAC地址不是虚拟MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
  10. 根据权利要求8所述的运营商边界设备，其特征在于，
    所述处理单元还用于，
    若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址不同于白名单中记录的任意1个MAC地址，则不执行如下操作的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由；
    和/或，
    若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址等同于白名单中记录的其中1个MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
  11. 根据权利要求8所述的运营商边界设备，其特征在于，
    所述处理单元还用于，
    若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址不同 于黑名单中记录的任意1个MAC地址，则执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由；
    和/或，
    若确定所述源MAC地址不是虚拟MAC地址，且所述源MAC地址等同于黑名单中记录的其中1个MAC地址，则不执行如下操作中的至少一种：保存所述源IP地址对应的本地CE主机路由表项、基于所述路由协议在所述虚拟子网中分发所述IP地址对应的本地CE主机路由。
  12. 根据权利要求8至11任一项所述的运营商边界设备，其特征在于，
    在所述确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，所述处理单元具体用于：若所述报文携带的源MAC地址等同于所述运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址为虚拟MAC地址；若所述源MAC地址不同于所述运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址不是虚拟MAC地址。
  13. 根据权利要求8至11任一项所述的运营商边界设备，其特征在于，
    在所述确定所述报文携带的源媒介访问控制MAC地址是否为虚拟MAC地址的方面，所述处理单元具体用于：查询所述至少一个第二运营商边界设备对应的虚拟MAC地址，若所述报文携带的源MAC地址等同于查询到的所述至少一个第二运营商边界设备之中的其中一个第二运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址为虚拟MAC地址；若所述报文携带的源MAC地址不同于查询到的所述至少一个第二运营商边界设备之中的任意一个第二运营商边界设备对应的虚拟MAC地址，则确定所述源MAC地址不是虚拟MAC地址。
  14. 根据权利要求8至13任一项所述的运营商边界设备，其特征在于，所述报文为地址解析协议ARP报文或邻居发现ND协议报文。
  15. 一种通信系统，其特征在于，包括：
    多个运营商边界设备，其中，所述多个运营商边界设备中的至少一个 为如权利要求8至14任一项所述的运营商边界设备。
PCT/CN2015/070045 2014-02-21 2015-01-04 虚拟子网中的主机路由处理方法及相关设备和通信系统 WO2015124041A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2016553302A JP6456398B2 (ja) 2014-02-21 2015-01-04 仮想サブネット内のホストルートの処理方法、関連デバイスおよび通信システム
EP15751835.8A EP3110087B1 (en) 2014-02-21 2015-01-04 Processing method and related device for host route in virtual sub-network, and communication system
US15/242,087 US10148568B2 (en) 2014-02-21 2016-08-19 Method for processing host route in virtual subnet, related device, and communications system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410060262.7 2014-02-21
CN201410060262.7A CN104869063B (zh) 2014-02-21 2014-02-21 虚拟子网中的主机路由处理方法及相关设备和通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/242,087 Continuation US10148568B2 (en) 2014-02-21 2016-08-19 Method for processing host route in virtual subnet, related device, and communications system

Publications (1)

Publication Number Publication Date
WO2015124041A1 true WO2015124041A1 (zh) 2015-08-27

Family

ID=53877622

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/070045 WO2015124041A1 (zh) 2014-02-21 2015-01-04 虚拟子网中的主机路由处理方法及相关设备和通信系统

Country Status (5)

Country Link
US (1) US10148568B2 (zh)
EP (1) EP3110087B1 (zh)
JP (1) JP6456398B2 (zh)
CN (1) CN104869063B (zh)
WO (1) WO2015124041A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105577536A (zh) * 2016-01-29 2016-05-11 华为技术有限公司 一种报文处理方法以及网络设备
CN111064668A (zh) * 2018-10-17 2020-04-24 华为技术有限公司 路由表项的生成方法、装置及相关设备
US11943637B2 (en) * 2018-08-23 2024-03-26 John Mezzalingua Associates, LLC System and method for creating and managing private subnetworks of LTE base stations

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105791457B (zh) * 2016-02-26 2019-04-09 新华三技术有限公司 一种数据处理方法及装置
US10027589B1 (en) * 2016-06-30 2018-07-17 Juniper Network, Inc. Apparatus, system, and method for achieving redundancy and load-balancing across communication layers within networks
CN109729010B (zh) * 2017-10-27 2021-06-22 华为技术有限公司 一种网络中确定流量传输路径的方法、设备和系统
CN109962846B (zh) * 2017-12-25 2020-09-25 华为技术有限公司 路由协议报文的处理方法及装置
CN108600106B (zh) * 2018-04-28 2019-06-14 北京邮电大学 一种低时延的数据交换装置及方法
US11159420B2 (en) * 2019-04-17 2021-10-26 Cloudflare, Inc. Method and apparatus of automatic route optimization in a private virtual network for client devices of a local network
US11108735B2 (en) 2019-06-07 2021-08-31 Microsoft Technology Licensing, Llc Mapping subnets in different virtual networks using private address space
US11977908B2 (en) * 2021-07-09 2024-05-07 Dish Wireless L.L.C. Streamlining the execution of software such as radio access network distributed units
CN113497765B (zh) * 2021-09-08 2021-11-30 中兴通讯股份有限公司 一种路由管理的方法、装置、电子设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040088389A1 (en) * 2002-11-05 2004-05-06 Tenor Networks, Inc. Methods and apparatus for automated edge device configuration in a heterogeneous network
CN101072238A (zh) * 2007-07-09 2007-11-14 中兴通讯股份有限公司 在mpls三层虚拟专用网中实现同一子网通信的方法
CN101075933A (zh) * 2007-06-29 2007-11-21 华为技术有限公司 学习mac地址的方法及网元设备
CN102164091A (zh) * 2011-05-13 2011-08-24 北京星网锐捷网络技术有限公司 一种mac地址表建立方法及运营商边缘设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7260648B2 (en) * 2001-01-25 2007-08-21 Ericsson, Inc. Extension of address resolution protocol (ARP) for internet protocol (IP) virtual networks
US7436783B2 (en) * 2005-04-04 2008-10-14 Apple Inc. Method and apparatus for detecting a router that improperly responds to ARP requests
US20070192858A1 (en) * 2006-02-16 2007-08-16 Infoexpress, Inc. Peer based network access control
US8144698B2 (en) * 2006-06-09 2012-03-27 Ericsson Ab Scalable data forwarding techniques in a switched network
JP4899959B2 (ja) * 2007-03-19 2012-03-21 富士通株式会社 Ｖｐｎ装置
US20090063706A1 (en) * 2007-08-30 2009-03-05 International Business Machines Corporation Combined Layer 2 Virtual MAC Address with Layer 3 IP Address Routing
US7948993B2 (en) * 2009-04-24 2011-05-24 Telefonaktiebolaget L M Ericsson (Publ) Address resolution optimization procedure to effect a gradual cutover from a provider bridge network to a VPLS or provider backbone bridging network
US8989187B2 (en) * 2010-06-04 2015-03-24 Coraid, Inc. Method and system of scaling a cloud computing network
JP5678678B2 (ja) * 2011-01-18 2015-03-04 富士通株式会社 プロバイダ網及びプロバイダエッジ装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040088389A1 (en) * 2002-11-05 2004-05-06 Tenor Networks, Inc. Methods and apparatus for automated edge device configuration in a heterogeneous network
CN101075933A (zh) * 2007-06-29 2007-11-21 华为技术有限公司 学习mac地址的方法及网元设备
CN101072238A (zh) * 2007-07-09 2007-11-14 中兴通讯股份有限公司 在mpls三层虚拟专用网中实现同一子网通信的方法
CN102164091A (zh) * 2011-05-13 2011-08-24 北京星网锐捷网络技术有限公司 一种mac地址表建立方法及运营商边缘设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3110087A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105577536A (zh) * 2016-01-29 2016-05-11 华为技术有限公司 一种报文处理方法以及网络设备
US11943637B2 (en) * 2018-08-23 2024-03-26 John Mezzalingua Associates, LLC System and method for creating and managing private subnetworks of LTE base stations
CN111064668A (zh) * 2018-10-17 2020-04-24 华为技术有限公司 路由表项的生成方法、装置及相关设备
CN111064668B (zh) * 2018-10-17 2022-06-14 华为技术有限公司 路由表项的生成方法、装置及相关设备

Also Published As

Publication number Publication date
JP2017506468A (ja) 2017-03-02
EP3110087A1 (en) 2016-12-28
EP3110087A4 (en) 2017-02-22
US20160373356A1 (en) 2016-12-22
US10148568B2 (en) 2018-12-04
CN104869063B (zh) 2019-02-12
EP3110087B1 (en) 2019-04-17
JP6456398B2 (ja) 2019-01-23
CN104869063A (zh) 2015-08-26

Similar Documents

Publication Publication Date Title
WO2015124041A1 (zh) 虚拟子网中的主机路由处理方法及相关设备和通信系统
US9281955B2 (en) Interoperability of data plane based overlays and control plane based overlays in a network environment
US9448821B2 (en) Method and system for realizing virtual machine mobility
WO2018040530A1 (zh) 一种确定虚拟机迁移的方法和装置
US20150358232A1 (en) Packet Forwarding Method and VXLAN Gateway
CN110798403B (zh) 通信方法、通信设备和通信系统
US20140075047A1 (en) Network-Assisted Virtual Machine Mobility
US20170331641A1 (en) Deployment Of Virtual Extensible Local Area Network
WO2018214809A1 (zh) 消息发送方法及装置、存储介质
JP2020520612A (ja) パケット伝送方法、エッジデバイス及び機械可読記憶媒体
JP7053901B2 (ja) ループ回避通信方法、ループ回避通信デバイスおよびループ回避通信システム
WO2019091088A1 (zh) 一种vxlan的配置方法、设备及系统
WO2012119390A1 (zh) 虚拟机迁移通知方法和系统
US20210328922A1 (en) Packet forwarding method and network device
JP2023518594A (ja) Ｍａｃアドレス送信方法、装置、およびシステム、ならびに関連デバイス
US11929851B2 (en) Gateway selection method, device, and system
EP4152701A1 (en) Routing processing method and related device
WO2009121265A1 (zh) 一种多归属多地址空间网络中实现流量工程的方法和设备
EP3021529B1 (en) Method and device for implementing layer 3 virtual private network
WO2022199486A1 (zh) 路径跟踪方法、设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15751835

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2016553302

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015751835

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015751835

Country of ref document: EP