WO2019091088A1 - 一种vxlan的配置方法、设备及系统 - Google Patents

一种vxlan的配置方法、设备及系统 Download PDF

Info

Publication number
WO2019091088A1
WO2019091088A1 PCT/CN2018/088038 CN2018088038W WO2019091088A1 WO 2019091088 A1 WO2019091088 A1 WO 2019091088A1 CN 2018088038 W CN2018088038 W CN 2018088038W WO 2019091088 A1 WO2019091088 A1 WO 2019091088A1
Authority
WO
WIPO (PCT)
Prior art keywords
vtep
information
network device
vni
network
Prior art date
Application number
PCT/CN2018/088038
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 EP18876451.8A priority Critical patent/EP3694157B1/en
Publication of WO2019091088A1 publication Critical patent/WO2019091088A1/zh
Priority to US16/861,914 priority patent/US11310080B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4675—Dynamic sharing of VLAN information amongst network nodes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, a device, and a system for configuring a virtual extensible local network (VXLAN).
  • VXLAN virtual extensible local network
  • VXLAN is a technology for encapsulating Layer 2 packets with a Layer 3 protocol.
  • VXLAN technology involves messages in the MAC-in-UDP format. Specifically, the Ethernet frame based on the Media Access Control (MAC) protocol is encapsulated in a user datagram protocol (UDP) packet. Further, the UDP packet is encapsulated in an Internet Protocol (IP) packet, and the IP packet can be transmitted in the Layer 3 network. Therefore, Ethernet frames are transmitted in a three-layer network.
  • the VXLAN technology uses a VXLAN network identifier (VNI) to identify a VXLAN segment. Different VXLAN segments correspond to different VNIs. Different VXLAN segments are isolated.
  • VNI VXLAN network identifier
  • the VXLAN L3 gateway does not need to communicate with two virtual machines (VMs) in the same VNI. Two VMs located in different VNIs need to communicate via a VXLAN Layer 3 gateway.
  • the VNI field contains 24 bits.
  • An administrative domain can contain up to 2 16 VXLAN segments.
  • the VXLAN tunnel end point (VTEP) can be integrated into a network virtualization edge (NVE) device as an edge device in the VXLAN.
  • the NVE device transmits VXLAN traffic through a VXLAN tunnel.
  • a VXLAN tunnel is a point-to-point logical tunnel between two NVE devices.
  • VXLAN is mainly configured manually.
  • the configuration process includes: Step1, the user performs overall network planning, and confirms dev1 and dev2. Between dev1 and dev3, you need to establish a VXLAN tunnel, and confirm the IP addresses to be used on the interfaces of each device in dev1, dev2, and dev3, the VNIs required by each device, and the access points of each device.
  • Step2 User Configure the loopback address, the interface address and network segment of the device, and the routing protocol for each device.
  • Step 3 Configure the div1, dev2, and dev3 respectively.
  • Step 4 the user sends the configuration to dev1, dev2, and dev3 respectively, configures the Layer 2 sub-interface of each device, and the BD to which the VM connected to the Layer 2 sub-interface belongs, and configures the VNI for each BD.
  • Etc. wherein the VNI is used to indicate the BD to which the VM belongs, and the BD may be referred to as a broadcast domain (BD) or a bridge domain (BD).
  • the present application provides a VXLAN configuration method, device, and system, which solves the problem of low configuration efficiency and high error rate when VXLAN is configured.
  • a VXLAN configuration method acquires configuration information, where the configuration information includes a plurality of VTEP device information, where the plurality of VTEP device information are respectively used to indicate a plurality of VTEPs included in the VXLAN; and the first network device is configured according to the The information generates a first generic autonomic signaling protocol (GRASP) information, where the first GRASP information includes target information, and the objective information is used to carry the configuration information, the first network device Running an autonomic networking integrated model and approach (ANIMA) protocol; the first network device sends the first GRASP information to a second network device, where the first GRASP information is used to trigger the The second network device establishes a VXLAN tunnel according to the first GRASP information.
  • GRASP generic autonomic signaling protocol
  • ANIMA autonomic networking integrated model and approach
  • the first network device may obtain configuration information for indicating multiple VTEPs included in the VXLAN, and carry the configuration information in the GRASP information and send the information to the second network device, where the second network device may be configured according to the second network device.
  • the GRASP information creates a VXLAN tunnel.
  • the VXLAN configuration is completed through information exchange between network devices, thereby realizing the automatic configuration of the VXLAN, thereby avoiding the problem that the existing configuration VXLAN is inefficient and has a high error rate.
  • each of the plurality of VTEP device information includes a VTEP device identifier and a VNI, wherein the VTEP device identifier corresponds to the VNI.
  • the first network device determines that the device identifier of the first network device is the same as the first VTEP device identifier included in the first VTEP device information, the first network device determines that the first network device is the first VTEP, The first VTEP device information is used to indicate the first VTEP; the first network device generates first VTEP information according to the first VTEP device information, where the first VTEP device information further includes The first VTEP device identifier corresponds to the first VNI, the first VTEP information includes a first VTEP address and the first VNI, and the first VTEP address is bound to the first VNI; the first network device Sending second GRASP information to the second network device, the second GRASP information including the first VTEP information.
  • the first network device may determine that it is a VTEP according to the content included in the configuration information, and generate its own VTEP information, and carry its own VTEP information in the GRASP information and send it to the second network device, so as to be the second network.
  • the device automatically creates a VXLAN tunnel from the second network device to the first network device according to the VTEP information of the first network device and its own VTEP information.
  • the first network device receives third GRASP information that is sent by the second network device, the third GRASP information includes second VTEP information, the second The VTEP information includes a second VTEP address and a second VNI, the second VTEP address being bound to the second VNI; and when the first network device determines that the first VNI is the same as the second VNI, The first network device establishes a VXLAN tunnel from the first network device to the second network device according to the first VTEP information and the second VTEP information.
  • the first network device may receive the GRASP information that is sent by the second network device and carry the VTEP information of the second network device, and automatically create the VTEP information of the second network device and the VTEP information of the second network device in the GRASP information.
  • each of the plurality of VTEP device information further includes a VTEP access side port identifier, the VTEP access side port identifier and the VTEP device The identifier corresponds. Determining, by the first network device, the Layer 2 sub-interface of the first network device and the first BD corresponding to the Layer 2 sub-interface according to the first VTEP access-side port identifier included in the first VTEP device information, The first VTEP access side port identifier is associated with the first VTEP device identifier, the second layer sub-interface is used to connect to the virtual machine VM, and the first VNI is used to indicate that the VM belongs to the first BD .
  • the first network device may automatically determine the Layer 2 sub-interface of the first network device and the BD corresponding to the Layer 2 sub-interface according to the access-side port information included in the configuration information. Therefore, after the VXLAN tunnel is established between the first network device and the other network devices, the second layer sub-interface of the second layer interface and the BD corresponding to the VM connected to the second layer sub-interface are determined, so that the virtual local network (VLAN) of the VM is facilitated. The information is converted to the information identified by the VNI and sent out through the VXLAN tunnel.
  • VLAN virtual local network
  • the first VTEP device information further includes a first loopback address, where the first loopback address corresponds to the first VTEP device identifier, where A network device generates first VTEP information according to the first VTEP device information, and the first network device determines the first loopback address as the first VTEP address.
  • the first network device may use the lookback address included in the configuration information as its own VTEP address. Thereby, the VXLAN configuration efficiency is improved.
  • a VXLAN configuration method receives the first GRASP information sent by the first network device, where the first GRASP information includes Objective information, where the Objective information is used to carry configuration information, where the configuration information includes multiple virtual extended LAN tunnel endpoint VTEP devices.
  • each of the plurality of VTEP device information includes a VTEP device identifier and a VXLAN network identifier VNI, wherein the VTEP device identifier corresponds to the VNI; when the second network device determines the When the device identifier of the second network device is the same as the second VTEP device identifier included in the second VTEP device information, the second network device determines that the second network device is the second VTEP, and the second VTEP device information is used.
  • the second network device Instructing the second VTEP; the second network device generates second VTEP information according to the second VTEP device information, wherein the second VTEP device information further includes a second corresponding to the second VTEP device identifier VNI, the second VTEP information includes a second VTEP address and the second VNI, the second VTEP address is bound to the second VNI; the second network device GRASP three network device of the second transmission information, the second information comprises GRASP VTEP the second information, the second information GRASP third network device for triggering the establishment of a tunnel according to the second VXLAN GRASP information.
  • the second network device may receive the GRASP information that is sent by the first network device and carries the configuration information, and after determining that it is a VTEP according to the content included in the configuration information, generate VTEP information, and generate the generated VTEP.
  • the information is carried in the GRASP information and sent to the third network device, so that the third network device automatically creates the VXLAN from the third network device to the second network device according to the VTEP information of the second network device and the VTEP information of the third network device itself. tunnel.
  • the second network device receives the third GRASP information that is sent by the third network device, where the third GRASP information includes the first VTEP information, where the first The VTEP information includes a first VTEP address and a first VNI, the first VTEP address being bound to the first VNI; and when the second network device determines that the first VNI is the same as the second VNI, The second network device establishes a VXLAN tunnel from the second network device to the third network device according to the first VTEP information and the second VTEP information.
  • the second network device may receive the GRASP information that is sent by the peer end (the third network device) and carries the VTEP information of the third network device, according to the VTEP information of the third network device and the second network in the GRASP information.
  • the VTEP information of the device automatically creates a VXLAN tunnel from the second network device to the third network device.
  • the third network device is the first network device.
  • the first network device has the function of acquiring configuration information and transmitting configuration information to other network devices, and has the function of creating a VXLAN tunnel as a VTEP.
  • the second network device forwards the first GRASP information to the third network device, where the first GRASP information is used to trigger the third network device Establishing a VXLAN tunnel according to the first GRASP information.
  • the second network device can serve as a relay node to forward configuration information to other network devices.
  • each of the plurality of VTEP device information further includes a VTEP access side port identifier, the VTEP access side port identifier and the VTEP device The identifier corresponds. Determining, by the second network device, the Layer 2 sub-interface of the second network device and the first BD corresponding to the Layer 2 sub-interface according to the second VTEP access-side port identifier included in the second VTEP device information, The second VTEP access side port identifier is associated with the second VTEP device identifier, the second layer sub-interface is used to connect to the virtual machine VM, and the second VNI is used to indicate that the VM belongs to the first BD .
  • the second network device may automatically determine the Layer 2 sub-interface of the second network device and the BD corresponding to the Layer 2 sub-interface according to the access-side port information included in the configuration information. Therefore, after the VXLAN tunnel is established between the second network device and the other network device, the second layer sub-interface of the second layer interface and the BD corresponding to the VM connected to the second layer sub-interface are determined, so that the VLAN information of the VM is converted into the information identified by the VNI. And send this information out through the VXLAN tunnel.
  • the second network device after the second network device determines that the second network device is the second VTEP, the second network device generates a second loopback loopback address, where the The second lookback address includes an identifier of the second network device, a reserved bit, and a fixed value; and the second network device determines the second loopback address as the second VTEP address.
  • the first network device may automatically generate a lookback address, and use the automatically generated lookback address as its own VTEP address.
  • a first network device having a function of implementing the behavior of the first network device in the implementation of the first aspect or the first aspect.
  • the functions may be implemented based on hardware, or may be implemented based on hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above. No restrictions.
  • the first network device includes a processor and an interface configured to support the first network device to perform a corresponding function in the above method.
  • the interface is configured to support communication between the first network device and the second network device, send information or instructions involved in the foregoing method to the second network device, or receive information involved in the foregoing method from the second network device. Or instructions.
  • the first network device can also include a memory for coupling with a processor that retains program instructions and data necessary for the first network device.
  • the first network device includes: a processor, a receiver, a transmitter, a random access memory, a read only memory, and a bus.
  • the processor is coupled to the receiver, the transmitter, the random access memory, and the read only memory through a bus.
  • the first network device is booted into a normal running state by booting in a basic input/output system in a read-only memory or a bootloader booting system in an embedded system.
  • the application and operating system are run in a random access memory such that the processor performs the method of the first aspect or any possible implementation of the first aspect.
  • a first network device in a fourth aspect, includes: a main control board and an interface board, and further, a switching network board.
  • the first network device is operative to perform the method of the first aspect or any possible implementation of the first aspect.
  • the first network device comprises means for performing the method of the first aspect or any possible implementation of the first aspect.
  • a first network device comprising a controller and a first forwarding sub-device.
  • the first forwarding sub-device includes: an interface board, and further, may further include a switching network board.
  • the first forwarding sub-device is configured to perform the function of the interface board in the fourth aspect. Further, the function of the switching network board in the fourth aspect may also be performed.
  • the controller includes a receiver, a processor, a transmitter, a random access memory, a read only memory, and a bus.
  • the processor is coupled to the receiver, the transmitter, the random access memory, and the read only memory through a bus.
  • the booting is started by the solid input/output system in the read-only memory or the bootloader booting system in the embedded system, and the controller is put into a normal running state. After the controller enters a normal operating state, the application and the operating system are run in the random access memory, so that the processor performs the functions of the main control board in the fourth aspect.
  • a computer storage medium for storing a program, code or instruction for use in the first network device, and the processor or the hardware device can perform the first of the above aspects when executing the program, code or instruction.
  • the function or step of a network device is provided for storing a program, code or instruction for use in the first network device, and the processor or the hardware device can perform the first of the above aspects when executing the program, code or instruction.
  • a second network device having a function of implementing the behavior of the second network device in any of the implementations of the second aspect or the second aspect.
  • the functions may be implemented based on hardware, or may be implemented based on hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above. No restrictions.
  • the second network device includes a processor and an interface configured to support the second network device to perform a corresponding function in the above method.
  • the interface is configured to support communication between the second network device and the first network device, or the second network device and the third network device, and send the information involved in the foregoing method to the second network device or the third network device, or Instructing, or receiving information or instructions involved in the above method from the second network device or the third network device.
  • the second network device can also include a memory for coupling with the processor that retains program instructions and data necessary for the second network device.
  • the second network device includes: a processor, a receiver, a transmitter, a random access memory, a read only memory, and a bus.
  • the processor is coupled to the receiver, the transmitter, the random access memory, and the read only memory through a bus.
  • the booting is performed by the bootloader booting system in the basic input/output system or the embedded system in the read-only memory, and the second network device is booted into a normal running state.
  • the application and operating system are run in a random access memory such that the processor performs the method of any of the second or second aspects of the possible implementation.
  • a second network device in an eighth aspect, includes: a main control board and an interface board, and further, a switching network board.
  • the second network device is operative to perform the method of the second aspect or any possible implementation of the second aspect.
  • the second network device comprises means for performing the method of any of the second aspect or any of the possible implementations of the second aspect.
  • a second network device comprising a controller and a first forwarding sub-device.
  • the first forwarding sub-device includes: an interface board, and further, may further include a switching network board.
  • the first forwarding sub-device is configured to perform the function of the interface board in the eighth aspect. Further, the function of the switching network board in the eighth aspect may also be performed.
  • the controller includes a receiver, a processor, a transmitter, a random access memory, a read only memory, and a bus.
  • the processor is coupled to the receiver, the transmitter, the random access memory, and the read only memory through a bus.
  • the booting is started by the solid input/output system in the read-only memory or the bootloader booting system in the embedded system, and the controller is put into a normal running state. After the controller enters the normal operating state, the application and the operating system are run in the random access memory, so that the processor performs the functions of the main control board in the eighth aspect.
  • a computer storage medium for storing a program, code or instruction used by the second network device, and the processor or the hardware device can perform the second of the above aspects when executing the program, code or instruction.
  • the function or step of a network device is provided for storing a program, code or instruction used by the second network device, and the processor or the hardware device can perform the second of the above aspects when executing the program, code or instruction.
  • a VXLAN configuration system is provided, where the configuration system of the VXLAN includes a first network device and a second network device, where the first network device is the foregoing third aspect or the fourth aspect or the fifth aspect or The first network device in the sixth aspect, wherein the second network device is the foregoing seventh or eighth aspect or the second network device in the ninth or tenth aspect.
  • the VXLAN configuration method, device, and system provided by the embodiment of the present application, after the first network device obtains configuration information for indicating multiple VTEPs included in the VXLAN, the configuration information is carried in the GRASP.
  • the information is sent to the second network device, the second network device determines that it is a VTEP according to the content included in the configuration information, the second network device generates VTEP information, and sends the third network device to the third network device that carries the second network device.
  • the GRASP information of the VTEP information, the third network device creates a VXLAN tunnel according to the VTEP information of the second network device and the VTEP information of the third network device, and the third network device may also send the third network device to the second network device according to the same principle.
  • the VTEP information, the second network device creates a VXLAN tunnel according to the VTEP information of the second network device and the VTEP information of the third network device. Therefore, the VXLAN configuration is completed through information interaction between the network devices, and the automatic configuration of the VXLAN is realized, thereby avoiding the problem that the existing configuration VXLAN is inefficient and the error rate is high.
  • FIG. 1 is a schematic structural diagram of an EVPN-VPWS network according to an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a VXLAN according to an embodiment of the present application.
  • FIG. 3 is a flowchart of a method for configuring a VXLAN according to an embodiment of the present application
  • FIG. 3a is a schematic diagram of a GRASP information format according to an embodiment of the present application.
  • FIG. 3b is a schematic diagram of a lookback address according to an embodiment of the present application.
  • FIG. 3c is a schematic diagram of VTEP information according to an embodiment of the present application.
  • FIG. 3 is a flowchart of a method for sending first GRASP information according to an embodiment of the present application
  • FIG. 4 is a flowchart of still another method for configuring a VXLAN according to an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of a first network device according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of hardware of a first network device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of hardware of another first network device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of hardware of still another first network device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a second network device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of hardware of a second network device according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of hardware of another second network device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of hardware of still another second network device according to an embodiment of the present application.
  • the VXLAN configuration method provided by the present application can be used to configure a Layer 3 routing network as a VXLAN, and can also be used to configure a Layer 2 switching network or other data center network as a VXLAN, which is not limited.
  • the configuration of the VXLAN provided by the present application is described in detail below by taking the network shown in FIG. 1 as a VXLAN as an example.
  • the process of configuring other VXLANs in the network can refer to the solution provided in this application.
  • the network may include: a core layer device, a first network device, a second network device, a third network device, and a host.
  • the core layer device is a high-speed switching backbone of the network, and can process all traffic from the network device.
  • the core network device can be a device such as a router supporting Layer 2 switching technology; the first network device, the second network device, and the third device.
  • a network device can be a provider edge (PE) device (such as a router or a switch). It is used to connect hosts and other sites to the network. It is responsible for some user management functions (such as address authentication, user authentication, and accounting management).
  • PE provider edge
  • the host can be a customer edge (CE) device (such as a router or a switch), connected to a network device, accessing the network through a network device, each virtual machine can create multiple virtual machines (VMs), and the VM can send data packets through network devices and core layer devices. Give other devices such as the target VM or host.
  • CE customer edge
  • the network shown in FIG. 1 may be configured as the VXLAN shown in FIG. 2 by using the VXLAN configuration method provided by the present application, for example, the host connected to the host is configured.
  • Each network device acts as a VTEP.
  • a VXLAN tunnel can be established between different VTEPs.
  • VMs belonging to the same VXLAN can communicate with each other through VXLAN tunnels.
  • FIG. 3 is a flowchart of a method for configuring a VXLAN according to an embodiment of the present application.
  • the method shown in Figure 3 can be used to configure the network shown in Figure 1 into a VXLAN.
  • the network shown in FIG. 1 may include a first network device, a second network device, and a third network.
  • the method shown in FIG. 3 includes S101 to S107,
  • S101 The first network device acquires configuration information.
  • the first network device may be a PE located in a core network, and the PE may be a router or a switch.
  • a PE device may be referred to as an NVE device, or an NVE device is integrated in a PE, or an NVE device communicates as a standalone device with a PE device.
  • a VTEP entity or a VTEP device (VTEP) can be integrated in the NVE device, and is not limited.
  • the first network device runs the ANIMA protocol and has an autonomous function to minimize the dependence on the network administrator or the centralized management system.
  • the configuration information may be determined according to the VXLAN networking requirements of the user.
  • the configuration information specifies which devices in the VXLAN are VTEP and related information of the VTEP.
  • the configuration information may include multiple VTEP device information, and the multiple VTEP device information may be used to indicate multiple VTEPs included in the VXLAN, respectively.
  • Each VTEP device information may include, but is not limited to, a VTEP device identification and a VNI, where the VTEP device identification corresponds to a VNI.
  • the VNI is used to distinguish the virtual network instance.
  • the virtual local area network instance may be a Layer 2 virtual network instance or a Layer 3 virtual network instance. Different virtual network instances correspond to different VNIs. Different virtual network instances are isolated. Communication between two VMs in the same VNI does not require a VXLAN Layer 3 gateway. Two VMs located in different VNIs need to communicate via a VXLAN Layer 3 gateway.
  • the VNI field contains 24 bits. An administrative domain can contain up to 2 16 VXLAN segments.
  • the VTEP device identifier is used to uniquely identify the device as a VTEP.
  • the VTEP device identifier may be a serial number (SN) of the VTEP or a MAC address of the VTEP, which is not limited.
  • the device identifier of device 1 is 001
  • the device identifier of device 2 is 002
  • the device identifier of device 3 is
  • the VTEP device in the VXLAN is the device 1, the device 2, and the device 3, and the configuration information obtained by the first network device is as shown in Table 1.
  • the VNI corresponding to the VTEP device identifier 001 is VNI101, vni102, VNI corresponding to VTEP device identifier 002 is vni101, VNI corresponding to VTEP device identifier 003 is vni102, so when device 1, device 2, device 3 obtains the configuration information, it may include itself according to the configuration information.
  • the device identifies the same VTEP device identifier, determines itself as VTEP, and establishes a VXLAN tunnel with the peer.
  • the VNI corresponding to the peer is the same as the corresponding VNI.
  • the configuration information includes the VTEP device identifier 001 that is the same as the device identifier of the device 1, and determines that it is VTEP, and according to the table 1, it can be known that it corresponds to vni101.
  • Vni102 a VXLAN tunnel can be established with the device 2 corresponding to the vni101, and a VXLAN tunnel is established with the device 3 corresponding to the vni102.
  • the first network device includes a command line interface (CLI) module, where the CLI module is used for interaction between the user and the first network device, and the CLI module can be implemented in a hardware manner. It can also be implemented in the manner that the processor executes software instructions.
  • the first network device obtains configuration information input by the user through the CLI module. For example, the user may decompose the configuration information into multiple pieces of information, and the first network device acquires information input by the user one by one through the CLI module.
  • CLI command line interface
  • the configuration information is stored in the form of a file (such as an extensible markup language (XML) file, or a JavaScript object notation (json) file) in network management.
  • the first network device includes a configurator (CFG) module, where the CFG component is used to manage and configure a configuration file, and the CFG module may be implemented in a hardware manner or may execute a software instruction by using a processor. The way to achieve.
  • the first network device invokes the CFG module to obtain configuration information from the network management server.
  • the manner in which the foregoing first network device obtains the configuration information through the CLI module or the CFG module can be referred to FIG. 3d, and details are not described herein again.
  • the configuration information is stored in a file transfer protocol (ftp) server in the form of a file (such as an XML file or a json file, etc.), and the first network device obtains the ftp server from the ftp server through ftp.
  • Configuration information For example, the first network device supports the ftp protocol, and the first network device sends a reload command to the ftp server, and the ftp server sends configuration information to the first network device according to the load command, and the first network device receives the configuration information.
  • the above VXLANIntent represents a VXLAN file.
  • vxlanConfig represents the VXLAN configuration section.
  • the outervlan name indicates the vlan to be configured on the port to which the user is connected.
  • the outerVlan value indicates which vlan the vlan needs to be configured on the port to which the user is connected.
  • the snNum name indicates the device that is the VTEP in the VXLAN
  • VNI Range List represents a list of ranges for the VNI.
  • VNI start and VNI End describe the scope of vni.
  • Mapping VLAN Start and Mapping VLAN End describe the range of vlan bound to vni.
  • GateWay IP Start and GateWay IP End describe the range of gateway address, described by Mask Length. It is the mask of the gateway.
  • the service list is a service list, which describes the service types of different VLANs and the deployment mode of vxlan.
  • Service Name “user1,” indicates the service of the user 1
  • Service Specificator type VLAN
  • identity of the service type is VLAN
  • Service Specificator value 1024 indicates that the vlan corresponding to the service is vlan1024, and VXLAN Mode: 1 (Centralized) indicates The service deployment mode is 1 (central deployment).
  • the first network device generates first GRASP information according to the configuration information.
  • the first GRASP information may include the Objective information, where the Objective information is used to carry the configuration information acquired by the first network device.
  • the Objective information may include an objective name (objective-name) and an objective value (objective-value).
  • the objective-name is used to identify an Objective to indicate the role of the Objective. Refers to the configuration parameters included in Objective.
  • the objective-name included in the first GRASP information may be VXLAN_configuration_information (VXLAN configuration information), to indicate that the Objective is used for VXLAN configuration, and the objective-value may be obtained by the first network device.
  • the configuration information includes the VTEP device information, and each VTEP device information includes a VTEP device identifier and a corresponding VNI.
  • the VTEP device information in the objective-value may be expressed in the form of Table 1 or otherwise, and is not limited.
  • the configuration information includes VTEP_1 device information indicating VTEP_1 included in the VXLAN and VTEP_2 device information of VTEP_2.
  • the VTEP_1 device information includes the VTEP_1 device identifier 001 with its corresponding vni101
  • the VTEP_2 device information includes the VTEP_2 device identifier 002 with its corresponding vni101
  • the objective-value includes The content is "VTEP_1 device identifier, VTEP_1 device identifier value, VTEP_1 vni identifier, VTEP_1 vni identifier value", "VTEP_2 device identifier, VTEP_2 device identifier value, VTEP_2 vni identifier, VTEP_2 vni identifier value".
  • the VTEP_1 device identifier corresponds to the vni identifier of VTEP_1, and the VTEP_2 device identifier corresponds to the vni identifier of VTEP_2.
  • the device identifier, snNum-value indicates the specific value of the device identifier, vniNum name indicates the VNI corresponding to a device, and vniNum value indicates the specific value of the VNI corresponding to the device
  • the Objective information includes, in addition to the objective-name and the objective-value, as shown in FIG. 3a, the Objective information may further include one or more of a loop-count, an objective-flag, and the like. .
  • the loop-count field is used to indicate the hop count of the first GRASP information forwarding.
  • the loop-count field ranges from 0 to 255.
  • the loop-count field ensures a range in which the first GRASP information is transmitted. For example, when the value is 1, the first GRASP information may be propagated to the second network device, and when the value is 2, the first GRASP is Information can be propagated to the third network device.
  • the objective-flag is used to indicate a discovery session, a negotiation session, a synchronization session, or a dry-run negotiation.
  • the first network device includes a GRASP component, and the first network device obtains the Objective information from the configuration information by using the GRASP component, and encapsulates the obtained Objective information and the GRASP packet header to form the first GRASP. information.
  • the process of S102 can be referred to FIG. 3d, and details are not described herein again.
  • the GRASP packet header may include one of a message type (message_type), a session identifier (session-id), an initiator (initiator), and a time-to-live (TTL). Or multiple.
  • messages_type a message type
  • session-id session identifier
  • initiator initiator
  • TTL time-to-live
  • each field shown in FIG. 3a occupies different bits, and the corresponding bit of each field may be fixed (eg, the message_type is located in the first field of the GRASP information), and may also be changed according to actual needs, such as: TTL In the past, the initiator is in the back, or the initiator is in the front, and the TTL is in the back, no limit.
  • the message_type is used to indicate the type of the first GRASP information, and specifically indicates the Objective information used in the mechanism (the discovery mechanism or the synchronization mechanism or the negotiation mechanism or the flooding mechanism) of the Objective information carried by the first GRSAP information. For example, if the message_type is divided into: M_DISCOVERY, it means the Objective information used in the discovery mechanism.
  • Session-id refers to the identity of the GRASP session.
  • the initiator refers to the initiator of the GRASP information referred to in this application, such as the first network device in this application.
  • the TTL is used to indicate the lifetime of the Objective information carried by the first GRASP information in the network device.
  • the length of the TTL is 32 bits, and the value ranges from 0 ms to 4294967295 ms, and ms represents milliseconds.
  • the first network device sends the first GRASP information to the second network device.
  • the second network device may also be a PE located in the core network, and the PE may be a router or a switch; or may be an NVE device integrated in a VXLAN router or independently existed in the VXLAN; or may be integrated in the The VTEP in the NVE device is not limited.
  • the second network device may be regarded as a single network device, or may be regarded as multiple network devices.
  • the first network device sending the first GRASP information to the second network device may refer to: the first network device simultaneously sending the first GRASP to the plurality of network devices.
  • the first network device runs the ANIMA function, configures the anima domain, and floods the first GRASP information to all the network devices in the anima domain through the grasp protocol, where the anima domain includes the second network device, and Contains other network devices, such as: third network device, fourth network device, and so on.
  • the process of S103 can be referred to FIG. 3d, and details are not described herein again.
  • the second network device receives the first GRASP information sent by the first network device.
  • the second network device may decapsulate the first GRASP information, obtain configuration information included in the first GRASP information, and view the VTEP device identifier included in each VTEP device information, and associate it with the If the device ID is the same, the device ID is determined to be a VTEP. You can establish a VXLAN tunnel with the peer VTEP.
  • the device identifier of the second network device is 002 and the VTEP device identifier of VTEP_2 in the configuration information is 002, it is determined that the second network device is VTEP_2. It can be understood that when the VTEP device identifier of the device identifier of the second network device is not included in the configuration information, it means that the second network device cannot be used as the VTEP, and the following steps S106-S107 are not performed.
  • the second network device generates second VTEP information according to the second VTEP device information, where the second VTEP device information further includes a second VNI corresponding to the second VTEP device identifier, where the second VTEP information includes the second VTEP address and the first The second VNI, the second VTEP address is bound to the second VNI.
  • the generating, by the second network device, the second VTEP information according to the second VTEP device information may include:
  • the second network device After determining that the VTEP is itself, the second network device determines the second VTEP address, and combines the second VTEP address and the second VNI as the second VTEP information.
  • the second VTEP address may be a network address that can be routed to the second VTEP, and the address of the second VTEP may be a lookback address of the second VTEP, and may also be an IP address of the physical interface of the second VTEP, and the like, and is not limited.
  • the second VTEP device information further includes a second lookback address, where the second lookback address corresponds to the second VTEP device identifier, and when the second network device determines that it is the second VTEP, the second network device The second lookback address is determined to be the second VTEP address.
  • the second network device when the second network device determines that it is the second VTEP, the second network device generates a second lookback address according to the generation rule of the lookback address, and determines the generated second lookback address as the second. VTEP address.
  • the second lookback address includes an identifier of the second network device, a reserved bit, and a fixed value. Specifically, as shown in FIG.
  • the second lookback address includes 32 bits, wherein the 0th bit (including the 0th bit) to the 16th bit (including the 16th bit) fill the identifier of the second network device, and the 16th bit Bits (excluding the 16th bit) to 24th bit (including the 24th bit) are reserved bits, all padded with the number 0, the 24th bit (excluding the 24th bit) to the 31st bit (including the 31st bit)
  • the fixed value is filled. Normally, the fixed value can be 152 as shown in Figure 3b.
  • the second VTEP device information further includes a value range and a rule of the IP address of the physical interface of the second VTEP, and the physical interface of the second VTEP corresponds to the second VTEP device identifier, and the second VTEP
  • the value range and rules of the IP address of the physical interface can be used to specify the IP address of the physical interface of the second VTEP and the address range corresponding to the IP address of the configured physical interface.
  • the value range and the rule of the IP address of the physical interface of the second VTEP of the second network device determine the IP address of the physical interface of the second VTEP, and the physical interface of the second VTEP The IP address is determined to be the second VTEP address.
  • the second network device when the second network device determines that it is the second VTEP, the second network device configures an ipv6 local auto-link on the physical interface, and the physical interface is configured according to the Internet.
  • the method described in the Internet Engineering Task Force (IETF) Request For Comments (RFC) 7217 generates a random ipv6 address and determines the generated ipv6 address as the second VTEP address.
  • the RFC7217 can refer to the prior art, and details are not described herein again.
  • the second network device sends the second GRASP information to the third network device, where the second GRASP information includes the second VTEP information, where the second GRASP information is used to trigger the third network device to establish a VXLAN tunnel according to the second GRASP information.
  • the third network device may be the first network device, and may be other network devices than the first network device and the second network device, and is not limited.
  • the third network device is the first network device
  • the first network device is a member of the VTEP
  • the first network device can perform not only the configuration information acquired by the S101 but also the second network according to the second GRASP information. Create a VXLAN tunnel between devices.
  • the second network device may carry the second VTEP information in the Objective information, and encapsulate the Objective information and the GRASP packet header to generate the second GRASP information.
  • the Objective information carrying the second VTEP information may include an objective-name and an objective-value, where the objective-name may be used to identify the Objective, the Objective may be the second VTEP information described in the application, and the Objective-name may be the first
  • the objective-value may include the configuration parameter of the Objective.
  • the second VTEP address in the second VTEP information and the VNI to which it is bound may be included in the application.
  • the Objective information carrying the second VTEP information may include a loop-count, an objective-flag, and the like in addition to the second VTEP information.
  • the GRASP header in the second GRASP information may include a message_type and a session.
  • the description of each field included in the second GRASP information may be referred to the related description of the field included in the foregoing first GRASP information, and details are not described herein again.
  • the address of the second network device is loopback address 1.1.1.1
  • the VNI bound to the address is vni101
  • the VTEP_2 information sent by the second network device is HW_VTEP_2
  • the objective-flag is F_SYNC.
  • the loop-count is 6, and the second GRASP information generated by the second network device is as shown in FIG. 3c.
  • FIG. 3c is only an example in which the address of the second network device is bound to a VNI. In an actual application, the address of the second network device may be bound to multiple VNIs, which is not limited.
  • the process of the second network device sending the second GRASP information to the third network device may refer to the related description in S103.
  • the second network device may also send the second GRASP information to the third network device by using the flooding mode. Let me repeat.
  • the first network device may obtain configuration information for indicating multiple VTEPs included in the VXLAN, and carry the configuration information in the first GRASP information and send the information to the second network device, where the second network device
  • the second VTEP information may be determined according to the configuration information included in the first GRASP information, and the second VTEP information is generated according to the second VTEP device information, and the second VTEP information is carried in the second GRASP information and sent to the third network device. So that the third network device creates a VXLAN tunnel according to the second GRASP information. Therefore, the VXLAN configuration is completed through information interaction between the network devices, and the automatic configuration of the VXLAN is realized, thereby avoiding the problem that the existing configuration VXLAN is inefficient and the error rate is high.
  • the third network device is the first network device
  • the first network device determines that it is the first VTEP
  • the first network device establishes the VXLAN tunnel according to the second GRASP information, including:
  • the first network device determines that the first VNI is the same as the second VNI
  • the first network device establishes a VXLAN tunnel from the first network device to the second network device according to the first VTEP information and the second VTEP information, where the first VTEP device information includes The first VNI, the first VNI corresponds to the first VTEP device identifier, and the first VTEP device information is used to indicate the first VTEP.
  • the process of determining, by the first network device, that the first VTEP is the same as the device ID of the first VTEP device in the configuration information is determined to be the first VTEP.
  • the first VTEP information may include a first VNI and a first VTEP address, the first VTEP address being bound to the first VNI.
  • the determination manner of the first VTEP address refer to the foregoing determining manner of the second VTEP address, and details are not described herein again.
  • the establishing, by the first network device, the VXLAN tunnel from the first network device to the second network device according to the first VTEP information and the second VTEP information includes:
  • the first network device creates a peer list corresponding to the first VNI, and the peer list corresponding to the first VNI may include the first network device address.
  • the second VTEP information includes information such as the second VTEP address 1.1.1.1, and vni101.
  • the first network device receives the second VTEP information, it finds that the second VTEP information includes the same vni101 as its own VNI, and then creates The peer list corresponding to vni101, the peer list contains the second VTEP address 1.1.1.1.
  • the creation process is as follows:
  • the source VTEP is the first network device. Therefore, the local VTEP (the first network device) can know that the remote VTEP belonging to the vni101 is 1.1.1.1. When the local VTEP receives the packet from the vni101, it passes the VXLAN. The tunnel sends the packet to the peer VTEP1.1.1.1.
  • the first network device Since the VXLAN tunnels are created by each other, in order to implement the VXLAN tunnel from the second network device to the third network device by the second network device, after the first network device determines that it is the first VTEP, the first network device generates the first a VTEP information, and transmitting, to the second network device, third GRASP information carrying the first VTEP information; the second network device receiving the third GRASP information sent by the first network device, when the second network device determines the second VNI and the first The VNI is the same, the second network device establishes a VXLAN tunnel from the second network device to the third network device according to the second VTEP information and the first VTEP information;
  • the process of establishing, by the second network device, the VXLAN tunnel from the second network device to the first network device according to the second VTEP information and the first VTEP information may be created by referring to the first network device according to the first VTEP information and the second VTEP information.
  • the process of the VXLAN tunnel from the first network device to the second network device is not described here.
  • the second VTEP information includes the second VTEP address 1.1.1.1, and the vni101 information.
  • the first VTEP information includes the first VTEP address 2.2.2.2, and the information such as vni101.
  • the source VTEP is the second network device. Therefore, the local VTEP (the second network device) can know that the remote VTEP belonging to the vni101 is 2.2.2.2. When the local VTEP receives the packet from the vni101, it passes the VXLAN. The tunnel sends the packet to the peer VTEP2.2.2.2.
  • the third network device may directly obtain configuration information through S101; if the third network device is the first network device and the second network device, The other network device, the third network device may receive the first GRASP information carried by the first network device and carry the configuration information, or the second network device serves as the relay node, the second network.
  • the device forwards the first GRASP information to the third network device, that is, the third network device receives the first GRASP information forwarded by the second network device, and is not limited.
  • the VTEP device information further includes a VTEP access side port identifier, and the VTEP access side port identifier corresponds to the VTEP device identifier.
  • the scheme shown in Figure 3 also includes:
  • the layer 2 sub-interface of the first network device and the first BD corresponding to the layer 2 sub-interface according to the first VTEP access-side port identifier included in the first VTEP device information, where the first The VTEP access side port identifier corresponds to the first VTEP device identifier, the layer 2 sub-interface is used to connect to the VM, and the first VNI is used to indicate that the VM belongs to the first BD.
  • the first network device can determine its own Layer 2 sub-interface and the BD corresponding to the VM connected to the Layer 2 sub-interface, so as to convert the VLAN information of the VM into the VNI identifier. Information and send it out through the VXLAN tunnel.
  • the VTEP access side port identifier is used to identify the VTEP access side port, and the VTEP access side port identifier may be the VTEP access side port index number, for example, the index side 1 to n may be used for the VTEP access side port. If the number is greater than or equal to 2, the VTEP access-side port identifier may be the physical address of the access-side port of the VTEP, such as an Ethernet address, and is not limited.
  • the access-side port of the first network device is 10GE1/0/1
  • the VNI of the first network device is vni4000 and vni5000.
  • a Layer 2 sub-interface 10GE1/0 is created. /1.1 and 10GE1/0/1.2, and the Layer 2 sub-interface 10GE1/0/1.1 is added to the BD broadcast domain 10, and the vni4000 is configured for the BD broadcast domain 10, and the Layer 2 sub-interface 10GE1/0/1.2 is added to the BD broadcast domain 20.
  • configure the vni5000 for the BD broadcast domain 20 is as follows:
  • Bridge-domain 10// indicates that a "Large Layer 2 Broadcast Domain" BD is created, which is numbered 10
  • Vxlan vni 4000// indicates that under BD broadcast domain 10, the VNI associated with it is specified as vni4000
  • Bridge-domain 10// indicates that a "Large Layer 2 Broadcast Domain" BD is created, which is numbered 20
  • Vxlan vni 5000// indicates that under the BD broadcast domain 20, the VNI associated with it is specified as vni5000.
  • the configuration information acquired by the first network device further includes a routing protocol used by the network, and the routing protocol includes an open shortest path first (ospf) and an intermediate system to an intermediate system (intermediate system to Intermediate system, isis) and other protocols.
  • This routing protocol is used to allow users to select which routing protocol to use when advertising routes between devices. It is ospf protocol or other routing protocols such as isis.
  • the first network device can include an ANIMA control module and a GRASP module.
  • the ANIMA control module is used to manage and schedule other modules in the first network device.
  • the GRASP module is used to implement the GRASP function.
  • the GRASP module is further configured to generate and send the first GRASP information.
  • the first network device may also include a CFG module and/or a CLI module.
  • the CFG module is used to manage and configure the configuration file.
  • the CLI module is used for interaction between the user and the first network device.
  • the ANIMA control module, the GRASP module, the CFG module, and the CLI module may be implemented in a hardware manner or may be implemented by a processor executing software instructions.
  • the method shown in Figure 3d includes S1101 through S1105.
  • the S1101, the CLI module, or the CFG module obtains configuration information.
  • the first network device can obtain configuration information through a CLI module or a CFG module.
  • the user enters configuration information through the CLI module.
  • the ANIMA control module invokes the CFG module to configure the configuration information. In this way, the CFG module can obtain configuration information.
  • the S1102, CLI module or CFG module sends configuration information to the ANIMA control module.
  • the CLI module or the CFG module may directly send configuration information to the ANIMA control module, or carry the configuration information in the first message, and send the first message to the ANIMA control module.
  • the format of the first message may use a messaging format internal to the network device, such as a socket message.
  • the S1103 and ANIMA control modules forward configuration information to the GRASP module.
  • the ANIMA control module can forward the received configuration information to the GRASP module or forward the received first message to the GRASP module.
  • the S1104 and the GRASP module generate the first GRASP information according to the configuration information.
  • the GRASP module may encapsulate the configuration information in the first GRASP information in the format shown in FIG. 3a.
  • the S1105 and the GRASP module send the first GRASP information.
  • the ANIMA control module is configured to manage and schedule other modules in the first network device, and after receiving the configuration information, the ANIMA control module sends the configuration information to the GRASP module. After receiving the configuration information, the GRASP module can generate the first GRASP information by using the configuration information. The GRASP module then sends the first GRASP information to the second network device.
  • the specific implementation of the first GRASP information packet can be seen in Figure 3a.
  • S1101 to S1105 illustrate an implementation manner in which the CLI module or the CFG module actively reports configuration information to the GRASP module through the ANIMA control module.
  • the GRASP module can actively request the ANIMA control module to query the ANIMA control module configuration information.
  • the ANIMA control module calls the CLI module or the CFG module for reporting. For the process of reporting the CLI module or the CFG module, refer to the descriptions of S1101 to S1105 above, and details are not described herein.
  • the VXLAN tunnel is established between VTEP_1 and VTEP_2 as an example.
  • FIG. 4 is a flowchart of still another VXLAN configuration method according to an embodiment of the present application. As shown in FIG. 4, the method includes:
  • the network device 1 acquires configuration information, where the configuration information includes VTEP_1 device information and VTEP_2 device information, the VTEP_1 device information is used to indicate VTEP_1 in the VXLAN, the VTEP_1 device information includes the VTEP_1 device identifier 001, and the VTEP_1 device identifier 001 corresponds to The vni101, VTEP_2 device information is used to indicate VTEP_2 in the VXLAN, the VTEP_2 device information includes the VTEP_2 device identifier 002, and the vni101 corresponding to the VTEP_2 device identifier 002.
  • the network device 1 generates the GRASP information 1 according to the configuration information, and transmits the GRASP information 1 to the network device 2.
  • the GRASP information 1 includes the GRASP packet header, the VTEP_1 device identifier 001, the vni101 corresponding to the VTEP_1 device identifier 001, the VTEP_2 device identifier 002, and the vni101 corresponding to the VTEP_2 device identifier 002.
  • the process of generating the GRASP information 1 and the GRASP1 by the network device 1 may refer to the process of generating the first GRASP information and the first GRASP information by using the foregoing first network device, and details are not described herein again.
  • the network device 2 receives the GRASP information 1, and searches for the VTEP device information included in the configuration information in the GRASP information 1. When it is determined that the VTEP_2 device identifier 002 is the same as the device identifier of the device, the network device 2 determines that it is VTEP_2 and corresponds to vni101.
  • the network device 1 searches for the VTEP device information included in the configuration information. When it is determined that the device identifier 001 of the VTEP_1 is the same as the device identifier of the VTEP_1, the network device 1 determines that it is VTEP_1 and corresponds to vni101.
  • the network device 1 determines the VTEP_1 address, and carries its own vni101 and VTEP_1 addresses in the VTEP_1 information.
  • the network device 1 generates GRASP information 2 based on the VTEP_1 information, and transmits the GRASP information 2 to the network device 2.
  • the process of determining the VTEP_1 address by the network device 1 may refer to the process of determining the first VTEP address by using the foregoing first network device, and details are not described herein again.
  • the network device 1 generates the GRASP information 2 according to the VTEP_1 information.
  • the network device 1 may carry the VTEP_1 information in the Objective information, and encapsulate the Objective information and the GRASP packet header to generate the GRASP information 2.
  • the network device 2 receives the GRASP information 2, determines that the VTEP_1 information in the GRASP information 2 is the same as the vni101 of the vIR101, and creates a peer list of the vni101, where the peer list includes the VTEP_1 address, and thus the network device 2 to the network device 1 is implemented.
  • the network device 2 determines the VTEP_2 address, and carries the vni101 and VTEP_2 addresses in the VTEP_2 information.
  • the network device 2 generates the GRASP information 3 based on the VTEP_2 information, and transmits the GRASP information 3 to the network device 1.
  • the process of determining the VTEP_2 address by the network device 2 may refer to the process of determining the second VTEP address by using the foregoing second network device, and details are not described herein again.
  • the network device 2 generates the GRASP information 2 according to the VTEP_2 information.
  • the network device 2 may carry the VTEP_2 information in the Objective information, and encapsulate the Objective information and the GRASP packet header to generate the GRASP information 2.
  • the network device 1 receives the GRASP information 3.
  • the peer list of the vni101 is created, and the peer list includes the VTEP_2 address, and the network device 1 to the network device 2 is implemented.
  • S405 to S406, and S407 to S408 are simultaneously executed or S405 to S406 are executed before, S407 to S408 are executed later, or S407 to S408 are executed before, and S405 to S406 are executed. Execution afterwards, no restrictions. Further, S402 to S403 may be executed simultaneously with S405, or may be performed between S405 and S406, and are not limited.
  • FIG. 5 is a schematic structural diagram of a first network device 50 according to an embodiment of the present application.
  • the first network device 50 shown in FIG. 5 runs the ANIMA protocol, and the first network device 50 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the first network device 500 includes a receiving unit 501, a processing unit 502, and a sending unit 503.
  • the receiving unit 501 is configured to acquire configuration information, where the configuration information includes multiple VTEP device information, where the multiple VTEP device information is used to indicate multiple VTEPs included in the VXLAN.
  • the processing unit 502 is configured to generate first GRASP information according to the configuration information acquired by the receiving unit 501, where the first GRASP information includes Objective information, where the Objective information is used to carry the configuration information.
  • the sending unit 503 is configured to send the first GRASP information generated by the processing unit 502 to the second network device, where the first GRASP information is used to trigger the second network device to establish a VXLAN according to the first GRASP information. tunnel.
  • each of the plurality of VTEP device information includes a VTEP device identifier and a VXLAN network identifier VNI, wherein the VTEP device identifier corresponds to the VNI.
  • the processing unit 502 determines that the device identifier of the first network device is the same as the first VTEP device identifier included in the first VTEP device information, the processing unit 502 determines that the first network device is the first VTEP, The first VTEP device information is used to indicate the first VTEP; the processing unit 502 is further configured to generate first VTEP information according to the first VTEP device information, where the first VTEP device information further includes The first VTEP device identifier corresponds to the first VNI, the first VTEP information includes a first VTEP address and the first VNI, and the first VTEP address is bound to the first VNI; the sending unit 503 further And the second GRASP information is sent to the second network device, where the second GRASP information includes the first VTEP information.
  • the receiving unit 501 is further configured to receive third GRASP information that is sent by the second network device, where the third GRASP information includes second VTEP information, where the second VTEP information includes a second VTEP address and a second VNI, the second VTEP address being bound to the second VNI; when the processing unit 502 determines that the first VNI is the same as the second VNI, the processing unit 502 is further configured to The first VTEP information and the second VTEP information establish a VXLAN tunnel from the first network device to the second network device.
  • each VTEP device information of the multiple VTEP device information further includes a VTEP access side port identifier, where the VTEP access side port identifier corresponds to the VTEP device identifier
  • the processing unit 502 further uses Determining, according to the first VTEP access side port identifier included in the first VTEP device information, a Layer 2 sub-interface of the first network device and a first BD corresponding to the Layer 2 sub-interface, the first VTEP
  • the access-side port identifier is associated with the first VTEP device identifier
  • the second-layer sub-interface is configured to connect to the virtual machine VM, where the first VNI is used to indicate that the VM belongs to the first BD.
  • the first VTEP device information further includes a first loopback loopback address, the first loopback address is corresponding to the first VTEP device identifier, and the processing unit 502 generates a first according to the first VTEP device information.
  • the VTEP information specifically includes: the processing unit 502 is further configured to determine the first loopback address as the first VTEP address.
  • the first network device shown in FIG. 5 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the automatic configuration of VXLAN is realized, which avoids the problem that the existing VXLAN configuration is inefficient and the configuration error rate is high.
  • FIG. 6 is a schematic structural diagram of hardware of a first network device 60 according to an embodiment of the present application.
  • the first network device 60 shown in FIG. 6 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the first network device 60 includes a processor 601, a memory 602, an interface 603, and a bus 604.
  • the interface 603 can be implemented in a wireless or wired manner, and specifically can be a network card.
  • the above processor 601, memory 602 and interface 603 are connected by a bus 604.
  • the interface 603 may specifically include a transmitter and a receiver, configured to send and receive information between the first network device and the second network device in the foregoing embodiment.
  • the interface 603 is configured to support acquiring configuration information and sending the first GRASP information to the second network device.
  • the interface 603 is used to support the processes S101 and S103 in FIG.
  • the processor 601 is configured to perform processing performed by the first network device in the foregoing embodiment.
  • the processor 601 is configured to generate first GRASP information; and/or other processes for the techniques described herein.
  • the processor 601 is configured to support the process S102 of FIG.
  • the memory 602 includes an operating system 6021 and an application program 6022 for storing programs, codes, or instructions.
  • the memory 602 may include a read-only memory (ROM) and a random access memory (RAM).
  • the ROM includes a basic input/output system (BIOS) or an embedded system;
  • the RAM includes an application and an operating system.
  • BIOS basic input/output system
  • the first network device 60 is booted into a normal operating state by booting the BIOS in the ROM or the bootloader booting system in the embedded system.
  • the application program and the operating system running in the RAM are executed, thereby completing the processing procedure involving the first network device in the method embodiment.
  • FIG. 6 only shows a simplified design of the first network device 60.
  • the first network device can contain any number of interfaces, processors or memories.
  • FIG. 7 is a schematic structural diagram of hardware of another first network device 70 according to an embodiment of the present application.
  • the first network device 70 shown in FIG. 7 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the first network device 70 includes a main control board 701, a switching network board 702, an interface board 703, and an interface board 704.
  • the main control board 701, the interface board 703 and the interface board 704, and the switching network board 702 are connected to each other through the system bus to implement interworking.
  • the main control board 701 is used to complete functions such as system management, device maintenance, and protocol processing.
  • the switching network board 702 is used to complete data exchange between each interface board (also referred to as a line card or a service board).
  • the interface boards 703 and 704 are used to provide various service interfaces (for example, a POS interface, a GE interface, an ATM interface, etc.), and implement forwarding of data packets.
  • the interface board 703 may include a central processing unit 7011, a forwarding entry storage 7034, a physical interface card 7033, and a network processor 7032.
  • the central processing unit 7031 is configured to control and manage the interface board and communicate with the central processing unit on the main control board.
  • the forwarding entry storage 7034 is used to save forwarding entries.
  • the physical interface card 7033 is used to complete the reception and transmission of traffic.
  • the network storage 7032 is configured to control the physical interface card 7033 to send and receive traffic according to the forwarding entry.
  • the physical interface card 7033 receives the configuration information, and transmits the configuration information to the central processing unit 7011 on the main control board 701 via the central processing unit 7031.
  • the central processing unit 7011 is configured to acquire the configuration information, and generate first GRASP information according to the configuration information.
  • the physical interface card 7033 is further configured to forward the first GRASP information to the second network device.
  • the central processing unit 7011 is further configured to determine that the first network device is the first VTEP, according to the first The VTEP device information generates first VTEP information, and the physical interface card 7033 is further configured to send the second GRASP information to the second network device, where the second GRASP information includes the first VTEP information.
  • the physical interface card 7033 is further configured to receive third GRASP information sent by the second network device, where the third GRASP information includes second VTEP information, where the second VTEP information includes a second VTEP address and a second VNI.
  • the second VTEP address is bound to the second VNI; when the central processor 7011 determines that the first VNI is the same as the second VNI, the central processor 7011 is further configured to use the first VTEP information and The second VTEP information establishes a VXLAN tunnel from the first network device to the second network device.
  • the central processing unit 7011 is further configured to determine, according to the first VTEP access side port identifier included in the first VTEP device information, a layer two sub-interface of the first network device and a second layer sub-interface corresponding to the first a first VTEP access side port identifier corresponding to the first VTEP device identifier, the second layer subinterface is used to connect to the virtual machine VM, and the first VNI is used to indicate that the VM belongs to the First BD.
  • the first VTEP device information further includes a first loopback address, the first loopback address is corresponding to the first VTEP device identifier, and the central processor 7011 is further configured to determine the first loopback address as the first VTEP address.
  • the operation on the interface board 704 in the embodiment of the present invention is consistent with the operation of the interface board 703, and details are not described herein for brevity.
  • the first network device 70 of the present embodiment may correspond to the functions and/or various steps of the foregoing method embodiments, and details are not described herein.
  • this embodiment is only described by taking the first network device as an example.
  • the second network device or more network devices have the same functions as the first network device, and details are not described herein again.
  • the main control board may have one or more blocks, and when there are multiple blocks, the main control board and the standby main control board may be included.
  • the interface board may have one or more blocks. The stronger the data processing capability of the first network device, the more interface boards are provided.
  • the physical interface card on the interface board can also have one or more blocks.
  • the switching network board may not exist, and there may be one or more blocks. When there are multiple blocks, the load sharing redundant backup can be implemented together.
  • the first network device does not need to exchange the network board, and the interface board undertakes the processing function of the service data of the entire system.
  • the first network device may have at least one switching network board, and implement data exchange between multiple interface boards through the switching network board to provide large-capacity data exchange and processing capability. Therefore, the data access and processing capabilities of the first network device of the distributed architecture are greater than those of the centralized architecture. Which architecture is used depends on the specific network deployment scenario, and is not limited here.
  • FIG. 8 is a schematic diagram showing the hardware structure of still another first network device 80 according to an embodiment of the present application.
  • the first network device 80 shown in FIG. 8 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • This product form of the first network device 80 is applicable to a network architecture (eg, Software Defined Network (SDN)) that is separate based on control and forwarding.
  • SDN Software Defined Network
  • the main control board 701 of the first network device 70 shown in FIG. 7 is separated from the device to form a new independent physical device (ie, the controller 801 shown in FIG. 8), and the remaining formation Another independent physical device (ie, the first forwarding sub-device 802 as shown in FIG. 8).
  • the controller 801 interacts with the first forwarding sub-device 802 through a control channel protocol.
  • the control channel protocol may be an OpenFlow protocol, a Path Computation Element Communication Protocol (PCEP), a Border Gateway Protocol (BGP), an Interface to the Routing System (I2RS), or the like.
  • the first network device 80 in this embodiment includes the separated controller 801 and the first forwarding sub-device 802 as compared with the embodiment corresponding to FIG. 7 described above.
  • the controller 801 may be implemented based on a general-purpose physical server or a dedicated hardware structure.
  • the controller includes a receiver, a processor, a transmitter, a RAM, a ROM, and a bus (not shown in the figure). ).
  • the processor is coupled to the receiver, the transmitter, the RAM, and the ROM through a bus.
  • the BIOS is booted in the ROM or the bootloader booting system in the embedded system to boot, and the controller is put into a normal running state. After the controller enters the normal running state, the application and the operating system are run in the RAM, so that the processor performs all the functions and steps of the main control board 701 in FIG. 7 described above.
  • the first forwarding sub-device 802 may be implemented based on a dedicated hardware structure, and its function and structure are consistent with the functions and structures of the interface board 703, the interface board 704, and the switching network board 702 in FIG. 7, and perform corresponding functions and steps. . It may also be a virtual first forwarding sub-device implemented based on a universal physical server and a network function virtualization (NFV) technology, and the virtual first forwarding sub-device is a virtual router. In the scenario of the virtual first forwarding sub-device, the first forwarding sub-device mentioned in the foregoing first forwarding sub-device embodiment includes an interface board, a switching network board, and the processor can be considered as being based on the virtual environment.
  • NFV network function virtualization
  • the general physical server allocates interface resources, network resources, and processing resources used by the virtual first forwarding sub-device.
  • the function or the step of implementing the first forwarding sub-device by using the general physical server, or the function or the step of implementing the first forwarding sub-device by using the NFV technology, may refer to the embodiment of FIG. 6 .
  • controller 801 and the first forwarding sub-device 802 in the first network device 80 in this embodiment may implement various functions and steps implemented by the first network device in the method embodiment. No longer.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the first network device, which includes a program designed to execute the foregoing method embodiments.
  • FIG. 9 is a schematic structural diagram of a second network device 90 according to an embodiment of the present application.
  • the second network device 90 includes a receiving unit 901, a processing unit 902, and a transmitting unit 903.
  • the receiving unit 901 is configured to receive first GRASP information that is sent by the first network device, where the first GRASP information includes Objective information, where the Objective information is used to carry configuration information, where the configuration information includes multiple VTEP device information, where Each of the plurality of VTEP device information includes a VTEP device identifier and a VXLAN network identifier VNI, wherein the VTEP device identifier corresponds to the VNI;
  • the processing unit 902 is configured to: when the processing unit 902 determines that the device identifier of the second network device is the same as the second VTEP device identifier included in the second VTEP device information, determine that the second network device is the second VTEP, The second VTEP device information is used to indicate the second VTEP;
  • the processing unit 902 is further configured to generate second VTEP information according to the second VTEP device information, where the second VTEP device information further includes a second VNI corresponding to the second VTEP device identifier, The second VTEP information includes a second VTEP address and the second VNI, and the second VTEP address is bound to the second VNI;
  • the sending unit 903 is configured to send, to the third network device, the second GRASP information, where the second GRASP information includes the second VTEP information, where the second GRASP information is used to trigger the third network device according to the The second GRASP information establishes a VXLAN tunnel.
  • the receiving unit 901 is further configured to receive third GRASP information that is sent by the third network device, where the third GRASP information includes first VTEP information, where the first VTEP information includes a first VTEP address and a first VNI, the first VTEP address is bound to the first VNI; when the processing unit 902 determines that the first VNI is the same as the second VNI, the processing unit 902 is further configured to The first VTEP information and the second VTEP information establish a VXLAN tunnel from the second network device to the third network device.
  • the sending unit 903 is further configured to forward the first GRASP information to the third network device, where the first GRASP information is used to trigger the third network device to establish according to the first GRASP information.
  • VXLAN tunnel is further configured to forward the first GRASP information to the third network device, where the first GRASP information is used to trigger the third network device to establish according to the first GRASP information.
  • each VTEP device information of the multiple VTEP device information further includes a VTEP access side port identifier, where the VTEP access side port identifier corresponds to the VTEP device identifier
  • the processing unit 902 further uses Determining, according to the second VTEP access side port identifier included in the second VTEP device information, a Layer 2 sub-interface of the second network device and a first BD corresponding to the Layer 2 sub-interface, the second VTEP
  • the access side port identifier is associated with the second VTEP device identifier
  • the second layer sub-interface is used to connect to the virtual machine VM
  • the second VNI is used to indicate that the VM belongs to the first BD.
  • the processing unit 902 is further configured to: after the processing unit 902 determines that the second network device is the second VTEP, generate a second loopback address, and determine the second loopback address as the second The VTEP address, the second lookback address includes an identifier of the second network device, a reserved bit, and a fixed value.
  • the second network device shown in FIG. 9 can perform the corresponding steps performed by the second network device in the method in the foregoing embodiment, implements automatic configuration of the VXLAN, and avoids the problem that the existing VXLAN configuration is inefficient and the configuration error rate is high.
  • FIG. 10 is a schematic structural diagram of hardware of a second network device 100 according to an embodiment of the present application.
  • the second network device 100 shown in FIG. 10 can perform the corresponding steps performed by the second network device in the method of the above embodiment.
  • the second network device 100 includes a processor 1001, a memory 1002, an interface 1003, and a bus 1004.
  • the interface 1003 can be implemented by using a wireless or wired manner, and specifically can be a network card.
  • the above processor 1001, memory 1002, and interface 1003 are connected by a bus 1004.
  • the interface 1003 may specifically include a transmitter and a receiver, configured to send and receive information between the second network device and the first network device in the foregoing embodiment, or used in the second network device and the third network in the foregoing embodiment. Send and receive information between devices.
  • the interface 1003 is configured to support receiving, by the first network device, first GRASP information including configuration information and transmitting second GRASP information to the third network device.
  • the interface 1003 is used to support processes S104 and S107 in FIG.
  • the processor 1001 is configured to perform processing performed by the second network device in the foregoing embodiment.
  • the processor 1001 is configured to determine itself as a VTEP based on configuration information, and may also be used to generate VTEP information; and/or other processes for the techniques described herein.
  • the processor 1001 is used to support processes S105 and S106 in FIG.
  • the memory 1002 includes an operating system 10021 and an application 10022 for storing programs, codes, or instructions that can be executed when a processor or a hardware device executes the programs, codes, or instructions.
  • the memory 1002 may include a ROM and a RAM.
  • the ROM includes a BIOS or an embedded system; the RAM includes an application and an operating system.
  • booting is performed by the BIOS in the ROM or the bootloader booting system in the embedded system, and the second network device 100 is booted into a normal operating state.
  • the application program and the operating system running in the RAM are executed, thereby completing the processing procedure involving the second network device in the method embodiment.
  • FIG. 10 only shows a simplified design of the second network device 100.
  • the second network device can include any number of interfaces, processors or memories.
  • FIG. 11 is a schematic structural diagram of hardware of another second network device 110 according to an embodiment of the present application.
  • the second network device 110 shown in FIG. 11 can perform the corresponding steps performed by the second network device in the method of the above embodiment.
  • the second network device 110 includes: a main control board 1101 , an interface board 1103 , a switching network board 1102 , and an interface board 1104 .
  • the main control board 1101, the interface boards 1103 and 1104, and the switching network board 1102 are connected to each other through a system bus to implement interworking.
  • the main control board 1101 is used to complete functions such as system management, device maintenance, and protocol processing.
  • the switching network board 1102 is used to complete data exchange between each interface board (also referred to as a line card or a service board).
  • the interface boards 1103 and 1104 are configured to provide various service interfaces (for example, a POS interface, a GE interface, an ATM interface, etc.), and implement forwarding of data packets.
  • the interface board 1103 can include a central processor 11031, a forwarding entry memory 11034, a physical interface card 11033, and a network processor 11032.
  • the central processing unit 11031 is configured to control and manage the interface board and communicate with the central processing unit on the main control board.
  • the forwarding entry storage 10034 is used to save forwarding entries.
  • the physical interface card 11033 is used to complete the reception and transmission of traffic.
  • the network storage 11032 is configured to control the physical interface card 11033 to send and receive traffic according to the forwarding entry.
  • the physical interface card 11033 receives the first GRASP information from the first network device, and sends the first GRASP information to the central processing unit 11011 on the main control board 1101 via the central processing unit 11031.
  • the central processor 11011 is configured to obtain the first GRASP information, determine that the second network device is a VTEP, and generate second GRASP information that carries the VTEP information.
  • the physical interface card 11033 is further configured to send the second GRASP information to the third network device.
  • the physical interface card 11033 is further configured to receive third GRASP information sent by the third network device, where the third GRASP information includes first VTEP information, where the first VTEP information includes a first VTEP address and a first VNI The first VTEP address is bound to the first VNI; when the central processing unit 11011 determines that the first VNI is the same as the second VNI, the central processing unit 11011 is further configured to perform according to the first A VTEP information and the second VTEP information establish a VXLAN tunnel from the second network device to the third network device.
  • the physical interface card 11033 is further configured to forward the first GRASP information to the third network device, where the first GRASP information is used to trigger the third network device to establish a VXLAN tunnel according to the first GRASP information.
  • the central processing unit 11011 is further configured to determine, according to the second VTEP access side port identifier included in the second VTEP device information, a layer two sub-interface of the second network device and a second layer sub-interface corresponding to the second a BD, the second VTEP access side port identifier is associated with the second VTEP device identifier, the second layer sub-interface is used to connect to the virtual machine VM, and the second VNI is used to indicate that the VM belongs to the First BD.
  • the central processing unit 11011 is further configured to: after the central processing unit 11011 determines that the second network device is the second VTEP, generate a second loopback address, and determine the second loopback address as the second VTEP address.
  • the second lookback address includes an identifier of the second network device, a reserved bit, and a fixed value.
  • the second network device 110 of the present embodiment may correspond to the functions and/or various steps of the foregoing method embodiments, and details are not described herein again.
  • the main control board may have one or more blocks, and when there are multiple blocks, the main control board and the standby main control board may be included.
  • the interface board may have one or more blocks. The stronger the data processing capability of the second network device, the more interface boards are provided.
  • the physical interface card on the interface board can also have one or more blocks.
  • the switching network board may not exist, and there may be one or more blocks. When there are multiple blocks, the load sharing redundant backup can be implemented together.
  • the second network device does not need to exchange the network board, and the interface board undertakes the processing function of the service data of the entire system.
  • the second network device may have at least one switching network board, and exchange data between multiple interface boards through the switching network board to provide large-capacity data exchange and processing capability. Therefore, the data access and processing capabilities of the second network device of the distributed architecture are greater than those of the centralized architecture. Which architecture is used depends on the specific network deployment scenario, and is not limited here.
  • FIG. 12 is a schematic structural diagram of hardware of still another second network device 120 according to an embodiment of the present application.
  • the second network device 120 shown in FIG. 12 can perform the corresponding steps performed by the second network device in the method of the above embodiment.
  • This product form of the second network device 120 is applicable to a network architecture (eg, SDN) that is separate based on control and forwarding.
  • SDN a network architecture
  • the main control board 1101 of the second network device 110 shown in FIG. 11 is separated from the device to form a new independent physical device (ie, the controller 1201 shown in FIG. 12), and the remaining formation is performed.
  • Another independent physical device i.e., first forwarding sub-device 1202 as shown in Figure 12).
  • the controller 1201 interacts with the first forwarding sub-device 1202 through a control channel protocol.
  • the control channel protocol can be OpenFlow protocol, PCEP, BGP, I2RS, and the like. That is, the second network device 120 in this embodiment includes the separated controller 1201 and the first forwarding sub-device 1202, as compared with the embodiment corresponding to FIG. 11 described above.
  • the controller 1201 may be implemented based on a general-purpose physical server or a dedicated hardware structure.
  • the controller includes a receiver, a processor, a transmitter, a RAM, a ROM, and a bus (not shown in the figure). ).
  • the processor is coupled to the receiver, the transmitter, the RAM, and the ROM through a bus.
  • the BIOS is booted in the ROM or the bootloader booting system in the embedded system to boot, and the controller is put into a normal running state. After the controller enters the normal running state, the application and the operating system are run in the RAM, so that the processor performs all the functions and steps of the main control board 1101 in FIG.
  • the first forwarding sub-device 1202 may be implemented based on a dedicated hardware structure, and its function and structure are consistent with the functions and structures of the interface board 1103, the interface board 1104, and the switching network board 1102 in FIG. 11 described above, and perform corresponding functions and steps. . It may also be a virtual first forwarding sub-device implemented based on a universal physical server and an NFV technology, and the virtual first forwarding sub-device is a virtual router. In the scenario of the virtual first forwarding sub-device, the first forwarding sub-device mentioned in the foregoing first forwarding sub-device embodiment includes an interface board, a switching network board, and the processor can be considered as being based on the virtual environment.
  • the general physical server allocates interface resources, network resources, and processing resources used by the virtual first forwarding sub-device.
  • the function or the step of implementing the first forwarding sub-device by using a general physical server, or the function or the step of implementing the first forwarding sub-device by using the NFV technology may be specifically referred to the embodiment of FIG.
  • controller 1201 and the first forwarding sub-device 1202 in the second network device 120 in this embodiment may implement various functions and steps implemented by the second network device in the method embodiment. I will not repeat them here.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the second network device, which includes a program designed to execute the foregoing method embodiments.
  • the embodiment of the present application further includes a VXLAN configuration system, where the configuration system of the VXLAN may include a first network device and a second network device, where the first network device may be the foregoing FIG. 5 or FIG. 6 or FIG. Or the first network device in FIG. 8, the second network device may be the second network device in the foregoing FIG. 9 or FIG. 10 or FIG. 11 or FIG.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions.
  • the software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in the user equipment.
  • the processor and the storage medium may also reside as discrete components in the user equipment.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种VXLAN的配置方法、设备及系统。所述方法包括，第一网络设备获取配置信息，根据配置信息生成第一GRASP信息，并向第二网络设备发送第一GRASP信息，配置信息包括VTEP设备信息，多个VTEP设备信息分别用于指示VXLAN中包括的多个VTEP，第一GRASP信息包括Objective信息，Objective信息用于携带配置信息；第二网络设备接收第一GRASP信息，根据第一GRASP信息建立VXLAN隧道。从而，实现了VXLAN的自动配置，避免了现有VXLAN配置效率低下，且出错率较高的问题。

