A method, device, and medium for monitoring VXLAN package configuration based on an M-LAG environment.

Abstract

This specification discloses a method, device, and medium for monitoring VXLAN encapsulation configuration in an M-LAG environment, relating to the field of switch technology. The method includes: obtaining the interface encapsulation configuration type of a specified M-LAG member interface in a pre-built M-LAG environment, wherein the interface encapsulation configuration type includes: Untag type, Taged type, and Default type; configuring one or more current VXLAN encapsulation configuration information for the specified M-LAG member interface based on the interface encapsulation configuration type; sending the current VXLAN encapsulation configuration information to the peer device of the specified M-LAG member device through the synchronization interface corresponding to the specified M-LAG member interface; and monitoring the consistency of the VXLAN encapsulation configuration in the M-LAG environment based on the peer device and the current VXLAN encapsulation configuration information. This VXLAN encapsulation configuration check ensures the consistency of the VXLAN encapsulation configuration at both ends of the M-LAG member interface, guaranteeing traffic forwarding between M-LAG devices.

Description

Technical Field

[0001] This specification relates to the field of switch technology, and in particular to a VXLAN encapsulation configuration monitoring method, device and medium based on the M-LAG environment. Background Technology

[0002] As data center tenants grow larger and the number of virtual machines increases significantly, traditional Layer 2 VLANs are no longer sufficient to meet the needs of large numbers of virtual tenants in large Layer 2 networks. Simultaneously, to enable flexible allocation of virtual resources within computers, it is necessary to support the flexible migration of virtual machines across partitions and even across data centers. Virtual Extensible Local Area Network (VXLAN), one of the NVO3 (Network Virtualization over Layer 3) standard technologies defined by the IETF, encapsulates Layer 2 packets using Layer 3 protocols, establishing Layer 2 Ethernet network tunnels on top of Layer 3 networks. This enables cross-regional Layer 2 interconnection while simultaneously meeting the needs of large-scale Layer 2 virtual migration and multi-tenancy in data centers.

[0003] In a typical "Spine-Leaf" network, to meet users' reliability requirements for VXLAN networks, stacking or multichassis link aggregation groups (M-LAG) dual-homed access are often used to form VTEP (VXLAN Tunnel EndPoint) nodes on the leaf side, achieving redundancy and load balancing. In M-LAG dual-homed access, two M-LAG devices are virtualized as one device, achieving dual-homed access with edge devices, with servers or hosts then connected to the edge devices. Due to the characteristics of M-LAG, both M-LAG devices have independent control and forwarding planes. Certain configurations on both ends of the M-LAG need to be consistent to avoid problems such as M-LAG malfunction or loops. In VXLAN scenarios, to enable communication between VXLAN tunnels, encapsulation types need to be configured on the M-LAG member ports to distinguish traffic forwarding from different tunnels. The member port configurations on both sides of the M-LAG device need to be identical to ensure proper table synchronization. The existing configuration check cannot check the VXLAN encapsulation configuration, which may lead to inconsistencies in the VXLAN encapsulation configuration at both ends of the M-LAG member port, affecting traffic forwarding between M-LAG devices. Summary of the Invention

[0004] This specification provides one or more embodiments of a VXLAN encapsulation configuration monitoring method, device, and medium based on an M-LAG environment to solve the following technical problem: existing configuration checks cannot check VXLAN encapsulation configurations, which may lead to inconsistencies in the VXLAN encapsulation configurations at both ends of the M-LAG member port, affecting traffic forwarding between M-LAG devices.

[0005] One or more embodiments of this specification employ the following technical solutions:

[0006] This specification provides one or more embodiments for obtaining the interface encapsulation configuration type of a specified M-LAG member interface in a pre-built M-LAG environment, wherein the interface encapsulation configuration type includes: Untag type, Taged type, and Default type; based on the interface encapsulation configuration type of the specified M-LAG member interface, configuring one or more current VXLAN encapsulation configuration information for the specified M-LAG member interface; sending the current VXLAN encapsulation configuration information to the peer device of the specified M-LAG member device through the synchronization interface corresponding to the specified M-LAG member interface; and performing configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment according to the peer device and the current VXLAN encapsulation configuration information.

[0007] Further, based on the peer device and the current VXLAN encapsulation configuration information, configuration consistency monitoring is performed on the VXLAN encapsulation configuration of the M-LAG environment. Specifically, this includes: obtaining the local VXLAN encapsulation configuration information pre-stored by the peer device, wherein the local VXLAN encapsulation configuration information is the VXLAN encapsulation configuration information of the M-LAG member interface of the peer device; and comparing the current VXLAN encapsulation configuration information with the local VXLAN encapsulation configuration information to perform configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment.

[0008] Furthermore, the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information are compared. Specifically, this includes comparing the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information. When the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information are inconsistent, the interface status of the M-LAG member interface of the peer device is set to err-disable.

[0009] Furthermore, the method further includes: when the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information are inconsistent, configuring VXLAN encapsulation configuration information for the M-LAG member interface of the peer device according to the current VXLAN encapsulation configuration information to generate current peer VXLAN encapsulation configuration information; synchronizing the current peer VXLAN encapsulation configuration information of the M-LAG member interface of the peer device to the designated M-LAG member device through the synchronization interface; and through the designated M-LAG member device, performing configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment according to the current peer VXLAN encapsulation configuration information and the pre-stored designated local VXLAN encapsulation configuration information, wherein the designated local VXLAN encapsulation configuration information is the VXLAN encapsulation configuration information of the M-LAG member interface of the designated M-LAG member device.

[0010] Furthermore, through the designated M-LAG member device, configuration consistency monitoring of the VXLAN encapsulation configuration in the M-LAG environment is performed based on the current peer VXLAN encapsulation configuration information and the pre-stored designated local VXLAN encapsulation configuration information. Specifically, this includes: comparing the current peer VXLAN encapsulation configuration information and the designated local VXLAN encapsulation configuration information through the designated M-LAG member device; when the current peer VXLAN encapsulation configuration information and the designated local VXLAN encapsulation configuration information are consistent, the interface state of the peer device's M-LAG member interface is changed to UP state.

[0011] Further, the current VXLAN encapsulation configuration information is sent to the peer device through the synchronization interface corresponding to the designated M-LAG member interface. Specifically, this includes: generating a current VXLAN encapsulation configuration message corresponding to the current VXLAN encapsulation configuration information according to a preset configuration message interaction format, wherein the current VXLAN encapsulation configuration message includes a message type for identifying the current VXLAN encapsulation configuration information, an operation identifier code corresponding to the current VXLAN encapsulation configuration information, and the current VXLAN encapsulation configuration information; and synchronizing the current VXLAN encapsulation configuration message to the peer device through the peer-link port between the designated M-LAG member device and the peer device.

[0012] Further, the current VXLAN encapsulation configuration information is sent to the peer device through the synchronization interface corresponding to the designated M-LAG member interface. Specifically, this includes: when the interface encapsulation configuration type of the M-LAG member interface is the Taged type, dividing the current VXLAN encapsulation configuration information into multiple encapsulation configuration sub-information; generating an encapsulation configuration sub-message corresponding to each encapsulation configuration sub-message according to a preset configuration message interaction format, wherein the encapsulation configuration sub-message includes a last identifier and the encapsulation configuration sub-message, the last identifier being used to identify whether the encapsulation configuration sub-message is the last segment of the multiple encapsulation configuration sub-messages; and synchronizing the current VXLAN encapsulation configuration message to the peer device through the peer-link port between the designated M-LAG member device and the peer device.

[0013] Furthermore, before performing configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment based on the peer device and the current VXLAN encapsulation configuration information, the method further includes: obtaining multiple encapsulation configuration sub-messages received by the peer device through the peer-link port between the designated M-LAG member device and the peer device; determining whether the peer device is in a reception completion state based on the last identifier in each encapsulation configuration sub-message; and when the peer device is in the reception completion state, performing configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment based on the peer device and the current VXLAN encapsulation configuration information.

[0014] This specification provides one or more embodiments of a VXLAN encapsulated configuration monitoring device based on an M-LAG environment, including:

[0015] At least one processor; and,

[0016] A memory communicatively connected to the at least one processor; wherein,

[0017] The memory stores instructions that can be executed by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0018] Obtain the interface encapsulation configuration type of a specified M-LAG member interface in the pre-built M-LAG environment, wherein the interface encapsulation configuration type includes: Untag type, Taged type, and Default type; based on the interface encapsulation configuration type of the specified M-LAG member interface, configure one or more current VXLAN encapsulation configuration information for the specified M-LAG member interface; send the current VXLAN encapsulation configuration information to the peer device of the specified M-LAG member device through the synchronization interface corresponding to the specified M-LAG member interface; and perform configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment according to the peer device and the current VXLAN encapsulation configuration information.