Description

一种VXLAN的配置方法、设备及系统
本申请要求于2017年11月09日提交中国专利局、申请号为201711100410.3、发明名称为“一种VXLAN的配置方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种虚拟扩展局域网(virtual extensible local network，VXLAN)的配置方法、设备及系统。
背景技术
VXLAN是一种将二层报文用三层协议进行封装的技术。VXLAN技术涉及MAC-in-UDP格式的报文。具体地，将基于媒体接入控制(Media Access Control，MAC)协议的以太网帧封装在用户数据报协议(user datagram protocol，UDP)报文中。进一步地，将UDP报文封装在因特网协议(Internet Protocol，IP)报文中，可以在三层网络中传输IP报文。因此，实现了以太网帧在三层网络中传送。VXLAN技术使用VXLAN网络标识符(VXLAN network identifier，VNI)标识VXLAN段(VXLAN segment)。不同的VXLAN段分别对应不同的VNI。不同的VXLAN段之间是隔离的。同一个VNI内的两台虚拟机(virtual machine，VM)进行通信时不需要经由VXLAN三层网关(VXLAN L3 gateway)。分别位于不同VNI中的两台VM通信需要经由VXLAN三层网关。VNI字段包含24比特。一个管理域最多可以包含2 16个VXLAN段。虚拟扩展局域网隧道端点(VXLAN tunnel end point，VTEP)可以被集成在网络虚拟边缘(network virtualization edge，NVE)设备中，作为VXLAN中的边缘设备。NVE设备通过VXLAN隧道(tunnel)传输VXLAN的流量。VXLAN隧道是指两台NVE设备之间的点到点逻辑隧道。
目前，主要通过人工方式来配置VXLAN，例如，当用户计划在dev1和dev2之间以及dev1和dev3之间创建VXLAN隧道时，其配置过程包括：Step1，用户进行整网规划，确认dev1和dev2之间以及dev1和dev3之间需要建立VXLAN隧道，以及确认dev1、dev2、dev3中各个设备的接口上要用到的IP地址，各个设备需要的VNI，各个设备的接入点等数据；Step2，用户分别向dev1、dev2、dev3下发配置，配置各个设备的回环(loopback)地址、设备的接口地址和网段、以及路由协议等；Step3、用户分别向dev1、dev2、dev3下发配置，配置各个设备的NVE虚接口等；Step4，用户分别向dev1、dev2、dev3下发配置，配置各个设备的二层子接口，以及与二层子接口连接的VM所属的BD，并为每个BD配置VNI等，其中，VNI用于指示VM所属的BD，BD可以被称为广播域(broadcast domain，BD)或者桥域(bridge domain，BD)。
由上可知，现有人工配置VXLAN的步骤较多，且需要逐台设备进行配置，当网络中设备数量比较多时，配置效率低下，且出错率较高。
发明内容
本申请提供一种VXLAN配置方法、设备及系统，以解决现有配置VXLAN时，配置效率低下，且出错率较高的问题。
为达到上述目的，本申请采用如下技术方案：
第一方面，提供了一种VXLAN的配置方法。第一网络设备获取配置信息，所述配置 信息包括多个VTEP设备信息，所述多个VTEP设备信息分别用于指示所述VXLAN中包括的多个VTEP；所述第一网络设备根据所述配置信息生成第一通用自主信令协议(generic autonomic signaling protocol，GRASP)信息，所述第一GRASP信息包括目标(Objective)信息，所述Objective信息用于携带所述配置信息，所述第一网络设备运行有自主网络集成模型和方法(autonomic networking integrated model and approach，ANIMA)协议；所述第一网络设备向第二网络设备发送所述第一GRASP信息，所述第一GRASP信息用于触发所述第二网络设备根据所述第一GRASP信息建立VXLAN隧道。
基于实施例提供的方案，第一网络设备可以获取用于指示VXLAN中包括的多个VTEP的配置信息，并将该配置信息携带在GRASP信息中发送至第二网络设备，第二网络设备可以根据该GRASP信息创建VXLAN隧道。通过网络设备间的信息交互完成VXLAN的配置，从而，实现VXLAN的自动配置，避免了现有配置VXLAN效率低下，且出错率较高的问题。
在第一方面的一种可能的实现方式中，所述多个VTEP设备信息中的每个VTEP设备信息包括VTEP设备标识和VNI，其中，所述VTEP设备标识与所述VNI对应。当所述第一网络设备确定所述第一网络设备的设备标识与第一VTEP设备信息包括的第一VTEP设备标识相同，所述第一网络设备确定所述第一网络设备为第一VTEP，所述第一VTEP设备信息用于指示所述第一VTEP；所述第一网络设备根据所述第一VTEP设备信息生成第一VTEP信息，其中，所述第一VTEP设备信息还包括与所述第一VTEP设备标识对应的第一VNI，所述第一VTEP信息包括第一VTEP地址和所述第一VNI，所述第一VTEP地址与所述第一VNI绑定；所述第一网络设备向所述第二网络设备发送第二GRASP信息，所述第二GRASP信息包括所述第一VTEP信息。
基于上述实现方式，第一网络设备可以根据配置信息中包括的内容确定自身为VTEP，并生成自身的VTEP信息，将自身的VTEP信息携带在GRASP信息中发送给第二网络设备，以便第二网络设备根据第一网络设备的VTEP信息和自身的VTEP信息自动地创建从第二网络设备到第一网络设备的VXLAN隧道。
在第一方面的又一种可能的实现方式中，所述第一网络设备接收所述第二网络设备发送的第三GRASP信息，所述第三GRASP信息包括第二VTEP信息，所述第二VTEP信息包括第二VTEP地址和第二VNI，所述第二VTEP地址与所述第二VNI绑定；当所述第一网络设备确定所述第一VNI与所述第二VNI相同，所述第一网络设备根据所述第一VTEP信息和所述第二VTEP信息建立从所述第一网络设备到所述第二网络设备的VXLAN隧道。
基于上述实现方式，第一网络设备可以接收第二网络设备发送的携带有第二网络设备的VTEP信息的GRASP信息，根据该GRASP信息中第二网络设备的VTEP信息和自身的VTEP信息自动地创建从第一网络设备到第二网络设备的VXLAN隧道。
在第一方面的再一种可能的实现方式中，所述多个VTEP设备信息中的每个VTEP设备信息还包括VTEP接入侧端口标识，所述VTEP接入侧端口标识与所述VTEP设备标识对应。所述第一网络设备根据所述第一VTEP设备信息包括的第一VTEP接入侧端口标识，确定所述第一网络设备的二层子接口和所述二层子接口对应的第一BD，所述第一VTEP接入侧端口标识与所述第一VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第一VNI用于指示所述VM属于所述第一BD。
基于上述实现方式，第一网络设备可以根据配置信息中包括的接入侧端口信息自动地确定第一网络设备的二层子接口和二层子接口对应的BD。从而，在第一网络设备和其他网络设备间建立VXLAN隧道之后，确定自身的二层子接口，以及连接二层子接口的VM对应的BD，便于将VM的虚拟局域网(virtual local network，VLAN)信息转换为VNI所标识的信息，并将该信息通过VXLAN隧道发送出去。
在第一方面的再一种可能的实现方式中，所述第一VTEP设备信息还包括第一回环(loopback)地址，所述第一loopback地址与所述第一VTEP设备标识对应，所述第一网络设备根据所述第一VTEP设备信息生成第一VTEP信息，所述第一网络设备将所述第一loopback地址确定为所述第一VTEP地址。
基于上述实现方式，第一网络设备可以将配置信息中包括的lookback地址作为自身的VTEP地址。从而，提高了VXLAN配置效率。
第二方面，提供了一种VXLAN的配置方法。第二网络设备接收第一网络设备发送的第一GRASP信息，所述第一GRASP信息包括Objective信息，所述Objective信息用于携带配置信息，所述配置信息包括多个虚拟扩展局域网隧道端点VTEP设备信息，所述多个VTEP设备信息中的每个VTEP设备信息包括VTEP设备标识和VXLAN网络标识符VNI，其中，所述VTEP设备标识与所述VNI对应；当所述第二网络设备确定所述第二网络设备的设备标识与第二VTEP设备信息包括的第二VTEP设备标识相同时，所述第二网络设备确定所述第二网络设备为第二VTEP，所述第二VTEP设备信息用于指示所述第二VTEP；所述第二网络设备根据所述第二VTEP设备信息生成第二VTEP信息，其中，所述第二VTEP设备信息还包括与所述第二VTEP设备标识对应的第二VNI，所述第二VTEP信息包括第二VTEP地址和所述第二VNI，所述第二VTEP地址与所述第二VNI绑定；所述第二网络设备向第三网络设备发送第二GRASP信息，所述第二GRASP信息包括所述第二VTEP信息，所述第二GRASP信息用于触发所述第三网络设备根据所述第二GRASP信息建立VXLAN隧道。
基于实施例提供的方案，第二网络设备可以接收第一网络设备发送的携带有配置信息的GRASP信息，并在根据配置信息中包括的内容确定自身为VTEP后，生成VTEP信息，将生成的VTEP信息携带在GRASP信息中发送给第三网络设备，以便第三网络设备根据第二网络设备的VTEP信息和第三网络设备自身的VTEP信息自动地创建从第三网络设备到第二网络设备的VXLAN隧道。
在第二方面的又一种可能的实现方式中，所述第二网络设备接收所述第三网络设备发送的第三GRASP信息，所述第三GRASP信息包括第一VTEP信息，所述第一VTEP信息包括第一VTEP地址和第一VNI，所述第一VTEP地址与所述第一VNI绑定；当所述第二网络设备确定所述第一VNI与所述第二VNI相同，所述第二网络设备根据所述第一VTEP信息和所述第二VTEP信息建立从所述第二网络设备到所述第三网络设备的VXLAN隧道。
基于上述实现方式，第二网络设备可以接收对端(第三网络设备)发送的携带有第三网络设备的VTEP信息的GRASP信息，根据该GRASP信息中第三网络设备的VTEP信息和第二网络设备的VTEP信息自动地创建从第二网络设备到第三网络设备的VXLAN隧道。
在第二方面的再一种可能的实现方式中，所述第三网络设备为所述第一网络设备。
基于上述实现方式，第一网络设备即具有获取配置信息并向其他网络设备发送配置信息的功能，又具有作为VTEP创建VXLAN隧道的功能。
在第二方面的再一种可能的实现方式中，所述第二网络设备向所述第三网络设备转发所述第一GRASP信息，所述第一GRASP信息用于触发所述第三网络设备根据所述第一GRASP信息建立VXLAN隧道。
基于上述可能的实现方式，第二网络设备可以作为中继节点，向其他网络设备转发配置信息。
在第二方面的再一种可能的实现方式中，所述多个VTEP设备信息中的每个VTEP设备信息还包括VTEP接入侧端口标识，所述VTEP接入侧端口标识与所述VTEP设备标识对应。所述第二网络设备根据所述第二VTEP设备信息包括的第二VTEP接入侧端口标识，确定所述第二网络设备的二层子接口和所述二层子接口对应的第一BD，所述第二VTEP接入侧端口标识与所述第二VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第二VNI用于指示所述VM属于所述第一BD。
基于上述实现方式，第二网络设备可以根据配置信息中包括的接入侧端口信息自动地确定第二网络设备的二层子接口和二层子接口对应的BD。从而，在第二网络设备和其他网络设备间建立VXLAN隧道之后，确定自身的二层子接口，以及连接二层子接口的VM对应的BD，便于将VM的VLAN信息转换为VNI所标识的信息，并将该信息通过VXLAN隧道发送出去。
在第二方面的再一种可能的实现方式中，在所述第二网络设备确定所述第二网络设备为第二VTEP之后，所述第二网络设备生成第二回环loopback地址，所述第二lookback地址包括所述第二网络设备的标识、预留比特位、以及固定数值；所述第二网络设备将所述第二loopback地址确定为所述第二VTEP地址。
基于上述实现方式，第一网络设备可以自动生成lookback地址，并将自动生成的lookback地址作为自身的VTEP地址。
第三方面，提供了第一网络设备，所述第一网络设备具有实现第一方面或者第一方面的任一实现方式中第一网络设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。不予限制。
在一个可能的设计中，第一网络设备的结构中包括处理器和接口，所述处理器被配置为支持第一网络设备执行上述方法中相应的功能。所述接口用于支持第一网络设备与第二网络设备之间的通信，向第二网络设备发送上述方法中所涉及的信息或者指令，或者从第二网络设备接收上述方法中所涉及的信息或者指令。所述第一网络设备还可以包括存储器，所述存储器用于与处理器耦合，其保存第一网络设备必要的程序指令和数据。
在另一个可能的设计中，所述第一网络设备包括：处理器、接收器、发送器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接接收器、发送器、随机存取存储器以及只读存储器。其中，当需要运行第一网络设备时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导第一网络设备进入正常运行状态。在第一网络设备进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第四方面，提供一种第一网络设备，所述第一网络设备包括：主控板和接口板，进一步，还可以包括交换网板。所述第一网络设备用于执行第一方面或第一方面的任意可能的实现方式中的方法。具体地，所述第一网络设备包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的模块。
第五方面，提供一种第一网络设备，所述第一网络设备包括控制器和第一转发子设备。所述第一转发子设备包括：接口板，进一步，还可以包括交换网板。所述第一转发子设备用于执行第四方面中的接口板的功能，进一步，还可以执行第四方面中交换网板的功能。所述控制器包括接收器、处理器、发送器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接接收器、发送器、随机存取存储器以及只读存储器。其中，当需要运行控制器时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导控制器进入正常运行状态。在控制器进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第四方面中主控板的功能。
第六方面，提供了一种计算机存储介质，用于储存为上述第一网络设备所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述方面中第一网络设备的功能或步骤。
第七方面，提供了第二网络设备，所述第二网络设备具有实现第二方面或者第二方面的任一实现方式中第二网络设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。不予限制。
在一个可能的设计中，第二网络设备的结构中包括处理器和接口，所述处理器被配置为支持第二网络设备执行上述方法中相应的功能。所述接口用于支持第二网络设备与第一网络设备，或者第二网络设备与第三网络设备之间的通信，向第二网络设备或者第三网络设备发送上述方法中所涉及的信息或者指令，或者从第二网络设备或者第三网络设备接收上述方法中所涉及的信息或者指令。所述第二网络设备还可以包括存储器，所述存储器用于与处理器耦合，其保存第二网络设备必要的程序指令和数据。
在另一个可能的设计中，所述第二网络设备包括：处理器、接收器、发送器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接接收器、发送器、随机存取存储器以及只读存储器。其中，当需要运行第二网络设备时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导第二网络设备进入正常运行状态。在第二网络设备进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第八方面，提供一种第二网络设备，所述第二网络设备包括：主控板和接口板，进一步，还可以包括交换网板。所述第二网络设备用于执行第二方面或第二方面的任意可能的实现方式中的方法。具体地，所述第二网络设备包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的模块。
第九方面，提供一种第二网络设备，所述第二网络设备包括控制器和第一转发子设备。所述第一转发子设备包括：接口板，进一步，还可以包括交换网板。所述第一转发子设备用于执行第八方面中的接口板的功能，进一步，还可以执行第八方面中交换网板的功能。 所述控制器包括接收器、处理器、发送器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接接收器、发送器、随机存取存储器以及只读存储器。其中，当需要运行控制器时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导控制器进入正常运行状态。在控制器进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第八方面中主控板的功能。
第十方面，提供了一种计算机存储介质，用于储存为上述第二网络设备所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述方面中第二网络设备的功能或步骤。
第十一方面，提供一种VXLAN的配置系统，所述VXLAN的配置系统包括第一网络设备和第二网络设备，所述第一网络设备为前述第三方面或第四方面或第五方面或者第六方面中的第一网络设备，所述第二网络设备为前述第七方面或者第八方面或者第九方面或者第十方面中的第二网络设备。
通过上述方案，本申请实施例提供的VXLAN的配置方法、设备及系统，所述第一网络设备在获取到用于指示VXLAN中包括的多个VTEP的配置信息后，将该配置信息携带在GRASP信息中发送至所述第二网络设备，所述第二网络设备根据配置信息中包括的内容确定自身为VTEP，第二网络设备生成VTEP信息，向第三网络设备发送携带有第二网络设备的VTEP信息的GRASP信息，第三网络设备根据第二网络设备的VTEP信息和第三网络设备的VTEP信息创建VXLAN隧道，同样的原理，第三网络设备也可以向第二网络设备发送第三网络设备的VTEP信息，第二网络设备根据第二网络设备的VTEP信息和第三网络设备的VTEP信息创建VXLAN隧道。从而，通过网络设备间的信息交互完成VXLAN的配置，实现VXLAN的自动配置，避免了现有配置VXLAN效率低下，且出错率较高的问题。
附图说明
图1为本申请实施例的一种EVPN-VPWS网络结构示意图；
图2为本申请实施例的一种VXLAN结构示意图；
图3为本申请实施例的一种VXLAN的配置方法流程图；
图3a为本申请实施例的一种GRASP信息格式示意图；
图3b为本申请实施例的一种lookback地址示意图；
图3c为本申请实施例的一种VTEP信息示意图；
图3d为本申请实施例的一种发送第一GRASP信息的方法流程图；
图4为本申请实施例的又一种VXLAN的配置方法流程图；
图5为本申请实施例的第一网络设备的结构示意图；
图6为本申请实施例的第一网络设备的硬件结构示意图；
图7为本申请实施例的另一第一网络设备的硬件结构示意图；
图8为本申请实施例的又一第一网络设备的硬件结构示意图；
图9为本申请实施例的第二网络设备的结构示意图；
图10为本申请实施例的第二网络设备的硬件结构示意图；
图11为本申请实施例的另一第二网络设备的硬件结构示意图；
图12为本申请实施例的又一第二网络设备的硬件结构示意图。
具体实施方式
下面结合附图对本申请的实施方式进行详细描述。
本申请提供的VXLAN的配置方法可以用于将三层路由网络配置成VXLAN，还可以用于将二层交换网络或者其他数据中心网络配置成VXLAN，不予限制。下面以将图1所示网络配置成VXLAN为例，对本申请提供的VXLAN的配置方法进行详细介绍，其他网络配置成VXLAN的过程可以参照本申请提供的方案。
如图1所示，该网络可以包括：核心层设备、第一网络设备、第二网络设备、第三网络设备以及主机。其中，核心层设备是网络的高速交换主干，能够处理来自网络设备的所有通信量，该核心网设备可以为支持二层交换技术的路由器等设备；第一网络设备、第二网络设备、第三网络设备可以为运营商边缘(provider edge，PE)设备(如路由器或交换机等)，用于将主机等站点接入网络，负责一些用户管理功能(如地址认证、用户认证、计费管理等)、以及用户信息收集工作(如用户的因特网协议(internet protocol，IP)地址、媒体接入控制(media access control，MAC)地址、访问日志等)；主机可以为用户边缘(customer edge，CE)设备(如路由器或者交换机等)，与网络设备连接，通过网络设备接入网络，每个主机上可以创建多台虚拟机(virtual machine，VM)，VM可以通过网络设备、核心层设备将数据包发送给目标VM或者主机等其他设备。
为了提高图1所示网络的网络隔离能力、以及避免虚拟机迁移受限，可以通过本申请提供的VXLAN配置方法将图1所示网络配置成图2所示的VXLAN，如：将连接主机的各个网络设备作为VTEP，不同VTEP之间可以建立VXLAN隧道(tunnel)，属于相同VXLAN的VM之间可以通过VXLAN tunnel实现二层互通，属于不同VXLAN的VM之间二层隔离。
图3为本申请实施例提供的一种VXLAN的配置方法流程图。图3所示的方法可以用于将图1所示网络配置成VXLAN中。图1所示网络可以包括第一网络设备、第二网络设备和第三网络。图3所示方法包括S101至S107，
S101：第一网络设备获取配置信息。
其中，上述第一网络设备可以为位于核心网的PE，该PE可以为路由器或者交换器。在VXLAN场景中，PE设备可以被称为NVE设备，或者NVE设备被集成在PE中，或者NVE设备作为独立设备与PE设备通信。NVE设备中可以集成VTEP实体或者VTEP设备(简称VTEP)，不予限制。在本申请实施例中，第一网络设备运行有ANIMA协议，具有自主功能，以最大限度的减少对网络管理员或集中管理系统的依赖。
上述配置信息可以根据用户的VXLAN组网需求而定，该配置信息规定了VXLAN中哪些设备为VTEP、以及VTEP的相关信息等。具体的，所述配置信息可以包括多个VTEP设备信息，所述多个VTEP设备信息可以分别用于指示VXLAN中包括的多个VTEP。每个VTEP设备信息可以包括但不限于VTEP设备标识和VNI，其中，VTEP设备标识与VNI对应。
其中，VNI用于区分虚拟网络实例，该虚拟局域网实例可以为二层虚拟网络实例或者三层虚拟网络实例，不同的虚拟网络实例对应不同的VNI。不同的虚拟网络实例之间是隔离的。同一个VNI内的两台VM进行通信时不需要经由VXLAN三层网关。分别位于不同VNI中的两台VM通信需要经由VXLAN三层网关。VNI字段包含24比特。一个管理域最多可以包含2 16个VXLAN段。
VTEP设备标识用于唯一标识作为VTEP的设备，VTEP设备标识可以为VTEP的序 列(serial number，SN)号，或者VTEP的MAC地址，不予限制。
例如，假设用户确定设备1和设备2之间需要建立VXLAN隧道、设备1和设备3之间需要建立VXLAN隧道，设备1的设备标识为001，设备2的设备标识为002，设备3的设备标识为003，则VXLAN中作为VTEP的设备分别为设备1、设备2和设备3，第一网络设备获取到的配置信息可以如表1所示，在该配置信息中VTEP设备标识001对应的VNI为vni101、vni102，VTEP设备标识002对应的VNI为vni101，VTEP设备标识003对应的VNI为vni102，如此，当设备1、设备2、设备3获取到该配置信息时，可以根据配置信息中包括与自身的设备标识相同的VTEP设备标识，确定自身为VTEP，进而与对端建立VXLAN隧道，其中，对端对应的VNI与自身对应的VNI相同。如：设备1获取到表1所示信息后，根据查表1，确定配置信息包括与设备1的设备标识相同的VTEP设备标识001，确定自身为VTEP，且根据查表1可知自身对应vni101、vni102，可以与对应vni101的设备2建立VXLAN隧道，与对应vni102的设备3建立VXLAN隧道。
表1
VTEP设备标识 VNI
001 vni101、vni102
002 vni101
003 vni102
在一种可能的实现方式中，第一网络设备包括命令行接口(command line interface，CLI)模块，CLI模块用于用户与第一网络设备之间的交互，该CLI模块可以硬件的方式来实现，也可以以处理器执行软件指令的方式来实现。第一网络设备通过CLI模块获取用户输入的配置信息，如：用户可以将配置信息分解为多条信息，第一网络设备通过CLI模块获取用户逐条输入的信息。
在另一种可能的实现方式中，配置信息以文件的形式(如可扩展标记语言(extensible markup language，XML)文件，或者JavaScript对象表示法(JavaScript Object Notation，json)文件等)存储在网络管理服务器中，第一网络设备包括配置器(configurator，CFG)模块，所述CFG组件用于对配置文件进行管理和配置，该CFG模块可以硬件的方式来实现，也可以以处理器执行软件指令的方式来实现。第一网络设备调用该CFG模块从网络管理服务器中获取配置信息。
具体的，上述第一网络设备通过CLI模块或者CFG模块获取配置信息的方式可参照图3d所述，在此不再赘述。
在又一种可能的实现方式中，配置信息以文件的形式(如XML文件或者json文件等)存储在文件传输协议(file transfer protocol，ftp)服务器中，第一网络设备通过ftp从ftp服务器获取配置信息。如：第一网络设备支持ftp协议，第一网络设备向ftp服务器发送加载(reload)命令，ftp服务器根据该加载命令向第一网络设备发送配置信息，第一网络设备接收配置信息。
其中，上述XML文件的样例如下所示：
Figure PCTCN2018088038-appb-000001
Figure PCTCN2018088038-appb-000002
上述VXLANIntent表示VXLAN文件。vxlanConfig表示VXLAN配置段。asaObj name表示Objective的名字，asaObj value表示Objective的值，即该Objective的配置信息，如：asaObj name＝”specification”value＝”HW_VXLAN_OBJ”表示该Objective为配置参数，该配置参数用于HW_VXLAN。outerVlan name表示连接用户的端口上需要配置的vlan，outerVlan value表示连接用户的端口上需要配置的vlan的是哪个vlan，如：outerVlan name＝”vlanNum”value＝”1001”表示连接用户的端口上需要配置的vlan1001。snNum name表示VXLAN中作为VTEP的设备，snNum value表示作为VTEP的设备的标识，即该设备具体为哪个设备，如：snNum name＝”dev1”value＝”001”标识作为VTEP的设备为设备1，该设备1的设备标识为001。
其中，上述json文件的样例如下所示：
Figure PCTCN2018088038-appb-000003
Virsual Service 1标识虚拟业务1。VNI Range List表示VNI的范围列表。VNI start和VNI End描述的是vni的范围，Mapping VLAN Start和Mapping VLAN End描述的是和vni绑定的vlan的范围，GateWay IP Start和GateWay IP End描述的是网关地址的范围，Mask Length描述的是网关的掩码，Service List表示业务列表，描述不同vlan的业务类型和vxlan部署方式。Service Name”:user1,”表示用户1的业务，Service Specificator type”:VLAN,”标识 业务类型为VLAN，Service Specificator value”:1024表示该业务对应的vlan为vlan1024，VXLAN Mode:1(Centralized)表示该业务部署模式为1(中心部署)。
S102：第一网络设备根据配置信息生成第一GRASP信息。
其中，第一GRASP信息可以包括Objective信息，所述Objective信息用于携带第一网络设备获取到的配置信息。如图3a所示，所述Objective信息可以包括目标名称(objective-name)、目标值(objective-value)，所述objective-name用于标识Objective，以表明Objective的作用，所述objective-value是指Objective包括的配置参数。如：在本申请实施例中，第一GRASP信息中Objective信息包括的objective-name可以为VXLAN_configuration_information(VXLAN配置信息)，以表明Objective用于VXLAN的配置，objective-value可以为第一网络设备获取的配置信息，包括各个VTEP设备信息，每个VTEP设备信息包括VTEP设备标识及其对应的VNI，该objective-value中各VTEP设备信息可以以表1的形式表示或者以其他方式表示，不予限制。
例如，配置信息包括用于指示VXLAN中包括的VTEP_1的VTEP_1设备信息和VTEP_2的VTEP_2设备信息。VTEP_1设备信息包括VTEP_1设备标识001以其对应的vni101，VTEP_2设备信息包括VTEP_2设备标识002以其对应的vni101，则携带有配置信息的Objective信息中objective-name＝“VXLAN_configuration_information”，objective-value包括的内容为”VTEP_1设备标识，VTEP_1设备标识的值，VTEP_1的vni标识，VTEP_1的vni标识的值”、”VTEP_2设备标识，VTEP_2设备标识的值，VTEP_2的vni标识，VTEP_2的vni标识的值”。其中，VTEP_1设备标识和VTEP_1的vni标识对应，VTEP_2设备标识和VTEP_2的vni标识对应，该对应关系可以用下述方式表示：snNum-name＝“VTEP_1”，snNum-value＝“001”，snNum-name＝“VTEP_2”，snNum-value＝“002”，vniNum-name＝“VTEP_1VNI”，vniNum-value＝“vni101”，vniNum-name＝“VTEP_2VNI”，vniNum-value＝“vni101”，snNum-name表示设备的标识，snNum-value表示设备的标识的具体取值，vniNum name表示某个设备对应的VNI，vniNum value表示设备对应的VNI的具体取值。
其中，Objective信息除包含objective-name、objective-value之外，如图3a所示，Objective信息还可以包括循环次数(loop-count)、目标标志(objective-flag)等字段中的一个或者多个。其中，loop-count字段用于指示所述第一GRASP信息转发的跳数。所述loop-count字段的取值范围为0到255。所述loop-count字段确保了所述第一GRASP信息传播的范围，例如取值为1时，所述第一GRASP信息可以被传播到第二网络设备，取值为2时所述第一GRASP信息可以被传播到第三网络设备。objective-flag用于指示发现会话、协商会话、同步会话或协商演练(dry-run negotiation)。
在一种可能的实现方式中，第一网络设备包括GRASP组件，第一网络设备通过GRASP组件从配置信息中获取Objective信息，将获取到的Objective信息和GRASP报文头封装在一起形成第一GRASP信息。具体的，S102的过程可参照图3d所述，在此不再赘述。
其中，如图3a所示，GRASP报文头可以包括信息类型(message_type)、会话标识(session-id)、发起端(initiator)、生存时间(time-to-live，TTL)等字段中的一个或者多个。需要说明的是，图3a所示的各个字段占用不同的比特，每个字段对应的比特位可以固定不变(如：message_type位于GRASP信息的首字段)，也可以根据实际需要变更，如：TTL在前，initiator在后，或者initiator在前，TTL在后，不予限制。
其中，message_type用于指示所述第一GRASP信息的类型，具体表示第一GRSAP信息携带的Objective信息具体属于哪种机制(发现机制或者同步机制或者协商机制或者洪泛机制)中使用的Objective信息。如：若message_type分为：M_DISCOVERY，则表示发现机制中使用的Objective信息。
session-id是指GRASP会话的标识。
initiator是指本申请所提及的GRASP信息的发起者，例如本申请中的第一网络设备。
TTL用于指示所述第一GRASP信息携带的Objective信息在网络设备中的生存时间。所述TTL的长度为32比特，取值范围为0ms到4294967295ms，ms表示毫秒。
S103：第一网络设备向第二网络设备发送第一GRASP信息。
其中，上述第二网络设备也可以为位于核心网的PE，该PE可以为路由器或者交换器；还可以为集成在VXLAN中的路由器上或者独立存在于VXLAN中的NVE设备；又可以为集成在NVE设备中的VTEP，不予限制。
在本申请实施例中，第二网络设备可以看成一个单独的网络设备，也可以看成多个网络设备。当第二网络设备看成多个网络设备时，第一网络设备向第二网络设备发送第一GRASP信息可以指：第一网络设备同时向多个网络设备发送第一GRASP。
在一种可能的实现方式中，第一网络设备运行ANIMA功能，配置anima域，通过grasp协议向anima域内的所有网络设备洪泛第一GRASP信息，其中，anima域包含第二网络设备，还可以包含其他网络设备，如：第三网络设备、第四网络设备等等。具体的，S103的过程可参照图3d所述，在此不再赘述。
S104：第二网络设备接收第一网络设备发送的第一GRASP信息。
S105：当所述第二网络设备确定所述第二网络设备的设备标识与第二VTEP设备信息包括的第二VTEP设备标识相同时，所述第二网络设备确定所述第二网络设备为第二VTEP，所述第二VTEP设备信息用于指示所述第二VTEP。
其中，第二网络设备接收到第一GRASP信息之后，可以解封装第一GRASP信息，获取第一GRASP信息包括的配置信息，并查看每个VTEP设备信息包括的VTEP设备标识，将其与自身的设备标识进行比较，若存在与自身相同的设备标识，则确定自身为VTEP，可以与对端VTEP建立VXLAN隧道。
例如，第二网络设备的设备标识为002，配置信息中VTEP_2的VTEP设备标识为002，则确定第二网络设备为VTEP_2。可以理解的是，当配置信息中未包括与第二网络设备的设备标识的VTEP设备标识时，意味着第二网络设备不能作为VTEP，不执行下述步骤S106～S107。
S106：第二网络设备根据第二VTEP设备信息生成第二VTEP信息，其中，第二VTEP设备信息还包括与第二VTEP设备标识对应的第二VNI，第二VTEP信息包括第二VTEP地址和第二VNI，第二VTEP地址与第二VNI绑定。
其中，第二网络设备根据第二VTEP设备信息生成第二VTEP信息可以包括：
第二网络设备在确定自身为VTEP后，确定第二VTEP地址，并将第二VTEP地址和第二VNI组合在一起作为第二VTEP信息。
上述第二VTEP地址可以为能够路由到第二VTEP的网络地址，该第二VTEP的地址可以为第二VTEP的lookback地址，还可以为第二VTEP的物理接口的IP地址等，不予限制。
在一种可能的实现中，第二VTEP设备信息还包括第二lookback地址，第二lookback地址与第二VTEP设备标识对应，当第二网络设备确定自身为第二VTEP时，第二网络设备将第二lookback地址确定为第二VTEP地址。
在另一种可能的实现方式中，当第二网络设备确定自身为第二VTEP时，第二网络设备根据lookback地址的生成规则生成第二lookback地址，将生成的第二lookback地址确定为第二VTEP地址。该第二lookback地址包括第二网络设备的标识、预留比特位、以及固定数值。具体的，如图3b所示，第二lookback地址包括32个比特位，其中，第0bit位(包括第0bit位)～第16bit位(包括第16bit位)填充第二网络设备的标识，第16bit位(不包括第16bit位)～第24bit位(包括第24bit位)为预留比特位，全部填充为数字0，第24bit位(不包括第24bit位)～第31bit位(包括第31bit位)填充固定数值，通常情况下，该固定数值可以为图3b所示的152。
在又一种可能的实现方式中，第二VTEP设备信息还包括第二VTEP的物理接口的IP地址的取值范围和规则，第二VTEP的物理接口与第二VTEP设备标识对应，第二VTEP的物理接口的IP地址的取值范围和规则可以用于明确采用哪种方式配置第二VTEP的物理接口的IP地址，以及配置的物理接口的IP地址所对应的地址范围。当第二网络设备确定自身为第二VTEP时，第二网络设备第二VTEP的物理接口的IP地址的取值范围和规则确定第二VTEP的物理接口的IP地址，将第二VTEP的物理接口的IP地址确定为第二VTEP地址。
在再一种可能的实现方式中，当第二网络设备确定自身为第二VTEP时，第二网络设备在物理接口上配置ipv6本地自动链路(auto-link local)，配置后物理接口按照因特网工程任务组(Internet Engineering Task Force，IETF)请求注解(Request For Comments，RFC)7217中所述方法生成一个随机的ipv6地址，将生成的ipv6地址确定为第二VTEP地址。具体的，RFC7217可以参照现有技术，在此不再赘述。
S107：第二网络设备向第三网络设备发送第二GRASP信息，第二GRASP信息包括第二VTEP信息，第二GRASP信息用于触发第三网络设备根据第二GRASP信息建立VXLAN隧道。
其中，上述第三网络设备可以为第一网络设备，还可以为除第一网络设备、第二网络设备之外的其他网络设备，不予限制。当第三网络设备为第一网络设备时，预示着第一网络设备为VTEP中的一员，所述第一网络设备不仅可以执行S101获取配置信息，还可以根据第二GRASP信息与第二网络设备之间创建VXLAN隧道。
第二网络设备可以将第二VTEP信息携带在Objective信息中，将Objective信息和GRASP报文头封装在一起生成第二GRASP信息。如：携带第二VTEP信息的Objective信息可以包括objective-name和objective-value，其中，objective-name可以用于标识Objective，Objective可以为本申请所述的第二VTEP信息，objective-name可以为第二VTEP信息的类型，objective-value可以包括Objective的配置参数，如：本申请中可以包括第二VTEP信息中的第二VTEP地址及其绑定的VNI。
需要说明的是，携带第二VTEP信息的Objective信息除携带第二VTEP信息之外，还可以包括loop-count、objective-flag等字段；第二GRASP信息中的GRASP报文头可以包括message_type、session-id、initiator、time-to-live，TTL等字段中的一个或者多个。具体的，第二GRASP信息包括的各个字段的描述可参照上述第一GRASP信息包括的字段的相 关描述，在此不再赘述。
例如，假设第二网络设备为VTEP_2，第二网络设备的地址为loopback地址1.1.1.1，与该地址绑定的VNI为vni101，第二网络设备发送的VTEP_2信息为HW_VTEP_2，objective-flag等为F_SYNC，loop-count为6，则第二网络设备生成的第二GRASP信息如图3c所示。需要说明的是，图3c仅以第二网络设备的地址绑定一个VNI为例进行了说明，在实际应用中，第二网络设备的地址可以绑定多个VNI，不予限制。
上述第二网络设备向第三网络设备发送第二GRASP信息的过程可参照S103的相关描述，如：第二网络设备也可以通过洪泛方式向第三网络设备发送第二GRASP信息，在此不再赘述。
基于图3所示方案，第一网络设备可以获取用于指示VXLAN中包括的多个VTEP的配置信息，并将该配置信息携带在第一GRASP信息中发送至第二网络设备，第二网络设备可以根据该第一GRASP信息包括的配置信息确定自身为第二VTEP，根据第二VTEP设备信息生成第二VTEP信息，并将第二VTEP信息携带在第二GRASP信息中向第三网络设备发送，以便第三网络设备根据第二GRASP信息创建VXLAN隧道。从而，通过网络设备间的信息交互完成VXLAN的配置，实现VXLAN的自动配置，避免了现有配置VXLAN效率低下，且出错率较高的问题。
可选的，在图3所示方案中，假设第三网络设备为第一网络设备，第一网络设备确定自身为第一VTEP，第一网络设备根据第二GRASP信息建立VXLAN隧道包括：
第一网络设备接收第二网络设备发送的第二GRASP信息；
当第一网络设备确定第一VNI与第二VNI相同，第一网络设备根据第一VTEP信息和第二VTEP信息建立从第一网络设备到第二网络设备的VXLAN隧道，第一VTEP设备信息包含第一VNI，第一VNI与第一VTEP设备标识对应，第一VTEP设备信息用于指示第一VTEP。
其中，第一网络设备确定自身为第一VTEP的过程为：当配置信息中第一VTEP设备信息包含的第一VTEP设备标识与自身的设备标识相同，则确定自身为第一VTEP。
第一VTEP信息可以包含第一VNI以及第一VTEP地址，第一VTEP地址与第一VNI绑定。第一VTEP地址的确定方式可参照上述第二VTEP地址的确定方式，在此不再赘述。
具体的，第一网络设备根据第一VTEP信息和第二VTEP信息建立从第一网络设备到第二网络设备的VXLAN隧道包括：
第一网络设备创建第一VNI对应的对等列表(peer list)，第一VNI对应的peer list可以包含第一网络设备地址。
例如，第二VTEP信息包含第二VTEP地址1.1.1.1、以及vni101等信息，当第一网络设备接收到第二VTEP信息时，发现第二VTEP信息中包含与自身的VNI相同的vni101，则创建vni101对应的peer list，该peer list包含第二VTEP地址1.1.1.1。具体的，其创建过程如下所示：
#
source 2.2.2.2//配置源VTEP的IP地址
vni 101 head-end peer-list 1.1.1.1
#
其中，源VTEP为第一网络设备，如此，本端VTEP(第一网络设备)就可以知道属 于vni101的对端VTEP为1.1.1.1，当本端VTEP收到来自vni101的报文时，通过VXLAN隧道向对端VTEP1.1.1.1发送该报文。
由于创建VXLAN隧道是相互的，因此，为了实现第二网络设备创建从第二网络设备到第三网络设备的VXLAN隧道，在第一网络设备确定自身为第一VTEP后，第一网络设备生成第一VTEP信息，并向第二网络设备发送携带第一VTEP信息的第三GRASP信息；第二网络设备接收第一网络设备发送的第三GRASP信息，当第二网络设备确定第二VNI与第一VNI相同，第二网络设备根据第二VTEP信息和第一VTEP信息建立从第二网络设备到第三网络设备的VXLAN隧道；
其中，第二网络设备根据第二VTEP信息和第一VTEP信息建立从第二网络设备到第一网络设备的VXLAN隧道的过程可参照上述第一网络设备根据第一VTEP信息和第二VTEP信息创建从第一网络设备到第二网络设备的VXLAN隧道的过程，在此不再赘述。
仍以第二VTEP信息包含第二VTEP地址1.1.1.1、以及vni101等信息，第一VTEP信息包含第一VTEP地址2.2.2.2，以及vni101等信息为例，第二网络设备建立VXLAN隧道的过程如下所示：
#
source 1.1.1.1//配置源VTEP的IP地址
vni 101 head-end peer-list 2.2.2.2
#
其中，源VTEP为第二网络设备，如此，本端VTEP(第二网络设备)就可以知道属于vni101的对端VTEP为2.2.2.2，当本端VTEP收到来自vni101的报文时，通过VXLAN隧道向对端VTEP2.2.2.2发送该报文。
需要说明的是，在实际应用中，若第三网络设备为第一网络设备，则第三网络设备可以直接通过S101获取配置信息；若第三网络设备为除第一网络设备、第二网络设备之外的其他网络设备，第三网络设备可以同第二网络设备一样，接收第一网络设备发送的携带有配置信息的第一GRASP信息，或者，第二网络设备作为中继节点，第二网络设备向第三网络设备转发第一GRASP信息，即第三网络设备接收第二网络设备转发的第一GRASP信息，不予限制。
可选的，VTEP设备信息还包括VTEP接入侧端口标识，VTEP接入侧端口标识与VTEP设备标识对应。图3所示方案还包括：
第一网络设备根据所述第一VTEP设备信息包括的所述第一VTEP接入侧端口标识，确定第一网络设备的二层子接口和二层子接口对应的第一BD，所述第一VTEP接入侧端口标识与第一VTEP设备标识对应，所述二层子接口用于连接VM，第一VNI用于指示VM属于第一BD。
如此，第一网络设备可以在和其他网络设备间建立VXLAN隧道后，确定自身的二层子接口，以及连接二层子接口的VM对应的BD，便于将VM的VLAN信息转换为VNI所标识的信息，并将该信息通过VXLAN隧道发送出去。
其中，VTEP接入侧端口标识用于标识VTEP的接入侧端口，VTEP接入侧端口标识可以为VTEP的接入侧端口索引号，如可以用索引号1～n对VTEP的接入侧端口进行编号，n为大于等于2的整数，或者，VTEP接入侧端口标识可以为VTEP的接入侧端口的物理地址，如以太网地址，不予限制。
例如，第一网络设备的接入侧端口为10GE1/0/1，第一网络设备对应的VNI为vni4000和vni5000，基于接入侧端口10GE1/0/1，分别创建二层子接口10GE1/0/1.1和10GE1/0/1.2，并将二层子接口10GE1/0/1.1加入BD广播域10，且为BD广播域10配置vni4000，将二层子接口10GE1/0/1.2加入BD广播域20，且为BD广播域20配置vni5000，其配置如下所示：
#
interface 10GE1/0/1.1model2//创建二层子接口10GE1/0/1.1
bridge-domain 10//表示创建一个“大二层广播域”BD，其编号为10
vxlan vni 4000//表示在BD广播域10下，指定与之关联的VNI为vni4000
#
interface 10GE1/0/1.2mode l2//创建二层子接口10GE1/0/1.2
bridge-domain 10//表示创建一个“大二层广播域”BD，其编号为20
vxlan vni 5000//表示在BD广播域20下，指定与之关联的VNI为vni5000
#
进一步可选的，第一网络设备获取到的配置信息还包括网络所使用的路由协议，该路由协议包括开放式最短路径优先(open shortest path first，ospf)、中间系统到中间系统(intermediate system to intermediate system，isis)等协议，该路由协议用于让用户选择设备间发布路由时采用哪种路由协议，是ospf协议还是isis等其他路由协议。
下面以图3d为例，描述上述第一网络设备生成第一GRASP信息，并向第二网络设备发送第二GRASP信息的过程。如图3d所示，第一网络设备可以包括ANIMA控制模块和GRASP模块。其中，ANIMA控制模块用于管理和调度第一网络设备中的其他模块；GRASP模块用于实现GRASP功能，在本申请实施例中，GRASP模块还用于生成和发送第一GRASP信息。第一网络设备还可以包括CFG模块和/或CLI模块。其中，CFG模块用于对配置文件进行管理和配置。CLI模块用于用户与第一网络设备之间的交互。ANIMA控制模块、GRASP模块、CFG模块和CLI模块可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。图3d所示的方法包括S1101至S1105。
S1101、CLI模块或CFG模块获取配置信息。
第一网络设备可以通过CLI模块或CFG模块获取配置信息。例如，用户通过CLI模块输入配置信息。又例如，基于用户的配置请求，ANIMA控制模块调用CFG模块对配置信息进行配置。这样，CFG模块可以获取配置信息。
S1102、CLI模块或CFG模块向ANIMA控制模块发送配置信息。
CLI模块或CFG模块可以直接向ANIMA控制模块发送配置信息，或者将配置信息携带在第一消息后，向ANIMA控制模块发送第一消息。第一消息的格式可以使用网络设备内部的消息传送格式，例如socket消息。
S1103、ANIMA控制模块向GRASP模块转发配置信息。
ANIMA控制模块可以将接收到的配置信息转发给GRASP模块，或者将接收到的第一消息转发给GRASP模块。
S1104、GRASP模块根据配置信息生成第一GRASP信息。
具体的，GRASP模块可以图3a所示格式将配置信息封装在第一GRASP信息中。
S1105、GRASP模块发送第一GRASP信息。
根据前述，ANIMA控制模块用于管理和调度第一网络设备中的其他模块，ANIMA控制模块接收到配置信息后，将配置信息发送到GRASP模块。GRASP模块在接收到配置信息后，可以利用配置信息生成第一GRASP信息。然后，GRASP模块向第二网络设备发送第一GRASP信息。其中，第一GRASP信息报文的具体实现方式可以参见图3a所示。
上述S1101至S1105说明了CLI模块或CFG模块通过ANIMA控制模块向GRASP模块主动上报配置信息的实现方式。在另一种实现方式中，GRASP模块可以主动的向ANIMA控制模块进行请求，询问ANIMA控制模块配置信息。ANIMA控制模块调用CLI模块或CFG模块进行上报。CLI模块或CFG模块进行上报的过程可以参见上述S1101至S1105的说明，此处不进行赘述。
下面以网络设备1的设备标识为管理设备(主要负责配置信息的发送)，网络设备1的设备标识001，网络设备2的设备标识为002，网络设备1和网络设备2分别作为VTEP_1和VTEP_2，VTEP_1和VTEP_2之间建立VXLAN隧道为例，对本申请提供的技术方案进行详细说明。
图4为本申请实施例提供又一种VXLAN的配置方法流程图，如图4所示，所述方法包括：
S401：网络设备1获取配置信息，所述配置信息包括VTEP_1设备信息和VTEP_2设备信息，VTEP_1设备信息用于指示VXLAN中的VTEP_1，VTEP_1设备信息包括VTEP_1设备标识001，以及与VTEP_1设备标识001对应的vni101，VTEP_2设备信息用于指示VXLAN中的VTEP_2，VTEP_2设备信息包括VTEP_2设备标识002，以及与VTEP_2设备标识002对应的vni101。
其中，网络设备1获取配置信息的过程可参照上述S101中第一网络设备获取配置信息的过程，在此不再赘述。
S402：网络设备1根据配置信息生成GRASP信息1，并向网络设备2发送GRASP信息1。
其中，GRASP信息1包括GRASP报文头、VTEP_1设备标识001，VTEP_1设备标识001对应的vni101，VTEP_2设备标识002，VTEP_2设备标识002对应的vni101等信息。具体的，网络设备1生成GRASP信息1以及发送GRASP1的过程可参照上述第一网络设备生成第一GRASP信息以及发送第一GRASP信息的过程，在此不再赘述。
S403：网络设备2接收GRASP信息1，查找GRASP信息1中配置信息包括的各个VTEP设备信息，当确定VTEP_2设备标识002与自身的设备标识相同，网络设备2确定自身为VTEP_2，且自身对应vni101。
S404：网络设备1查找配置信息中包括的各个VTEP设备信息，当确定VTEP_1的设备标识001与自身的设备标识相同，网络设备1确定自身为VTEP_1，且自身对应vni101。
S405：网络设备1确定VTEP_1地址，将自身的vni101与VTEP_1地址携带在VTEP_1信息中。网络设备1根据VTEP_1信息生成GRASP信息2，并向网络设备2发送GRASP信息2。
其中，网络设备1确定VTEP_1地址的过程可参照上述第一网络设备确定第一VTEP地址的过程，在此不再赘述。
网络设备1根据VTEP_1信息生成GRASP信息2可以包括：网络设备1将VTEP_1信息携带在Objective信息中，将Objective信息和GRASP报文头封装在一起生成GRASP 信息2。
S406：网络设备2接收GRASP信息2，确定GRASP信息2中VTEP_1信息包括的vni101与自身的vni101相同，创建vni101的peer list，该peer list包括VTEP_1地址，至此实现从网络设备2到网络设备1的VXLAN隧道的建立。
S407：网络设备2确定VTEP_2地址，将vni101与VTEP_2地址携带在VTEP_2信息中。网络设备2根据VTEP_2信息生成GRASP信息3，并向网络设备1发送GRASP信息3。
其中，网络设备2确定VTEP_2地址的过程可参照上述第二网络设备确定第二VTEP地址的过程，在此不再赘述。
网络设备2根据VTEP_2信息生成GRASP信息2可以包括：网络设备2将VTEP_2信息携带在Objective信息中，将Objective信息和GRASP报文头封装在一起生成GRASP信息2。
S408：网络设备1接收GRASP信息3，当确定GRASP信息3中VTEP_2信息包括的vni101与自身的vni101相同，创建vni101的peer list，该peer list包括VTEP_2地址，实现从网络设备1到网络设备2的VXLAN隧道的建立。
需要说明的是，在一种可能的实现方式中，S405～S406，以及S407～S408同时执行或者S405～S406在前执行、S407～S408在后执行，或者S407～S408在前执行、S405～S406在后执行，不予限制。此外，S402～S403可以和S405同时执行，也可以在S405和S406之间执行，不予限制。
图5为本申请实施例的第一网络设备50的结构示意图。图5所示的第一网络设备50运行有ANIMA协议，第一网络设备50可以执行上述实施例的方法中第一网络设备执行的相应步骤。如图5所示，所述第一网络设备500包括接收单元501，处理单元502和发送单元503。
所述接收单元501，用于获取配置信息，所述配置信息包括多个VTEP设备信息，所述多个VTEP设备信息分别用于指示所述VXLAN中包括的多个VTEP。
所述处理单元502，用于根据所述接收单元501获取的配置信息生成第一GRASP信息，所述第一GRASP信息包括Objective信息，所述Objective信息用于携带所述配置信息。
所述发送单元503，用于向第二网络设备发送所述处理单元502生成的第一GRASP信息，所述第一GRASP信息用于触发所述第二网络设备根据所述第一GRASP信息建立VXLAN隧道。
可选的，所述多个VTEP设备信息中的每个VTEP设备信息包括VTEP设备标识和VXLAN网络标识符VNI，其中，所述VTEP设备标识与所述VNI对应。当所述处理单元502确定所述第一网络设备的设备标识与第一VTEP设备信息包括的第一VTEP设备标识相同，所述处理单元502确定所述第一网络设备为第一VTEP，所述第一VTEP设备信息用于指示所述第一VTEP；所述处理单元502还用于根据所述第一VTEP设备信息生成第一VTEP信息，其中，所述第一VTEP设备信息还包括与所述第一VTEP设备标识对应的第一VNI，所述第一VTEP信息包括第一VTEP地址和所述第一VNI，所述第一VTEP地址与所述第一VNI绑定；所述发送单元503还用于向所述第二网络设备发送第二GRASP信息，所述第二GRASP信息包括所述第一VTEP信息。
可选的，所述接收单元501还用于接收所述第二网络设备发送的第三GRASP信息， 所述第三GRASP信息包括第二VTEP信息，所述第二VTEP信息包括第二VTEP地址和第二VNI，所述第二VTEP地址与所述第二VNI绑定；当所述处理单元502确定所述第一VNI与所述第二VNI相同，所述处理单元502还用于根据所述第一VTEP信息和所述第二VTEP信息建立从所述第一网络设备到所述第二网络设备的VXLAN隧道。
可选的，所述多个VTEP设备信息中的每个VTEP设备信息还包括VTEP接入侧端口标识，所述VTEP接入侧端口标识与所述VTEP设备标识对应，所述处理单元502还用于根据所述第一VTEP设备信息包括的第一VTEP接入侧端口标识，确定所述第一网络设备的二层子接口和所述二层子接口对应的第一BD，所述第一VTEP接入侧端口标识与所述第一VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第一VNI用于指示所述VM属于所述第一BD。
可选的，所述第一VTEP设备信息还包括第一回环loopback地址，所述第一loopback地址与所述第一VTEP设备标识对应，所述处理单元502根据所述第一VTEP设备信息生成第一VTEP信息，具体包括：所述处理单元502还用于将所述第一loopback地址确定为所述第一VTEP地址。
图5所示的第一网络设备可以执行上述实施例的方法中第一网络设备执行的相应步骤。实现了VXLAN的自动配置，避免了现有VXLAN配置效率低下，且配置出错率高的问题。
图6为本申请实施例的第一网络设备60的硬件结构示意图。图6所示的第一网络设备60可以执行上述实施例的方法中第一网络设备执行的相应步骤。
如图6所示，所述第一网络设备60包括处理器601、存储器602、接口603和总线604。其中接口603可以通过无线或有线的方式实现，具体来讲可以是网卡。上述处理器601、存储器602和接口603通过总线604连接。
所述接口603具体可以包括发送器和接收器，用于第一网络设备与上述实施例中的第二网络设备之间收发信息。例如，所述接口603用于支持获取配置信息和向第二网络设备发送第一GRASP信息。作为举例，所述接口603用于支持图3中的过程S101和S103。所述处理器601用于执行上述实施例中由第一网络设备进行的处理。例如，所述处理器601用于生成第一GRASP信息；和/或用于本文所描述的技术的其他过程。作为举例，所述处理器601用于支持图3中的过程S102。存储器602包括操作系统6021和应用程序6022，用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及第一网络设备的处理过程。可选的，所述存储器602可以包括只读存储器(Read-only Memory，ROM)和随机存取存储器(Random Access Memory，RAM)。其中，所述ROM包括基本输入/输出系统(Basic Input/Output System，BIOS)或嵌入式系统；所述RAM包括应用程序和操作系统。当需要运行第一网络设备60时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导第一网络设备60进入正常运行状态。在第一网络设备60进入正常运行状态后，运行在RAM中的应用程序和操作系统，从而，完成方法实施例中涉及第一网络设备的处理过程。
可以理解的是，图6仅仅示出了第一网络设备60的简化设计。在实际应用中，第一网络设备可以包含任意数量的接口，处理器或者存储器。
图7为本申请实施例的另一第一网络设备70的硬件结构示意图。图7所示的第一网络设备70可以执行上述实施例的方法中第一网络设备执行的相应步骤。
如图7所述，第一网络设备70包括：主控板701、交换网板702、接口板703和接口 板704。主控板701、接口板703和接口板704，以及交换网板702之间通过系统总线与系统背板相连实现互通。其中，主控板701用于完成系统管理、设备维护、协议处理等功能。交换网板702用于完成各接口板(接口板也称为线卡或业务板)之间的数据交换。接口板703和704用于提供各种业务接口(例如，POS接口、GE接口、ATM接口等)，并实现数据包的转发。
接口板703可以包括中央处理器7011、转发表项存储器7034、物理接口卡7033和网络处理器7032。其中，中央处理器7031用于对接口板进行控制管理并与主控板上的中央处理器进行通信。转发表项存储器7034用于保存转发表项。物理接口卡7033用于完成流量的接收和发送。网络存储器7032用于根据所述转发表项控制物理接口卡7033收发流量。
具体的，物理接口卡7033接收配置信息，并且经由中央处理器7031向主控板701上的中央处理器7011发送所述配置信息。中央处理器7011用于获取所述配置信息，并根据该配置信息生成第一GRASP信息。物理接口卡7033还用于向所述第二网络设备转发所述第一GRASP信息。
当确定所述第一网络设备的设备标识与第一VTEP设备信息包括的第一VTEP设备标识相同，中央处理器7011还用于确定所述第一网络设备为第一VTEP，根据所述第一VTEP设备信息生成第一VTEP信息，所述物理接口卡7033还用于向所述第二网络设备发送第二GRASP信息，所述第二GRASP信息包括所述第一VTEP信息。
物理接口卡7033还用于接收所述第二网络设备发送的第三GRASP信息，所述第三GRASP信息包括第二VTEP信息，所述第二VTEP信息包括第二VTEP地址和第二VNI，所述第二VTEP地址与所述第二VNI绑定；当所述中央处理器7011确定所述第一VNI与所述第二VNI相同，中央处理器7011还用于根据所述第一VTEP信息和所述第二VTEP信息建立从所述第一网络设备到所述第二网络设备的VXLAN隧道。
所述中央处理器7011还用于根据所述第一VTEP设备信息包括的第一VTEP接入侧端口标识，确定所述第一网络设备的二层子接口和所述二层子接口对应的第一BD，所述第一VTEP接入侧端口标识与所述第一VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第一VNI用于指示所述VM属于所述第一BD。
所述第一VTEP设备信息还包括第一loopback地址，所述第一loopback地址与所述第一VTEP设备标识对应，中央处理器7011还用于将所述第一loopback地址确定为所述第一VTEP地址。
应理解，本发明实施例中接口板704上的操作与所述接口板703的操作一致，为了简洁，不再赘述。应理解，本实施例的第一网络设备70可对应于上述方法实施例所具有的功能和/或所实施的各种步骤，在此不再赘述。另外，本实施例仅以第一网络设备为例进行说明，应当理解，第二网络设备，或者更多的网络设备具有与所述第一网络设备相同的功能，此处不再一一赘述。
此外，需要说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，第一网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，第一网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，第一网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数 据交换，提供大容量的数据交换和处理能力。所以，分布式架构的第一网络设备的数据接入和处理能力要大于集中式架构的设备。具体采用哪种架构，取决于具体的组网部署场景，此处不做任何限定。
图8为本申请实施例的又一第一网络设备80的硬件结构示意图。图8所示的第一网络设备80可以执行上述实施例的方法中第一网络设备执行的相应步骤。
第一网络设备80的这种产品形态适用于基于控制与转发分离的网络架构(例如，软件定义网络(Software Defined Network,SDN))。在SDN中，如图7所示的第一网络设备70的主控板701从设备中分离出来，形成新的独立的物理设备(即如图8所示的控制器801)，剩下的形成另一独立的物理设备(即如图8所示的第一转发子设备802)。控制器801与第一转发子设备802通过控制通道协议实现交互。控制通道协议可以是开放流(OpenFlow)协议、路径计算通信协议(Path Computation Element Communication Protocol,PCEP)、边界网关协议(Border Gateway Protocol，BGP)、路由系统接口(Interface to the Routing System，I2RS)等。也就是说，与上述图7所对应的实施例相比，本实施中的第一网络设备80包括分离出去的控制器801和第一转发子设备802。
控制器801可以是基于通用的物理服务器实现或者是专用的硬件结构实现，在一个设计示例中，所述控制器包括接收器、处理器、发送器、RAM、ROM以及总线(图中未示出)。其中，处理器通过总线分别耦接接收器、发送器、RAM以及ROM。其中，当需要运行控制器时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导控制器进入正常运行状态。在控制器进入正常运行状态后，在RAM中运行应用程序和操作系统，使得该处理器执行上述图7中主控板701的所有功能和步骤。
第一转发子设备802可以是基于专用的硬件结构实现，其功能和结构与上述图7中的接口板703、接口板704和交换网板702的功能和结构保持一致，执行相应的功能和步骤。也可以是基于通用的物理服务器和网络功能虚拟化(Netwrk Function Virtulization，NFV)技术实现的虚拟第一转发子设备，所述虚拟第一转发子设备为虚拟路由器。在虚拟第一转发子设备的场景下，上述实体第一转发子设备实施例中提到的该第一转发子设备包括接口板、交换网板以及处理器在虚拟环境下可以认为是其所基于通用的物理服务器分配给该虚拟第一转发子设备所使用的接口资源、网络资源以及处理资源。采用通用物理服务器实施该第一转发子设备的功能或步骤，或者采用通用物理服务器并利用NFV技术实施该第一转发子设备的功能或步骤具体可以参考图6的实施例。
应理解，本实施例中第一网络设备80中的控制器801和该第一转发子设备802可以实现方法实施例中的第一网络设备所实施的各种功能、步骤，为了简洁，在此不再赘述。
另外，本申请实施例提供了一种计算机存储介质，用于储存为上述第一网络设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
图9为本申请实施例的第二网络设备90的结构示意图。如图9所示，所述第二网络设备90包括接收单元901，处理单元902和发送单元903。
接收单元901，用于接收第一网络设备发送的第一GRASP信息，所述第一GRASP信息包括Objective信息，所述Objective信息用于携带配置信息，所述配置信息包括多个VTEP设备信息，所述多个VTEP设备信息中的每个VTEP设备信息包括VTEP设备标识和VXLAN网络标识符VNI，其中，所述VTEP设备标识与所述VNI对应；
处理单元902，用于当所述处理单元902确定所述第二网络设备的设备标识与第二 VTEP设备信息包括的第二VTEP设备标识相同时，确定所述第二网络设备为第二VTEP，所述第二VTEP设备信息用于指示所述第二VTEP；
所述处理单元902，还用于根据所述第二VTEP设备信息生成第二VTEP信息，其中，所述第二VTEP设备信息还包括与所述第二VTEP设备标识对应的第二VNI，所述第二VTEP信息包括第二VTEP地址和所述第二VNI，所述第二VTEP地址与所述第二VNI绑定；
发送单元903，用于向第三网络设备发送第二GRASP信息，所述第二GRASP信息包括所述第二VTEP信息，所述第二GRASP信息用于触发所述第三网络设备根据所述第二GRASP信息建立VXLAN隧道。
可选的，所述接收单元901还用于接收所述第三网络设备发送的第三GRASP信息，所述第三GRASP信息包括第一VTEP信息，所述第一VTEP信息包括第一VTEP地址和第一VNI，所述第一VTEP地址与所述第一VNI绑定；当所述处理单元902确定所述第一VNI与所述第二VNI相同，所述处理单元902还用于根据所述第一VTEP信息和所述第二VTEP信息建立从所述第二网络设备到所述第三网络设备的VXLAN隧道。
可选的，所述发送单元903还用于向所述第三网络设备转发所述第一GRASP信息，所述第一GRASP信息用于触发所述第三网络设备根据所述第一GRASP信息建立VXLAN隧道。
可选的，所述多个VTEP设备信息中的每个VTEP设备信息还包括VTEP接入侧端口标识，所述VTEP接入侧端口标识与所述VTEP设备标识对应，所述处理单元902还用于根据所述第二VTEP设备信息包括的第二VTEP接入侧端口标识，确定所述第二网络设备的二层子接口和所述二层子接口对应的第一BD，所述第二VTEP接入侧端口标识与所述第二VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第二VNI用于指示所述VM属于所述第一BD。
可选的，所述处理单元902还用于在所述处理单元902确定所述第二网络设备为第二VTEP之后，生成第二loopback地址，将所述第二loopback地址确定为所述第二VTEP地址，所述第二lookback地址包括所述第二网络设备的标识、预留比特位、以及固定数值。
图9所示的第二网络设备可以执行上述实施例的方法中第二网络设备执行的相应步骤，实现了VXLAN的自动配置，避免了现有VXLAN配置效率低下且配置出错率高的问题。
图10为本申请实施例的第二网络设备100的硬件结构示意图。图10所示的第二网络设备100可以执行上述实施例的方法中第二网络设备执行的相应步骤。
如图10所示，所述第二网络设备100包括处理器1001、存储器1002、接口1003和总线1004。其中接口1003可以通过无线或有线的方式实现，具体来讲可以是网卡。上述处理器1001、存储器1002和接口1003通过总线1004连接。
所述接口1003具体可以包括发送器和接收器，用于第二网络设备与上述实施例中的第一网络设备之间收发信息，或者用于第二网络设备与上述实施例中的第三网络设备之间收发信息。例如，所述接口1003用于支持从所述第一网络设备接收包括有配置信息的第一GRASP信息和向所述第三网络设备发送第二GRASP信息。作为举例，所述接口1003用于支持图3中的过程S104和S107。所述处理器1001用于执行上述实施例中由第二网络设备进行的处理。例如，所述处理器1001用于根据配置信息确定自身为VTEP，还可以用于生成VTEP信息；和/或用于本文所描述的技术的其他过程。作为举例，所述处理器1001 用于支持图3中的过程S105和S106。存储器1002包括操作系统10021和应用程序10022，用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及第二网络设备的处理过程。可选的，所述存储器1002可以包括ROM和RAM。其中，所述ROM包括BIOS或嵌入式系统；所述RAM包括应用程序和操作系统。当需要运行第二网络设备100时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导第二网络设备100进入正常运行状态。在第二网络设备100进入正常运行状态后，运行在RAM中的应用程序和操作系统，从而，完成方法实施例中涉及第二网络设备的处理过程。
可以理解的是，图10仅仅示出了第二网络设备100的简化设计。在实际应用中，第二网络设备可以包含任意数量的接口，处理器或者存储器。
图11为本申请实施例的另一第二网络设备110的硬件结构示意图。图11所示的第二网络设备110可以执行上述实施例的方法中第二网络设备执行的相应步骤。
如图11所述，第二网络设备110包括：主控板1101、接口板1103、交换网板1102和接口板1104。主控板1101、接口板1103和1104，以及交换网板1102之间通过系统总线与系统背板相连实现互通。其中，主控板1101用于完成系统管理、设备维护、协议处理等功能。交换网板1102用于完成各接口板(接口板也称为线卡或业务板)之间的数据交换。接口板1103和1104用于提供各种业务接口(例如，POS接口、GE接口、ATM接口等)，并实现数据包的转发
接口板1103可以包括中央处理器11031、转发表项存储器11034、物理接口卡11033和网络处理器11032。其中，中央处理器11031用于对接口板进行控制管理并与主控板上的中央处理器进行通信。转发表项存储器11034用于保存转发表项。物理接口卡11033用于完成流量的接收和发送。网络存储器11032用于根据所述转发表项控制物理接口卡11033收发流量。
具体的，物理接口卡11033接收来自所述第一网络设备的第一GRASP信息，并且，经由中央处理器11031向主控板1101上的中央处理器11011发送所述第一GRASP信息。中央处理器11011用于获取所述第一GRASP信息，确定第二网络设备为VTEP，并生成携带有VTEP信息的第二GRASP信息。物理接口卡11033还用于向所述第三网络设备发送所述第二GRASP信息。
所述物理接口卡11033还用于接收所述第三网络设备发送的第三GRASP信息，所述第三GRASP信息包括第一VTEP信息，所述第一VTEP信息包括第一VTEP地址和第一VNI，所述第一VTEP地址与所述第一VNI绑定；当所述中央处理器11011确定所述第一VNI与所述第二VNI相同，所述中央处理器11011还用于根据所述第一VTEP信息和所述第二VTEP信息建立从所述第二网络设备到所述第三网络设备的VXLAN隧道。
所述物理接口卡11033还用于向所述第三网络设备转发所述第一GRASP信息，所述第一GRASP信息用于触发所述第三网络设备根据所述第一GRASP信息建立VXLAN隧道。
所述中央处理器11011还用于根据所述第二VTEP设备信息包括的第二VTEP接入侧端口标识，确定所述第二网络设备的二层子接口和所述二层子接口对应的第一BD，所述第二VTEP接入侧端口标识与所述第二VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第二VNI用于指示所述VM属于所述第一BD。
所述中央处理器11011还用于在所述中央处理器11011确定所述第二网络设备为第二 VTEP之后，生成第二loopback地址，将所述第二loopback地址确定为所述第二VTEP地址，所述第二lookback地址包括所述第二网络设备的标识、预留比特位、以及固定数值。
应理解，本发明实施例中接口板1104上的操作与所述接口板1103的操作一致，为了简洁，不再赘述。
应理解，本实施例的第二网络设备110可对应于上述方法实施例所具有的功能和/或所实施的各种步骤，在此不再赘述。
此外，需要说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，第二网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，第二网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，第二网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的第二网络设备的数据接入和处理能力要大于集中式架构的设备。具体采用哪种架构，取决于具体的组网部署场景，此处不做任何限定。
图12为本申请实施例的又一第二网络设备120的硬件结构示意图。图12所示的第二网络设备120可以执行上述实施例的方法中第二网络设备执行的相应步骤。
第二网络设备120的这种产品形态适用于基于控制与转发分离的网络架构(例如，SDN)。在SDN中，如图11所示的第二网络设备110的主控板1101从设备中分离出来，形成新的独立的物理设备(即如图12所示的控制器1201)，剩下的形成另一独立的物理设备(即如图12所示的第一转发子设备1202)。控制器1201与第一转发子设备1202通过控制通道协议实现交互。控制通道协议可以是OpenFlow协议、PCEP、BGP、I2RS等。也就是说，与上述图11所对应的实施例相比，本实施中的第二网络设备120包括分离出去的控制器1201和第一转发子设备1202。
控制器1201可以是基于通用的物理服务器实现或者是专用的硬件结构实现，在一个设计示例中，所述控制器包括接收器、处理器、发送器、RAM、ROM以及总线(图中未示出)。其中，处理器通过总线分别耦接接收器、发送器、RAM以及ROM。其中，当需要运行控制器时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导控制器进入正常运行状态。在控制器进入正常运行状态后，在RAM中运行应用程序和操作系统，使得该处理器执行上述图11中主控板1101的所有功能和步骤。
第一转发子设备1202可以是基于专用的硬件结构实现，其功能和结构与上述图11中的接口板1103、接口板1104和交换网板1102的功能和结构保持一致，执行相应的功能和步骤。也可以是基于通用的物理服务器和NFV技术实现的虚拟第一转发子设备，所述虚拟第一转发子设备为虚拟路由器。在虚拟第一转发子设备的场景下，上述实体第一转发子设备实施例中提到的该第一转发子设备包括接口板、交换网板以及处理器在虚拟环境下可以认为是其所基于通用的物理服务器分配给该虚拟第一转发子设备所使用的接口资源、网络资源以及处理资源。采用通用物理服务器实施该第一转发子设备的功能或步骤，或者采用通用物理服务器并利用NFV技术实施该第一转发子设备的功能或步骤具体可以参考图10的实施例。
应理解的是，本实施例中第二网络设备120中的控制器1201和该第一转发子设备1202 可以实现方法实施例中的第二网络设备所实施的各种功能、步骤，为了简洁，在此不再赘述。
另外，本申请实施例提供了一种计算机存储介质，用于储存为上述第二网络设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本申请实施例还包括一种VXLAN的配置系统，所述VXLAN的配置系统可以包括第一网络设备和第二网络设备，其中，所述第一网络设备可以为前述图5或图6或图7或图8中的第一网络设备，第二网络设备可以为前述图9或图10或图11或图12中的第二网络设备。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于用户设备中。当然，处理器和存储介质也可以作为分立组件存在于用户设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明。所应理解的是，以上所述仅为本申请的具体实施方式而已。

Claims (25)

  1. 一种虚拟扩展局域网VXLAN的配置方法，其特征在于，所述方法包括：
    第一网络设备获取配置信息，所述配置信息包括多个虚拟扩展局域网隧道端点VTEP设备信息，所述多个VTEP设备信息分别用于指示所述VXLAN中包括的多个VTEP；
    所述第一网络设备根据所述配置信息生成第一通用自主信令协议GRASP信息，所述第一GRASP信息包括目标Objective信息，所述Objective信息用于携带所述配置信息，所述第一网络设备运行有自主网络集成模型和方法ANIMA协议；
    所述第一网络设备向第二网络设备发送所述第一GRASP信息，所述第一GRASP信息用于触发所述第二网络设备根据所述第一GRASP信息建立VXLAN隧道。
  2. 根据权利要求1所述的方法，其特征在于，所述多个VTEP设备信息中的每个VTEP设备信息包括VTEP设备标识和VXLAN网络标识符VNI，其中，所述VTEP设备标识与所述VNI对应，所述方法还包括：
    当所述第一网络设备确定所述第一网络设备的设备标识与第一VTEP设备信息包括的第一VTEP设备标识相同，所述第一网络设备确定所述第一网络设备为第一VTEP，所述第一VTEP设备信息用于指示所述第一VTEP；
    所述第一网络设备根据所述第一VTEP设备信息生成第一VTEP信息，其中，所述第一VTEP设备信息还包括与所述第一VTEP设备标识对应的第一VNI，所述第一VTEP信息包括第一VTEP地址和所述第一VNI，所述第一VTEP地址与所述第一VNI绑定；
    所述第一网络设备向所述第二网络设备发送第二GRASP信息，所述第二GRASP信息包括所述第一VTEP信息。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收所述第二网络设备发送的第三GRASP信息，所述第三GRASP信息包括第二VTEP信息，所述第二VTEP信息包括第二VTEP地址和第二VNI，所述第二VTEP地址与所述第二VNI绑定；
    当所述第一网络设备确定所述第一VNI与所述第二VNI相同，所述第一网络设备根据所述第一VTEP信息和所述第二VTEP信息建立从所述第一网络设备到所述第二网络设备的VXLAN隧道。
  4. 根据权利要求2或3所述的方法，其特征在于，所述多个VTEP设备信息中的每个VTEP设备信息还包括VTEP接入侧端口标识，所述VTEP接入侧端口标识与所述VTEP设备标识对应，所述方法还包括：
    所述第一网络设备根据所述第一VTEP设备信息包括的第一VTEP接入侧端口标识，确定所述第一网络设备的二层子接口和所述二层子接口对应的第一广播域BD，所述第一VTEP接入侧端口标识与所述第一VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第一VNI用于指示所述VM属于所述第一BD。
  5. 根据权利要求2-4任一项所述的方法，其特征在于，所述第一VTEP设备信息还包括第一回环loopback地址，所述第一loopback地址与所述第一VTEP设备标识对应，所述第一网络设备根据所述第一VTEP设备信息生成第一VTEP信息，包括：
    所述第一网络设备将所述第一loopback地址确定为所述第一VTEP地址。
  6. 一种虚拟扩展局域网VXLAN的配置方法，其特征在于，所述方法包括：
    第二网络设备接收第一网络设备发送的第一通用自主信令协议GRASP信息，所述第 一GRASP信息包括目标Objective信息，所述Objective信息用于携带配置信息，所述配置信息包括多个虚拟扩展局域网隧道端点VTEP设备信息，所述多个VTEP设备信息中的每个VTEP设备信息包括VTEP设备标识和VXLAN网络标识符VNI，其中，所述VTEP设备标识与所述VNI对应；
    当所述第二网络设备确定所述第二网络设备的设备标识与第二VTEP设备信息包括的第二VTEP设备标识相同时，所述第二网络设备确定所述第二网络设备为第二VTEP，所述第二VTEP设备信息用于指示所述第二VTEP；
    所述第二网络设备根据所述第二VTEP设备信息生成第二VTEP信息，其中，所述第二VTEP设备信息还包括与所述第二VTEP设备标识对应的第二VNI，所述第二VTEP信息包括第二VTEP地址和所述第二VNI，所述第二VTEP地址与所述第二VNI绑定；
    所述第二网络设备向第三网络设备发送第二GRASP信息，所述第二GRASP信息包括所述第二VTEP信息，所述第二GRASP信息用于触发所述第三网络设备根据所述第二GRASP信息建立VXLAN隧道。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收所述第三网络设备发送的第三GRASP信息，所述第三GRASP信息包括第一VTEP信息，所述第一VTEP信息包括第一VTEP地址和第一VNI，所述第一VTEP地址与所述第一VNI绑定；
    当所述第二网络设备确定所述第一VNI与所述第二VNI相同，所述第二网络设备根据所述第一VTEP信息和所述第二VTEP信息建立从所述第二网络设备到所述第三网络设备的VXLAN隧道。
  8. 根据权利要求6或7所述的方法，其特征在于，
    所述第三网络设备为所述第一网络设备。
  9. 根据权利要求6或7所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备向所述第三网络设备转发所述第一GRASP信息，所述第一GRASP信息用于触发所述第三网络设备根据所述第一GRASP信息建立VXLAN隧道。
  10. 根据权利要求6-9任一项所述的方法，其特征在于，所述多个VTEP设备信息中的每个VTEP设备信息还包括VTEP接入侧端口标识，所述VTEP接入侧端口标识与所述VTEP设备标识对应，所述方法还包括：
    所述第二网络设备根据所述第二VTEP设备信息包括的第二VTEP接入侧端口标识，确定所述第二网络设备的二层子接口和所述二层子接口对应的第一广播域BD，所述第二VTEP接入侧端口标识与所述第二VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第二VNI用于指示所述VM属于所述第一BD。
  11. 根据权利要求6-10任一项所述的方法，其特征在于，在所述第二网络设备确定所述第二网络设备为第二VTEP之后，所述方法还包括：
    所述第二网络设备生成第二回环loopback地址，所述第二lookback地址包括所述第二网络设备的标识、预留比特位、以及固定数值；
    所述第二网络设备将所述第二loopback地址确定为所述第二VTEP地址。
  12. 一种第一网络设备，其特征在于，所述第一网络设备包括：
    接收器，用于获取配置信息，所述配置信息包括多个虚拟扩展局域网隧道端点VTEP设备信息，所述多个VTEP设备信息分别用于指示所述VXLAN中包括的多个VTEP；
    处理器，用于根据所述接收器获取的配置信息生成第一通用自主信令协议GRASP信息，所述第一GRASP信息包括目标Objective信息，所述Objective信息用于携带所述配置信息，所述第一网络设备运行有自主网络集成模型和方法ANIMA协议；
    发送器，用于向第二网络设备发送所述处理器生成的第一GRASP信息，所述第一GRASP信息用于触发所述第二网络设备根据所述第一GRASP信息建立VXLAN隧道。
  13. 根据权利要求12所述的第一网络设备，其特征在于，所述多个VTEP设备信息中的每个VTEP设备信息包括VTEP设备标识和VXLAN网络标识符VNI，其中，所述VTEP设备标识与所述VNI对应，
    当所述处理器确定所述第一网络设备的设备标识与第一VTEP设备信息包括的第一VTEP设备标识相同，所述处理器还用于确定所述第一网络设备为第一VTEP，所述第一VTEP设备信息用于指示所述第一VTEP；
    所述处理器还用于根据所述第一VTEP设备信息生成第一VTEP信息，其中，所述第一VTEP设备信息还包括与所述第一VTEP设备标识对应的第一VNI，所述第一VTEP信息包括第一VTEP地址和所述第一VNI，所述第一VTEP地址与所述第一VNI绑定；
    所述发送器还用于向所述第二网络设备发送第二GRASP信息，所述第二GRASP信息包括所述第一VTEP信息。
  14. 根据权利要求13所述的第一网络设备，其特征在于，
    所述接收器还用于接收所述第二网络设备发送的第三GRASP信息，所述第三GRASP信息包括第二VTEP信息，所述第二VTEP信息包括第二VTEP地址和第二VNI，所述第二VTEP地址与所述第二VNI绑定；
    当所述处理器确定所述第一VNI与所述第二VNI相同，所述处理器还用于根据所述第一VTEP信息和所述第二VTEP信息建立从所述第一网络设备到所述第二网络设备的VXLAN隧道。
  15. 根据权利要求13或14所述的第一网络设备，其特征在于，所述多个VTEP设备信息中的每个VTEP设备信息还包括VTEP接入侧端口标识，所述VTEP接入侧端口标识与所述VTEP设备标识对应，
    所述处理器还用于根据所述第一VTEP设备信息包括的第一VTEP接入侧端口标识，确定所述第一网络设备的二层子接口和所述二层子接口对应的第一广播域BD，所述第一VTEP接入侧端口标识与所述第一VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第一VNI用于指示所述VM属于所述第一BD。
  16. 根据权利要求13-15任一项所述的第一网络设备，其特征在于，所述第一VTEP设备信息还包括第一回环loopback地址，所述第一loopback地址与所述第一VTEP设备标识对应，所述处理器根据所述第一VTEP设备信息生成第一VTEP信息，具体包括：
    所述处理器还用于将所述第一loopback地址确定为所述第一VTEP地址。
  17. 一种第二网络设备，其特征在于，所述第二网络设备包括：
    接收器，用于接收第一网络设备发送的第一通用自主信令协议GRASP信息，所述第一GRASP信息包括目标Objective信息，所述Objective信息用于携带配置信息，所述配置信息包括多个虚拟扩展局域网隧道端点VTEP设备信息，所述多个VTEP设备信息中的每个VTEP设备信息包括VTEP设备标识和VXLAN网络标识符VNI，其中，所述VTEP设备标识与所述VNI对应；
    处理器，用于当所述处理器确定所述第二网络设备的设备标识与第二VTEP设备信息包括的第二VTEP设备标识相同时，确定所述第二网络设备为第二VTEP，所述第二VTEP设备信息用于指示所述第二VTEP；
    所述处理器，还用于根据所述第二VTEP设备信息生成第二VTEP信息，其中，所述第二VTEP设备信息还包括与所述第二VTEP设备标识对应的第二VNI，所述第二VTEP信息包括第二VTEP地址和所述第二VNI，所述第二VTEP地址与所述第二VNI绑定；
    发送器，用于向第三网络设备发送第二GRASP信息，所述第二GRASP信息包括所述第二VTEP信息，所述第二GRASP信息用于触发所述第三网络设备根据所述第二GRASP信息建立VXLAN隧道。
  18. 根据权利要求17所述的第二网络设备，其特征在于，
    所述接收器还用于接收所述第三网络设备发送的第三GRASP信息，所述第三GRASP信息包括第一VTEP信息，所述第一VTEP信息包括第一VTEP地址和第一VNI，所述第一VTEP地址与所述第一VNI绑定；
    当所述处理器确定所述第一VNI与所述第二VNI相同，所述处理器还用于根据所述第一VTEP信息和所述第二VTEP信息建立从所述第二网络设备到所述第三网络设备的VXLAN隧道。
  19. 根据权利要求17或18所述的第二网络设备，其特征在于，
    所述第三网络设备为所述第一网络设备。
  20. 根据权利要求17或18所述的第二网络设备，其特征在于，
    所述发送器还用于向所述第三网络设备转发所述第一GRASP信息，所述第一GRASP信息用于触发所述第三网络设备根据所述第一GRASP信息建立VXLAN隧道。
  21. 根据权利要求17-20任一项所述的第二网络设备，其特征在于，所述多个VTEP设备信息中的每个VTEP设备信息还包括VTEP接入侧端口标识，所述VTEP接入侧端口标识与所述VTEP设备标识对应，
    所述处理器还用于根据所述第二VTEP设备信息包括的第二VTEP接入侧端口标识，确定所述第二网络设备的二层子接口和所述二层子接口对应的第一广播域BD，所述第二VTEP接入侧端口标识与所述第二VTEP设备标识对应，所述二层子接口用于连接虚拟机VM，所述第二VNI用于指示所述VM属于所述第一BD。
  22. 根据权利要求17-21任一项所述的第二网络设备，其特征在于，
    在所述处理器确定所述第二网络设备为第二VTEP之后，所述处理器还用于生成第二回环loopback地址，将所述第二loopback地址确定为所述第二VTEP地址，所述第二lookback地址包括所述第二网络设备的标识、预留比特位、以及固定数值。
  23. 一种第一网络设备，所述第一网络设备包括至少一个处理器以及存储器；其特征在于，
    所述存储器用于存储计算机程序，使得所述计算机程序被所述至少一个处理器执行时实现如权利要求1-5中任一项所述的虚拟扩展局域网VXLAN的配置方法。
  24. 一种第二网络设备，第二网络设备包括至少一个处理器以及存储器；其特征在于，
    所述存储器用于存储计算机程序，使得所述计算机程序被所述至少一个处理器执行时实现如权利要求6-11中任一项所述的虚拟扩展局域网VXLAN的配置方法。
  25. 一种虚拟扩展局域网VXLAN的配置系统，其特征在于，所述VXLAN的配置系统 包括第一网络设备和第二网络设备，所述第一网络设备为权利要求12至16中任一项权利要求所述的第一网络设备或者权利要求23所述的第一网络设备，所述第二网络设备为权利要求17至22中任一项权利要求所述的第二网络设备或者权利要求24所述的第二网络设备。