[0019] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0020] Obtain the interface encapsulation configuration type of a specified M-LAG member interface in the pre-built M-LAG environment, wherein the interface encapsulation configuration type includes: Untag type, Taged type, and Default type; based on the interface encapsulation configuration type of the specified M-LAG member interface, configure one or more current VXLAN encapsulation configuration information for the specified M-LAG member interface; send the current VXLAN encapsulation configuration information to the peer device of the specified M-LAG member device through the synchronization interface corresponding to the specified M-LAG member interface; and perform configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment according to the peer device and the current VXLAN encapsulation configuration information.

[0021] The above-mentioned at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects: Through the above technical solution, the current VXLAN encapsulation configuration information is synchronized to the peer device. Based on the peer device and the current VXLAN encapsulation configuration information, in the M-LAG dual-homed access environment, the VXLAN encapsulation configuration of the M-LAG environment is monitored for consistency and checked, thus ensuring the consistency of the VXLAN encapsulation configuration at both ends of the M-LAG member port and ensuring the traffic forwarding between M-LAG devices. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0023] Figure 1 A flowchart illustrating a VXLAN encapsulation configuration monitoring method based on an M-LAG environment, provided in the embodiments of this specification;

[0024] Figure 2 A flowchart illustrating another VXLAN encapsulation configuration monitoring method based on an M-LAG environment provided in the embodiments of this specification;

[0025] Figure 3 This is a schematic diagram of a VXLAN-encapsulated configuration monitoring device based on an M-LAG environment, provided as an embodiment of this specification. Detailed Implementation

[0026] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0027] As data center tenants grow larger and the number of virtual machines increases significantly, traditional Layer 2 VLANs are no longer sufficient to meet the needs of large numbers of virtual tenants in large Layer 2 networks. Simultaneously, to enable flexible allocation of virtual resources within computers, it is necessary to support the flexible migration of virtual machines across partitions and even across data centers. Virtual Extensible Local Area Network (VXLAN), one of the NVO3 (Network Virtualization over Layer 3) standard technologies defined by the IETF, encapsulates Layer 2 packets using Layer 3 protocols, establishing Layer 2 Ethernet network tunnels on top of Layer 3 networks. This enables cross-regional Layer 2 interconnection while simultaneously meeting the needs of large-scale Layer 2 virtual migration and multi-tenancy in data centers.

[0028] In a typical "Spine-Leaf" network, to meet users' reliability requirements for VXLAN networks, stacking or multichassis link aggregation groups (M-LAG) dual-homed access are often used to form VTEP (VXLAN Tunnel EndPoint) nodes on the leaf side, achieving redundancy and load balancing. In M-LAG dual-homed access, two M-LAG devices are virtualized as one device, achieving dual-homed access with edge devices, with servers or hosts then connected to the edge devices. Due to the characteristics of M-LAG, both M-LAG devices have independent control and forwarding planes. Certain configurations on both ends of the M-LAG need to be consistent to avoid problems such as M-LAG malfunction or loops. In VXLAN scenarios, to enable communication between VXLAN tunnels, encapsulation types need to be configured on the M-LAG member ports to distinguish traffic forwarding from different tunnels. The member port configurations on both sides of the M-LAG device need to be identical to ensure proper table synchronization.

[0029] Currently, there are two types of consistency checks for M-LAG networks: critical configuration type (type 1) and general configuration type (type 2). Type 1 configuration includes global STP enabling, STP type, BPDU protection enabling, and MSTP-VLAN mapping; it also includes STP enabling, STP root protection, and LACP type for M-LAG member interfaces. Type 2 configuration includes global VLAN configuration, static MAC address entries, dynamic ARP aging time, dynamic MAC address aging time, BD configuration, BDIF configuration, and VLANIF configuration; it also includes STP priority, VLAN configuration, M-LAG member parameter configuration, and the number of member ports of the aggregation interface to which the M-LAG member port belongs.

[0030] The existing configuration check cannot check the VXLAN encapsulation configuration, which may lead to inconsistencies in the VXLAN encapsulation configuration at both ends of the M-LAG member port, affecting traffic forwarding between M-LAG devices.

[0031] This specification provides a method for monitoring VXLAN encapsulation configuration based on an M-LAG environment. It should be noted that the execution entity in this specification can be a server or any device with data processing capabilities. Figure 1 This specification provides a flowchart illustrating a VXLAN encapsulation configuration monitoring method based on an M-LAG environment, as shown in the embodiments below. Figure 1 As shown, the main steps include the following:

[0032] Step S101: Obtain the interface encapsulation configuration type of the specified M-LAG member interface in the pre-built M-LAG environment.

[0033] In one embodiment of this specification, an M-LAG environment is pre-built as a dual-homed access environment, including a designated M-LAG member device and its peer device. The designated M-LAG member device is the primary device, and its peer device is the backup device. They are connected via a peer-link port for configuration synchronization. The interface encapsulation configuration type of the designated M-LAG member interface of the designated M-LAG member device is determined. The interface encapsulation configuration types include: Untag type, Taged type, and Default type.

[0034] It should be noted that the Untag type encapsulated interface only accepts packets without tags. Whether encapsulating or decapsulating the original packet into a VXLAN packet, this interface does not perform VLAN tag processing. The corresponding operations include adding, replacing, and stripping. The Taged type encapsulated interface only accepts packets with VLAN tags. When encapsulating the original packet into a VXLAN packet, it removes the outer VLAN tag. When decapsulating the VXLAN packet, if the inner packet has a VLAN tag, it replaces it with the specified VLAN tag before forwarding; if the inner packet does not have a VLAN tag, it adds the specified VLAN tag before forwarding. The Default type encapsulated interface receives all packets, regardless of whether they have VLAN tags. Whether encapsulating or decapsulating the original packet into a VXLAN packet, this type of interface does not perform VLAN tag processing. The corresponding operations include adding, replacing, and stripping. When configuring, you first need to specify the wrapper type under the interface, namely Untag type, Taged type or Default type. Only one wrapper can be configured under Untag type and Default type, while one or more wrappers can be configured under Taged type.

[0035] Step S102: Based on the interface encapsulation configuration type of the specified M-LAG member interface, configure one or more current VXLAN encapsulation configuration information for the specified M-LAG member interface.

[0036] In one embodiment of this specification, one or more current VXLAN encapsulation configuration information are configured for a specified M-LAG member interface based on the interface encapsulation configuration type of the specified M-LAG member interface.

[0037] Step S103: Send the current VXLAN encapsulation configuration information to the peer device of the specified M-LAG member device through the synchronization interface corresponding to the specified M-LAG member interface.

[0038] In one embodiment of this specification, to ensure configuration consistency between a designated M-LAG member device and its peer device, it is necessary to synchronize the current VXLAN encapsulation configuration information through the synchronization interface corresponding to the designated M-LAG member interface. Here, the synchronization interface is the peer-link port between the designated M-LAG member device and the peer device. The current VXLAN encapsulation configuration information corresponding to the designated M-LAG member device is sent to the peer device of the designated M-LAG member device through the peer-link port.

[0039] The current VXLAN encapsulation configuration information is sent to the peer device through the synchronization interface corresponding to the designated M-LAG member interface. Specifically, this includes: generating a current VXLAN encapsulation configuration message corresponding to the current VXLAN encapsulation configuration information according to a preset configuration message interaction format, wherein the current VXLAN encapsulation configuration message includes a message type for identifying the current VXLAN encapsulation configuration information, an operation identifier code corresponding to the current VXLAN encapsulation configuration information, and the current VXLAN encapsulation configuration information; and synchronizing the current VXLAN encapsulation configuration message to the peer device through the peer-link port between the designated M-LAG member device and the peer device.

[0040] In one embodiment of this specification, a configuration message interaction format is pre-set. This format includes a message header and a message body. The message header includes basic message information, such as ID and length. The message body includes a message category identifier for VXLAN, an operation identifier code, and configuration information. Following this configuration message interaction format, a current VXLAN encapsulation configuration message corresponding to the current VXLAN encapsulation configuration information is generated. This message includes a message type identifying the current VXLAN encapsulation configuration information, an operation identifier code corresponding to the current VXLAN encapsulation configuration information, and the current VXLAN encapsulation configuration information itself. By specifying a peer-link port between the M-LAG member device and the peer device, the current VXLAN encapsulation configuration message is synchronized to the peer device, thus achieving configuration message interaction.

[0041] The current VXLAN encapsulation configuration information is sent to the peer device through the synchronization interface corresponding to the designated M-LAG member interface. Specifically, this includes: when the interface encapsulation configuration type of the M-LAG member interface is the Taged type, dividing the current VXLAN encapsulation configuration information into multiple encapsulation configuration sub-information; generating an encapsulation configuration sub-message corresponding to each encapsulation configuration sub-message according to a preset configuration message interaction format, wherein the encapsulation configuration sub-message includes a last identifier and the encapsulation configuration sub-message, the last identifier being used to identify whether the encapsulation configuration sub-message is the last segment of the multiple encapsulation configuration sub-messages; and synchronizing the current VXLAN encapsulation configuration message to the peer device through the peer-link port between the designated M-LAG member device and the peer device.