PCT/CN2018/088038 2017-11-09 2018-05-23 一种vxlan的配置方法、设备及系统 WO2019091088A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18876451.8A EP3694157B1 (en) 2017-11-09 2018-05-23 Vxlan configuration method, device and system
US16/861,914 US11310080B2 (en) 2017-11-09 2020-04-29 VXLAN configuration method, device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711100410.3 2017-11-09
CN201711100410.3A CN109768908B (zh) 2017-11-09 2017-11-09 一种vxlan的配置方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/861,914 Continuation US11310080B2 (en) 2017-11-09 2020-04-29 VXLAN configuration method, device, and system

Publications (1)

Publication Number Publication Date
WO2019091088A1 true WO2019091088A1 (zh) 2019-05-16

Family

ID=66438720

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088038 WO2019091088A1 (zh) 2017-11-09 2018-05-23 一种vxlan的配置方法、设备及系统

Country Status (4)

Country Link
US (1) US11310080B2 (zh)
EP (1) EP3694157B1 (zh)
CN (1) CN109768908B (zh)
WO (1) WO2019091088A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11165650B1 (en) 2020-07-10 2021-11-02 Dell Products L.P. Multi-fabric VLAN configuration system

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110677337B (zh) * 2019-09-27 2021-10-12 新华三信息安全技术有限公司 数据转发方法、装置、网络设备及计算机可读存储介质
CN111935013B (zh) * 2020-09-17 2021-01-08 南京中兴软件有限责任公司 流量转发控制方法及装置、流量转发方法及芯片、交换机
US11700673B2 (en) * 2020-12-24 2023-07-11 Nile Global, Inc. Methods and systems of automatic network service initiation
CN112948057B (zh) * 2021-03-08 2023-07-21 中国联合网络通信集团有限公司 虚拟机迁移控制方法、云管理平台、sdn管理器
CN113194019B (zh) * 2021-05-12 2022-05-31 中国联合网络通信集团有限公司 数据传输的控制方法、电子设备
US20220400075A1 (en) * 2021-06-09 2022-12-15 Hewlett Packard Enterprise Development Lp Failure detection and mitigation in an mc-lag environment
US20230188382A1 (en) * 2021-12-14 2023-06-15 Cisco Technology, Inc. Managing Traffic for Endpoints in Data Center Environments to Provide Cloud Management Connectivity

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104243268A (zh) * 2014-09-19 2014-12-24 杭州华三通信技术有限公司 Vxlan与隧道的关联方法及装置
CN104767666A (zh) * 2015-04-15 2015-07-08 杭州华三通信技术有限公司 虚拟可扩展局域网隧道终端建立隧道方法和设备
CN106878065A (zh) * 2017-01-18 2017-06-20 新华三技术有限公司 一种分布式聚合系统的配置方法及装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100473040C (zh) * 2005-06-07 2009-03-25 中兴通讯股份有限公司 一种虚拟专用网络的实现方法
US9729578B2 (en) * 2014-01-10 2017-08-08 Arista Networks, Inc. Method and system for implementing a network policy using a VXLAN network identifier
CN105282003B (zh) * 2014-06-20 2019-03-22 中国电信股份有限公司 建立隧道的方法和系统以及隧道控制器和虚拟交换机
CN105591916B (zh) * 2014-10-22 2018-10-30 华为技术有限公司 一种报文传输方法及装置
CN105634770B (zh) * 2014-10-29 2019-05-07 新华三技术有限公司 部署虚拟扩展局域网的方法和装置
CN104468394B (zh) * 2014-12-04 2018-02-09 新华三技术有限公司 一种vxlan网络中报文转发方法及装置
CN105812221B (zh) * 2014-12-31 2019-07-12 华为技术有限公司 虚拟可扩展本地区域网络中数据传输的设备和方法
CN106209553B (zh) * 2015-04-30 2019-07-23 华为技术有限公司 报文处理方法、设备及系统
US10063467B2 (en) * 2015-05-18 2018-08-28 Cisco Technology, Inc. Virtual extensible local area network performance routing
JP6549996B2 (ja) * 2016-01-27 2019-07-24 アラクサラネットワークス株式会社 ネットワーク装置、通信方法、及び、ネットワークシステム
CN107147580B (zh) * 2017-06-23 2020-09-25 北京佰才邦技术有限公司 一种隧道建立的方法及通信系统
CN107294711B (zh) * 2017-07-11 2021-03-30 国网辽宁省电力有限公司 一种基于vxlan技术的电力信息内网报文加密发布方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104243268A (zh) * 2014-09-19 2014-12-24 杭州华三通信技术有限公司 Vxlan与隧道的关联方法及装置
CN104767666A (zh) * 2015-04-15 2015-07-08 杭州华三通信技术有限公司 虚拟可扩展局域网隧道终端建立隧道方法和设备
CN106878065A (zh) * 2017-01-18 2017-06-20 新华三技术有限公司 一种分布式聚合系统的配置方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, A GENERIC AUTONOMIC SIGNALING PROTOCOL (GRASP), 13 July 2017 (2017-07-13), XP015120940 *
See also references of EP3694157A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11165650B1 (en) 2020-07-10 2021-11-02 Dell Products L.P. Multi-fabric VLAN configuration system
US11652692B2 (en) 2020-07-10 2023-05-16 Dell Products L.P. Multi-fabric VLAN configuration system