[0042] Furthermore, under normal circumstances, information exchange between M-LAG member devices and their peers uses a peer-link, meaning the primary and backup devices exchange information via a peer-link, typically preventing information loss. However, in certain scenarios, the real-time nature of configuration message exchange between the two ends of the M-LAG cannot be guaranteed, such as when the peer-link is disconnected or configuration is performed before the M-LAG is established. To ensure the accuracy of configuration information, the VXLAN encapsulation configuration of the M-LAG device member ports needs to be synchronized. For Untag and Default encapsulation configurations, since the number of configurable encapsulations is less than that of Taged types, the configuration information can be synchronized to the peer at once. However, the Taged type can only support a maximum of 4094 encapsulations; synchronizing too much information at once can cause message channel anomalies.

[0043] In one embodiment of this specification, when the interface encapsulation configuration type of the M-LAG member interface is Taged, and multiple configurations need to be synchronized, the configuration information can be divided into multiple parts, each containing multiple configuration messages. These parts are then sent to the peer device in a step-by-step manner. That is, the current VXLAN encapsulation configuration information is divided into multiple encapsulation configuration sub-messages. Each encapsulation configuration sub-message is processed to generate multiple corresponding encapsulation configuration sub-packets. Each encapsulation configuration sub-packet includes a last-bit identifier and an encapsulation configuration sub-message. It should be noted that the last-bit identifier is used to indicate whether the encapsulation configuration sub-packet is the last sent message among the multiple encapsulation configuration sub-packets, i.e., whether it is the last sent message. For example, when the first encapsulation configuration sub-packet is the last sent message, the last-bit identifier can be set to 1; when the second encapsulation configuration sub-packet is not the last sent message, the last-bit identifier can be set to 0. Other formats are also possible. Through the peer-link port between the designated M-LAG member device and the peer device, all multiple encapsulated configuration sub-messages corresponding to the current VXLAN encapsulated configuration message are synchronized to the peer device. The peer device checks the received information after receiving it. This configuration information is processed incrementally and includes an opcode field: ADD, DELETE, or FLUSH-ALL, also known as an operation identifier code. When configuring VXLAN encapsulation under the M-LAG interface, the opcode indicates whether the configuration is added or deleted. The configuration information is sent to the peer device to ensure the timing of configuration message processing. It should be noted that when notifying the peer device to clear saved configurations, the operation identifier code in the encapsulated configuration information is FLUSH-ALL, such as in scenarios where an M-LAG member interface leaves the M-LAG group or establishes an M-LAG connection, requiring the synchronization of all configuration information to the peer.

[0044] Before performing configuration consistency monitoring of the VXLAN encapsulation configuration of the M-LAG environment based on the peer device and the current VXLAN encapsulation configuration information, the method further includes: obtaining multiple encapsulation configuration sub-messages received by the peer device through the peer-link port between the specified M-LAG member device and the peer device; determining whether the peer device is in a reception completion state based on the last identifier in each encapsulation configuration sub-message; and when the peer device is in the reception completion state, performing configuration consistency monitoring of the VXLAN encapsulation configuration of the M-LAG environment based on the peer device and the current VXLAN encapsulation configuration information.

[0045] In one embodiment of this specification, the peer device needs to perform the check after receiving all configuration messages. By specifying the peer-link port between the M-LAG member device and the peer device, multiple encapsulation configuration sub-messages received by the peer device are obtained. When there is a sub-message with a specified last identifier among the encapsulation configuration sub-messages received by the peer device, it is determined that the peer device is in a reception completion state. Here, the specified last identifier refers to the identifier used to identify the last message sent by the end, such as 1. When the peer device is in this reception completion state, configuration consistency monitoring is performed on the VXLAN encapsulation configuration of the M-LAG environment based on the peer device and the current VXLAN encapsulation configuration information.

[0046] Step S104: Based on the peer device and the current VXLAN encapsulation configuration information, perform configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment.

[0047] Based on the peer device and the current VXLAN encapsulation configuration information, configuration consistency monitoring is performed on the VXLAN encapsulation configuration of the M-LAG environment. Specifically, this includes: obtaining the local VXLAN encapsulation configuration information pre-stored by the peer device, wherein the local VXLAN encapsulation configuration information is the VXLAN encapsulation configuration information of the M-LAG member interfaces of the peer device; comparing the current VXLAN encapsulation configuration information with the local VXLAN encapsulation configuration information to perform configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment.

[0048] In one embodiment of this specification, local VXLAN encapsulation configuration information pre-stored locally by the peer device is obtained. This local VXLAN encapsulation configuration information refers to the VXLAN encapsulation configuration information of the peer device's M-LAG member interfaces. The current VXLAN encapsulation configuration information is compared with the local VXLAN encapsulation configuration information to monitor the consistency of the VXLAN encapsulation configuration in the M-LAG environment.

[0049] The current VXLAN encapsulation configuration information is compared with the local VXLAN encapsulation configuration information. Specifically, the current VXLAN encapsulation configuration information is compared with the local VXLAN encapsulation configuration information. When the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information are inconsistent, the interface status of the M-LAG member interface of the peer device is set to err-disable, that is, the interface status of the corresponding M-LAG member interface of the backup device is set to err-disable.

[0050] In one embodiment of this specification, when the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information are inconsistent, it indicates that the encapsulation configuration of the member interface of the M-LAG member device is inconsistent with the encapsulation configuration of the peer device. In this case, the interface status of the member interface of the peer device is set to err-disable, and a corresponding prompt message is generated. The detailed record of the configuration inconsistency can be queried by command. Here, the detailed record refers to the configuration information corresponding to the two member interfaces respectively.

[0051] When the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information are inconsistent, the VXLAN encapsulation configuration information of the M-LAG member interface of the peer device is configured according to the current VXLAN encapsulation configuration information to generate the current peer VXLAN encapsulation configuration information; the current peer VXLAN encapsulation configuration information of the M-LAG member interface of the peer device is synchronized to the specified M-LAG member device through the synchronization interface; through the specified M-LAG member device, the configuration consistency of the VXLAN encapsulation configuration of the M-LAG environment is monitored according to the current peer VXLAN encapsulation configuration information and the pre-stored specified local VXLAN encapsulation configuration information, wherein the specified local VXLAN encapsulation configuration information is the VXLAN encapsulation configuration information of the M-LAG member interface of the specified M-LAG member device.

[0052] In one embodiment of this specification, when the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information are inconsistent, it is necessary to maintain the consistency of the encapsulation configuration between the M-LAG member interface of the specified M-LAG member device and the member interface of the peer device. Based on the current VXLAN encapsulation configuration information, the VXLAN encapsulation configuration information of the peer device's M-LAG member interface is configured, generating the current peer VXLAN encapsulation configuration information. Through the peer-link port between the specified M-LAG member device and the peer device, the current peer VXLAN encapsulation configuration information of the peer device's M-LAG member interface is synchronized to the specified M-LAG member device. Upon receiving the current peer VXLAN encapsulation configuration information of the peer device's M-LAG member interface, the specified M-LAG member device compares the current peer VXLAN encapsulation configuration information with the pre-stored specified local VXLAN encapsulation configuration information to monitor the consistency of the VXLAN encapsulation configuration in the M-LAG environment. Here, the specified local VXLAN encapsulation configuration information refers to the VXLAN encapsulation configuration information of the specified M-LAG member device's M-LAG member interface. It should be noted that when configuring interface encapsulation configuration information for a specified M-LAG member device, the configured VXLAN encapsulation configuration information of the M-LAG member interface is stored locally on the M-LAG member device.

[0053] Through the designated M-LAG member device, based on the current peer VXLAN encapsulation configuration information and the pre-stored designated local VXLAN encapsulation configuration information, configuration consistency monitoring of the VXLAN encapsulation configuration of the M-LAG environment is performed. Specifically, this includes: comparing the current peer VXLAN encapsulation configuration information and the designated local VXLAN encapsulation configuration information through the designated M-LAG member device; when the current peer VXLAN encapsulation configuration information and the designated local VXLAN encapsulation configuration information are consistent, the interface state of the peer device's M-LAG member interface is changed to UP state.

[0054] In one embodiment of this specification, when the current peer VXLAN encapsulation configuration information and the specified local VXLAN encapsulation configuration information are consistent, the interface state of the peer device's member interface is changed from err-disable state to UP state, so as to UP the M-LAG member port again.

[0055] The above technical solution synchronizes the current VXLAN encapsulation configuration information to the peer device. Based on the peer device and the current VXLAN encapsulation configuration information, in the M-LAG dual-homed access environment, the consistency of the VXLAN encapsulation configuration in the M-LAG environment is monitored and checked, ensuring the consistency of the VXLAN encapsulation configuration at both ends of the M-LAG member port and ensuring traffic forwarding between M-LAG devices.