Also Published As

Publication number Publication date
EP3694157B1 (en) 2023-05-31
CN109768908A (zh) 2019-05-17
EP3694157A1 (en) 2020-08-12
US11310080B2 (en) 2022-04-19
CN109768908B (zh) 2020-10-09
EP3694157A4 (en) 2020-11-18
US20200267022A1 (en) 2020-08-20

Similar Documents

Publication Publication Date Title
WO2019091088A1 (zh) 一种vxlan的配置方法、设备及系统
US10798760B2 (en) Method for controlling network slice, forwarding device, control device, and communications system
CN108574616B (zh) 一种处理路由的方法、设备及系统
US11374857B2 (en) Network device management method and apparatus, and system for indicating a network device to perform management operation
CN106452857B (zh) 生成配置信息的方法和网络控制单元
US10193707B2 (en) Packet transmission method and apparatus
US10263808B2 (en) Deployment of virtual extensible local area network
EP2843906B1 (en) Method, apparatus, and system for data transmission
CN111726286A (zh) Evpn报文处理方法、设备及系统
EP3069471B1 (en) Optimized multicast routing in a clos-like network
US20200186389A1 (en) Virtual Extensible Local Area Network (VXLAN) Packet Encapsulation
JP6838760B2 (ja) トラフィックエンジニアリングサービスマッピング
EP4044523A1 (en) Packet forwarding method, first network device, and first device group
US20190215191A1 (en) Deployment Of Virtual Extensible Local Area Network
US11929851B2 (en) Gateway selection method, device, and system
JP2019519146A (ja) ルーティング確立、パケット送信
US9438475B1 (en) Supporting relay functionality with a distributed layer 3 gateway
WO2022166465A1 (zh) 一种报文处理方法及相关装置
US20210328918A1 (en) Packet Forwarding Method and Network Device
CN108259292B (zh) 建立隧道的方法及装置
WO2022068389A1 (zh) 一种基于用户组的报文转发方法、设备及系统
CN113285780B (zh) 配置传送管道的方法、装置及系统
WO2023155733A1 (zh) 一种网络切片信息传输方法及装置
WO2023093786A1 (zh) 一种引流的方法、设备及系统
CN114363252A (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: 18876451

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018876451

Country of ref document: EP

Effective date: 20200506