[0056] Figure 2 A flowchart illustrating another VXLAN encapsulation configuration monitoring method based on an M-LAG environment provided in this specification is shown below. Figure 2As shown, during configuration, the encapsulation type under the interface must first be specified, namely Untag, Taged, or Default. Only one encapsulation can be configured under Untag and Default types, while one or more encapsulations can be configured under Taged type. To ensure configuration awareness between the two devices, the local device checks the existing configuration after configuring the encapsulation information under the interface, and also needs to synchronize a copy with the peer. After receiving the message, the peer checks the configuration to determine whether it is consistent with the local configuration. An encapsulation is configured in member group 1 of the master device. This encapsulation configuration is compared with that of member group 1 of the local storage slave device. Simultaneously, this configuration information is sent to the slave device via peer-link. Since the slave device does not have this encapsulation configured, the comparison result is inconsistent. After receiving this configuration information, the slave device compares it with its local configuration, and the result is also inconsistent. At this point, the slave device sets the M-LAG member port to err-disable and provides corresponding error messages. Details of the configuration inconsistency can be queried via commands. Similarly, the slave device then configures the same encapsulation configuration as the master device in member group 1. This configuration information is also sent to the master device and compared with the encapsulation configuration of member group 1 of the local storage master device. The comparison result is consistent, and the M-LAG member port is re-UP. This paper provides a method for checking the consistency of VXLAN encapsulation configuration of M-LAG member interfaces in a VXLAN network under M-LAG dual-homed access environment. The method automatically checks whether the configuration of M-LAG member interfaces is consistent. If they are inconsistent, the M-LAG member interface of the slave device is err-disabled, and the difference in configuration is prompted through relevant commands. This facilitates troubleshooting, improves user experience, and solves the technical problem that manual checking of a large number of encapsulation configurations is inconvenient and not conducive to troubleshooting abnormal traffic forwarding conditions.

[0057] This specification also provides an embodiment of a VXLAN-encapsulated configuration monitoring device based on an M-LAG environment, such as... Figure 3 As shown, the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0058] Obtain the interface encapsulation configuration type of a specified M-LAG member interface in the pre-built M-LAG environment, where the interface encapsulation configuration type includes: Untag type, Taged type, and Default type; based on the interface encapsulation configuration type of the specified M-LAG member interface, configure one or more current VXLAN encapsulation configuration information for the specified M-LAG member interface; send the current VXLAN encapsulation configuration information to the peer device of the specified M-LAG member device through the synchronization interface corresponding to the specified M-LAG member interface; and perform configuration consistency monitoring of the VXLAN encapsulation configuration of the M-LAG environment according to the peer device and the current VXLAN encapsulation configuration information.

[0059] This specification also provides a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0060] Obtain the interface encapsulation configuration type of a specified M-LAG member interface in the pre-built M-LAG environment, where the interface encapsulation configuration type includes: Untag type, Taged type, and Default type; based on the interface encapsulation configuration type of the specified M-LAG member interface, configure one or more current VXLAN encapsulation configuration information for the specified M-LAG member interface; send the current VXLAN encapsulation configuration information to the peer device of the specified M-LAG member device through the synchronization interface corresponding to the specified M-LAG member interface; and perform configuration consistency monitoring of the VXLAN encapsulation configuration of the M-LAG environment according to the peer device and the current VXLAN encapsulation configuration information.

[0061] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0062] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0063] The devices, media, and methods provided in the embodiments of this specification are one-to-one correspondences. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0064] Those skilled in the art will understand that embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0065] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0066] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0067] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0068] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0069] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0070] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0071] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0072] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A method for monitoring VXLAN encapsulation configuration based on an M-LAG environment, characterized in that, The method includes: Obtain the interface encapsulation configuration type of a specified M-LAG member interface in a pre-built M-LAG environment, wherein the interface encapsulation configuration type includes: Untag type, Taged type, and Default type; Based on the interface encapsulation configuration type of the specified M-LAG member interface, configure one or more current VXLAN encapsulation configuration information for the specified M-LAG member interface; The current VXLAN encapsulation configuration information is sent to the peer device of the specified M-LAG member device through the synchronization interface corresponding to the specified M-LAG member interface; Based on the peer device and the current VXLAN encapsulation configuration information, perform configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment; Based on the peer device and the current VXLAN encapsulation configuration information, configuration consistency monitoring is performed on the VXLAN encapsulation configuration of the M-LAG environment, specifically including: Obtain the local VXLAN encapsulation configuration information pre-stored by the peer device, wherein the local VXLAN encapsulation configuration information is the VXLAN encapsulation configuration information of the M-LAG member interface of the peer device; The current VXLAN encapsulation configuration information is compared with the local VXLAN encapsulation configuration information to monitor the consistency of the VXLAN encapsulation configuration in the M-LAG environment. The comparison between the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information specifically includes: The current VXLAN encapsulation configuration information is compared with the local VXLAN encapsulation configuration information. When the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information are inconsistent, the interface status of the M-LAG member interface of the peer device is set to err-disable. The method further includes: When the current VXLAN encapsulation configuration information and the local VXLAN encapsulation configuration information are inconsistent, the VXLAN encapsulation configuration information is configured on the M-LAG member interface of the peer device according to the current VXLAN encapsulation configuration information, and the current peer VXLAN encapsulation configuration information is generated. The current peer VXLAN encapsulation configuration information of the peer device's M-LAG member interface is synchronized to the designated M-LAG member device through the synchronization interface; Through the designated M-LAG member device, based on the current peer VXLAN encapsulation configuration information and the pre-stored designated local VXLAN encapsulation configuration information, the VXLAN encapsulation configuration of the M-LAG environment is monitored for configuration consistency. The designated local VXLAN encapsulation configuration information is the VXLAN encapsulation configuration information of the M-LAG member interface of the designated M-LAG member device. Through the designated M-LAG member device, based on the current peer VXLAN encapsulation configuration information and the pre-stored designated local VXLAN encapsulation configuration information, configuration consistency monitoring is performed on the VXLAN encapsulation configuration of the M-LAG environment, specifically including: The current peer VXLAN encapsulation configuration information and the specified local VXLAN encapsulation configuration information are compared using the designated M-LAG member device. When the current peer VXLAN encapsulation configuration information and the specified local VXLAN encapsulation configuration information are consistent, the interface state of the M-LAG member interface of the peer device is changed to UP state.

2. The VXLAN encapsulation configuration monitoring method based on an M-LAG environment according to claim 1, characterized in that, The current VXLAN encapsulation configuration information is sent to the peer device through the synchronization interface corresponding to the specified M-LAG member interface, specifically including: According to the preset configuration message interaction format, a current VXLAN encapsulation configuration message corresponding to the current VXLAN encapsulation configuration information is generated. The current VXLAN encapsulation configuration message includes a message type for identifying the current VXLAN encapsulation configuration information, an operation identifier code corresponding to the current VXLAN encapsulation configuration information, and the current VXLAN encapsulation configuration information. The current VXLAN encapsulated configuration message is synchronized to the peer device via the peer-link port between the designated M-LAG member device and the peer device.

3. The VXLAN encapsulation configuration monitoring method based on an M-LAG environment according to claim 1, characterized in that, The current VXLAN encapsulation configuration information is sent to the peer device through the synchronization interface corresponding to the specified M-LAG member interface, specifically including: When the interface encapsulation configuration type of the M-LAG member interface is the Taged type, the current VXLAN encapsulation configuration information is divided into multiple encapsulation configuration sub-messages; According to the preset configuration message interaction format, generate an encapsulated configuration sub-message corresponding to each encapsulated configuration sub-message. The encapsulated configuration sub-message includes a last identifier and the encapsulated configuration sub-message. The last identifier is used to identify whether the encapsulated configuration sub-message is the last segment of a series of encapsulated configuration sub-messages. Through the peer-link port between the designated M-LAG member device and the peer device, multiple encapsulation configuration sub-messages corresponding to the current VXLAN encapsulation configuration message are synchronized to the peer device.

4. The VXLAN encapsulation configuration monitoring method based on an M-LAG environment according to claim 3, characterized in that, Before performing configuration consistency monitoring on the VXLAN encapsulation configuration of the M-LAG environment based on the peer device and the current VXLAN encapsulation configuration information, the method further includes: The multiple encapsulation configuration sub-messages received by the peer device are obtained through the peer-link port between the specified M-LAG member device and the peer device. Based on the last bit identifier in each of the encapsulation configuration sub-messages, determine whether the peer device is in a reception completion state; When the peer device is in the received state, the VXLAN encapsulation configuration of the M-LAG environment is monitored for consistency based on the peer device and the current VXLAN encapsulation configuration information.

5. A VXLAN-encapsulated configuration monitoring device based on an M-LAG environment, characterized in that, The device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method as described in any one of claims 1-4.

6. A non-volatile computer storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are configured to execute the method as described in any one of claims 1-4.

Images