DHCP relay working method and device in MLAG environment and medium

Abstract

The application discloses a DHCP relay working method and device in an MLAG environment and a medium, belongs to the technical field of cross-device link aggregation, and aims to solve the technical problem that a large number of DHCP synchronization messages occupy CPU resources when the existing DHCP response messages are inconsistent on the round trip path. The method comprises the following steps: mounting the first virtual local area network of an MLAG master device and an MLAG backup device in a DHCP relay agent to the same IP address to obtain a third virtual local area network; performing broadcasting processing on a DHCP request message in a DHCP client in relation to the MLAG master device and the MLAG backup device to determine a DHCP relay agent IP address; and sending a DHCP response message to the DHCP client based on the DHCP relay agent IP address.

Description

Technical Field

[0001] This application relates to the field of cross-device link aggregation technology, and in particular to a DHCP relay working method, device and medium in an MLAG environment. Background Technology

[0002] Traditional data center networks employ device and link redundancy to ensure high reliability. However, due to their low link utilization and high network maintenance costs, data center switches have introduced stacking technology, which virtualizes multiple switches into a single switch, thereby simplifying network deployment and reducing network maintenance.

[0003] To meet the demands of increasing traffic and higher network reliability, MLAG virtualization technology emerged, which improves link reliability from the board level to the device level through link aggregation among multiple devices.

[0004] DHCP is a technology used to centrally manage and dynamically configure user IP addresses. When the client and the DHCP server are not on the same network segment, a DHCP Relay can be configured on the interface of a relay device to act as a relay agent. In this way, DHCP requests sent from the client can be forwarded to the DHCP server across the network segment via the DHCP relay. After receiving the message, the DHCP server will assign an IP address to the client.

[0005] Whether in data centers or campus networks, the application of MLAG combined with DHCP is indispensable in practical use. In most scenarios, MLAG systems do not simply serve Layer 2 networks; clients and DHCP servers are usually not in the same broadcast domain, which makes DHCP Relay essential.

[0006] Logically, a stacked device is a single device; both the control plane and forwarding plane can be considered as one device, resulting in a simple network structure and easier processing of DHCP relay messages. An MLAG device, however, is logically two devices, with a more complex network structure. In this case, DHCP message forwarding may result in inconsistent round-trip paths, causing DHCP server response messages sent to the DHCP relay to be discarded because the Relay Agent IP Address field does not contain the local interface address, preventing the DHCP client from obtaining an IP address.

[0007] Existing solutions increase the difficulty of code development and maintenance. A large number of DHCP synchronization messages consume CPU resources and may also cause peer-link port congestion, leading to MLAG system malfunctions. The purpose of this application is to allow the MLAG system to directly process DHCP response messages received by relay devices without synchronizing DHCP messages when encountering inconsistent return paths. Summary of the Invention

[0008] This application provides a DHCP relay working method, device and medium in an MLAG environment to solve the following technical problems: When the existing DHCP response messages have inconsistent round-trip paths, a large number of DHCP synchronization messages will occupy CPU resources and may also cause peer-link port blockage, leading to MLAG system abnormalities.

[0009] The embodiments of this application adopt the following technical solutions:

[0010] On one hand, this application provides a DHCP relay operation method in an MLAG environment, including: based on an MLAG system interconnected by peer-link, and through a virtual local area network (VLAN), configuring a DHCP server, a DHCP relay agent, and a DHCP client to be associated; wherein, the VLAN includes: a first VLAN and a second VLAN; configuring the first VLANs of the MLAG master device and the MLAG backup device in the DHCP relay agent to have the same IP address to obtain a third VLAN; through the third VLAN, broadcasting the DHCP request message in the DHCP client to the MLAG master device and the MLAG backup device to determine the DHCP relay agent IP address; through the DHCP server, and based on the DHCP relay agent IP address, sending a DHCP response message to the DHCP client to complete the allocation of IP address parameters in the DHCP client.

[0011] This embodiment of the application eliminates the need for MLAG relay devices to synchronize DHCP messages, allowing both primary and backup MLAG devices to process DHCP relay messages simultaneously. This reduces the CPU load on the MLAG devices, accelerates DHCP message forwarding efficiency, and improves network flexibility and stability. In other words, DHCP relay devices in an Mlag environment can process DHCP relay messages normally without needing to synchronize them with each other, thus improving DHCP message forwarding efficiency and enhancing network flexibility and stability.

[0012] In one feasible implementation, an MLAG system based on peer-link interconnection is configured to associate a DHCP server, a DHCP relay agent, and a DHCP client via a virtual local area network (VLAN). Specifically, this includes: interconnecting a first network device with a second network device using peer-link technology to establish the MLAG system; aggregating both the MLAG master device and the MLAG backup device with DHCP clients via cross-device links within the MLAG system, and aggregating both the MLAG master device and the MLAG backup device with the DHCP server; designating the first VLAN created by the MLAG master device and the MLAG backup device as the gateway for the DHCP client, and enabling the DHCP relay agent; and associating the second VLAN created by the MLAG master device and the MLAG backup device with the DHCP server.

[0013] In one feasible implementation, the first virtual local area networks (VLANs) of the MLAG master device and the MLAG backup device in the DHCP relay agent are configured to attach the same IP address to obtain a third VLAN. Specifically, this includes: performing configuration generation processing on the first VLANs of the MLAG master device and the MLAG backup device regarding the same IP address under the DHCP relay agent, and additionally attaching the same IP address to the first VLAN; and generating the third VLAN based on the same IP address attached to the first VLAN.

[0014] In one feasible implementation, before determining the DHCP relay agent IP address by broadcasting the DHCP request message in the DHCP client to the MLAG master device and the MLAG backup device via the third virtual local area network, the method further includes: randomly selecting an uplink aggregation port for the DHCP request message and sending it to the MLAG master device or the MLAG backup device via the DHCP client; and temporarily storing the DHCP request message in the MLAG master device or the MLAG backup device.

[0015] In one feasible implementation, the DHCP request message in the DHCP client is broadcast to the MLAG master device and the MLAG backup device via the third virtual local area network (VLAN) to determine the DHCP relay agent IP address. Specifically, this includes: encapsulating and identifying fields in the DHCP request message in the MLAG master device or the MLAG backup device via the third VLAN to obtain an encapsulated identification request message; and broadcasting the encapsulated identification request message to the DHCP server via the second VLAN to obtain the DHCP relay agent IP address of the encapsulated identification request message.

[0016] In one feasible implementation, before sending a DHCP response message to the DHCP client via the DHCP server and based on the DHCP relay agent IP address to complete the IP address parameter allocation process in the DHCP client, the method further includes: performing IP address parameter allocation processing on the DHCP request message via the DHCP server and based on the DHCP relay agent IP address to generate the DHCP response message; and sending the DHCP response message to the MLAG master device or the MLAG backup device via the second virtual LAN.

[0017] In one feasible implementation, the DHCP server sends a DHCP response message to the DHCP client based on the DHCP relay agent IP address. Specifically, this includes: the MLAG master device or the MLAG backup device performs field identification processing on the received DHCP response message based on the DHCP relay agent IP address, and identifies the downstream aggregated virtual LAN as the third virtual LAN; based on the third virtual LAN, the DHCP response message from the MLAG master device or the MLAG backup device is sent to the DHCP client to complete the IP address parameter allocation processing in the DHCP client.

[0018] In one feasible implementation, DHCP relay gateway technology is used to automatically switch the first virtual LAN and the third virtual LAN in the DHCP relay agent, so that both the MLAG master device and the MLAG backup device can normally reply to and process the DHCP request message.

[0019] Secondly, embodiments of this application also provide a DHCP relay working device in an MLAG environment, the device comprising: 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 to enable the at least one processor to execute a DHCP relay working method in an MLAG environment as described in any of the above embodiments.

[0020] Thirdly, embodiments of this application also provide a non-volatile computer storage medium, characterized in that the storage medium is a non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium stores at least one program, each program including instructions, and when the instructions are executed by a terminal, the terminal executes a DHCP relay working method in an MLAG environment as described in any of the above embodiments.

[0021] This application provides a DHCP relay working method, device, and medium in an MLAG environment. Compared with the prior art, this application has the following beneficial technical effects:

[0022] This embodiment of the application eliminates the need for MLAG relay devices to synchronize DHCP messages, allowing both primary and backup MLAG devices to process DHCP relay messages simultaneously. This reduces the CPU load on the MLAG devices, accelerates DHCP message forwarding efficiency, and improves network flexibility and stability. In other words, DHCP relay devices in an Mlag environment can process DHCP relay messages normally without needing to synchronize them with each other, thus improving DHCP message forwarding efficiency and enhancing network flexibility and stability. Attached Figure Description

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

[0024] Figure 1 A flowchart illustrating a DHCP relay operation method in an MLAG environment is provided as an embodiment of this application.

[0025] Figure 2 A schematic diagram of an MLAG system structure is provided for an embodiment of this application;

[0026] Figure 3 This is a schematic diagram of the structure of a DHCP relay device in an MLAG environment, provided as an embodiment of this application. Detailed Implementation

[0027] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, 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 application.

[0028] It should be noted that the existing solutions increase the difficulty of code development and maintenance. A large number of DHCP synchronization messages consume CPU resources and may also cause peer-link port congestion, leading to MLAG system malfunctions. The purpose of this invention is to allow the MLAG system to directly process the received DHCP response messages without synchronizing DHCP messages when encountering inconsistent round-trip paths.

[0029] This application provides a method for DHCP relay operation in an MLAG environment, such as... Figure 1 As shown, the DHCP relay operation method in the MLAG environment specifically includes steps S101-S104:

[0030] S101. An MLAG system based on peer-link interconnection, which associates and configures the DHCP server, DHCP relay agent, and DHCP client through a virtual local area network (VLAN). The VLAN includes a first VLAN and a second VLAN.

[0031] Specifically, the first network device and the second network device are interconnected through peer-link technology to establish an MLAG system.

[0032] Furthermore, through the cross-device link in the MLAG system, both the MLAG master device and the MLAG backup device are aggregated and connected to the DHCP client in the downlink, and both the MLAG master device and the MLAG backup device are aggregated and connected to the DHCP server in the uplink.

[0033] Furthermore, by connecting the MLAG master device and the MLAG backup device, the first virtual LAN created is designated as the gateway for the DHCP client, and the DHCP relay agent is enabled.

[0034] Furthermore, by associating the created second virtual LAN with the DHCP server through the MLAG master device and the MLAG backup device.

[0035] In one embodiment, Figure 2 This application provides a schematic diagram of an MLAG system structure, as shown in the embodiment. Figure 2 As shown, two network devices are interconnected via a peer-link to establish an MLAG system. The primary and backup MLAG devices connect to DHCP clients downstream via cross-device link aggregation, and also connect to the DHCP server upstream via cross-device link aggregation. The primary and backup MLAG devices create VLANIF10 (the first virtual LAN) as the gateway for DHCP clients and enable DHCP relay. The primary and backup MLAG devices create VLANIF20 (the second virtual LAN) and connect to the DHCP server.

[0036] S102. Configure the first virtual LAN of the MLAG master device and the MLAG backup device in the DHCP relay agent to have the same IP address to obtain the third virtual LAN.

[0037] Specifically, the first virtual local area network (VLAN) of the MLAG master device and the MLAG backup device is configured to have the same IP address under the DHCP relay agent, and the same IP address is additionally attached to the first VLAN. Based on the same IP address attached to the first VLAN, a third VLAN is generated.

[0038] It should be noted that because the DHCP server is connected to the MLAG relay device via an aggregated link, the packet hash may result in two scenarios:

[0039] Scenario 1: The DHCP reply message is sent back to the MLAG master device. The DHCP relay can process this message normally because the Relay Agent IP Address field is the address of the local interface VLAN 10 (Virtual Local Area Network), which is 10.1.1.1.

[0040] Scenario 2: The DHCP reply packet is sent to the MLAG backup device. The DHCP relay will discard this reply packet because the RelayAgent IP Address field is not the address of the local interface VLAN 10, 10.1.1.2, but 10.1.1.1. This will cause the DHCP client to be unable to obtain an IP address.

[0041] In one embodiment, the same DHCP relay IP is specified on the VLAN 10 interface of the primary and backup mlag devices, such as configuring DHCP relay gateway 10.1.1.254 (third VLAN).

[0042] S103. Through the third virtual LAN, the DHCP request message in the DHCP client is broadcast to the relevant MLAG master and MLAG backup devices to determine the DHCP relay agent IP address.

[0043] Specifically, the DHCP client randomly selects the uplink aggregation port for the DHCP request message and sends it to either the MLAG master or the MLAG backup device. The DHCP request message is then temporarily stored in either the MLAG master or the MLAG backup device.

[0044] Furthermore, through a third virtual LAN, the DHCP request messages in the MLAG master device or MLAG backup device are encapsulated and identified to obtain encapsulated and identified request messages.

[0045] Furthermore, the Encapsulation Identification Request message is broadcast to the DHCP server via the second virtual LAN, and the DHCP relay agent IP address of the Encapsulation Identification Request message is obtained.

[0046] In one embodiment, such as Figure 2 As shown, the DHCP client sends a DHCP request message to the server. Because the uplink of the DHCP client is an aggregated port, the message may be sent randomly to the selected link. If the DHCP request message is sent to the MLAG master device (DHCP relay VLAN 10-10.1.1.1), the master device receives the message, processes it appropriately, and then sends it in unicast to the designated DHCP server located in another network segment (VLAN 20-20.1.1.10). In this case, the Relay Agent IP Address field of the request message is filled with 10.1.1.1. Then, the DHCP relay agent encapsulates the DHCP request with the Relay Agent IP Address field of (third VLAN) 10.1.1.254 and sends it to the DHCP server. The DHCP server's reply DHCP response message can be processed normally by any DHCP relay, regardless of which DHCP relay it is sent to.

[0047] S104. Send the DHCP response message to the DHCP client through the DHCP server and based on the DHCP relay agent IP address.

[0048] Specifically, the DHCP server, based on the IP address of the DHCP relay agent, performs IP address parameter allocation processing on the DHCP request message and generates a DHCP response message.

[0049] Furthermore, the DHCP response message is sent to the MLAG master device or the MLAG backup device via the second virtual LAN.

[0050] Furthermore, the received DHCP response messages are processed by the MLAG master device or the MLAG backup device, which identifies the field identifier based on the DHCP relay agent IP address, and the VLANs aggregated by the downstream chain are identified as the third VLANs.

[0051] Furthermore, based on a third virtual LAN, the DHCP response message from the MLAG master device or the MLAG backup device is sent to the DHCP client to complete the allocation of IP address parameters in the DHCP client.

[0052] In one embodiment, such as Figure 2 As shown, the DHCP server assigns IP addresses and other parameters to the DHCP client based on the Relay Agent IP Address field (10.1.1.1), and sends the DHCP reply message to the DHCP relay agent identified by the Relay Agent IP Address field. Finally, it can also send the DHCP reply message from the MLAG master or MLAG backup device to the DHCP client based on a third virtual LAN.

[0053] In addition, embodiments of this application also provide a DHCP relay device in an MLAG environment, such as... Figure 3 As shown, the DHCP relay working device 300 in the MLAG environment specifically includes:

[0054] At least one processor 301. And a memory 302 communicatively connected to the at least one processor 301. The memory 302 stores instructions executable by the at least one processor 301, enabling the at least one processor 301 to execute:

[0055] The MLAG system is based on peer-link interconnection and uses virtual local area networks (VLANs) to associate and configure DHCP servers, DHCP relay agents, and DHCP clients. The VLANs include a first VLAN and a second VLAN.

[0056] Configure the first virtual LAN of the MLAG master device and the MLAG backup device in the DHCP relay agent to have the same IP address to obtain the third virtual LAN;

[0057] Through a third virtual LAN, the DHCP request messages in the DHCP client are broadcast to the MLAG master and MLAG backup devices to determine the DHCP relay agent IP address.

[0058] The DHCP server sends DHCP response messages to the DHCP client based on the DHCP relay agent's IP address to complete the IP address parameter allocation process in the DHCP client.

[0059] This embodiment of the application eliminates the need for MLAG relay devices to synchronize DHCP messages, allowing both primary and backup MLAG devices to process DHCP relay messages simultaneously. This reduces the CPU load on the MLAG devices, accelerates DHCP message forwarding efficiency, and improves network flexibility and stability. In other words, DHCP relay devices in an Mlag environment can process DHCP relay messages normally without needing to synchronize them with each other, thus improving DHCP message forwarding efficiency and enhancing network flexibility and stability.

[0060] The various embodiments in this application 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 for 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.

[0061] The devices and media provided in this application are one-to-one with the methods. 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.

[0062] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can 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.

[0063] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. 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, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0064] 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.

[0065] 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 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.

[0066] The foregoing has described specific embodiments of this application. 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 results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0067] The above description is merely an embodiment of this application and is not intended to limit this application. For those skilled in the art, various modifications and variations can be made to the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the embodiments of this application should be included within the scope of the claims of this application.

Claims

1. A DHCP relay operation method in an MLAG environment, characterized in that, The method includes: The MLAG system is based on peer-link interconnection and uses a virtual local area network (VLAN) to associate and configure the DHCP server, DHCP relay agent, and DHCP client; wherein the VLAN includes a first VLAN and a second VLAN. The first virtual LAN of the MLAG master device and the MLAG backup device in the DHCP relay agent are configured to have the same IP address to obtain the third virtual LAN. Through the third virtual local area network, the DHCP request message in the DHCP client is broadcast to the MLAG master device and the MLAG backup device to determine the DHCP relay agent IP address; The DHCP server sends a DHCP response message to the DHCP client based on the DHCP relay agent's IP address to complete the IP address parameter allocation process in the DHCP client.

2. The DHCP relay operation method in an MLAG environment according to claim 1, characterized in that, The MLAG system is based on peer-link interconnection and uses a virtual LAN to configure and associate the DHCP server, DHCP relay agent, and DHCP client. Specifically, this includes: The MLAG system is established by interconnecting the first network device and the second network device using peer-link technology. Through the cross-device link in the MLAG system, both the MLAG master device and the MLAG backup device are aggregated and connected to the DHCP client in the downlink, and both the MLAG master device and the MLAG backup device are aggregated and connected to the DHCP server in the uplink. By connecting the MLAG master device and the MLAG backup device, the first virtual LAN created is determined as the gateway of the DHCP client, and the DHCP relay agent is enabled. The second virtual local area network (VLAN) created is associated with the DHCP server by connecting the MLAG master device and the MLAG backup device.

3. The DHCP relay operation method in an MLAG environment according to claim 1, characterized in that, The third virtual local area network (VLAN) is obtained by mounting the first VLAN of the MLAG master device and the MLAG backup device in the DHCP relay agent with the same IP address, specifically including: Configure and generate the same IP address under DHCP relay agent for the first virtual local area network of the MLAG master device and the MLAG backup device, and additionally attach the same IP address to the first virtual local area network. A third virtual local area network is generated based on the same IP address mounted under the first virtual local area network.

4. The DHCP relay operation method in an MLAG environment according to claim 1, characterized in that, Before determining the DHCP relay agent IP address by broadcasting the DHCP request message in the DHCP client to the MLAG master device and the MLAG backup device via the third virtual local area network, the method further includes: The DHCP client randomly selects the uplink aggregation port for the DHCP request message and sends it to the MLAG master device or the MLAG backup device. The DHCP request message is temporarily stored in the MLAG master device or the MLAG backup device.

5. The DHCP relay operation method in an MLAG environment according to claim 1, characterized in that, Through the third virtual local area network, the DHCP request messages in the DHCP client are broadcast to the MLAG master device and the MLAG backup device to determine the DHCP relay agent IP address, specifically including: Through the third virtual local area network, the DHCP request message in the MLAG master device or the MLAG backup device is encapsulated and identified to obtain an encapsulated and identified request message. The Encapsulation Identifier Request message is broadcast to the DHCP server via the second virtual LAN, and the DHCP relay agent IP address of the Encapsulation Identifier Request message is obtained.

6. The DHCP relay operation method in an MLAG environment according to claim 1, characterized in that, Before sending a DHCP response message to the DHCP client via the DHCP server and based on the DHCP relay agent's IP address to complete the IP address parameter allocation process in the DHCP client, the method further includes: The DHCP server, based on the DHCP relay agent IP address, performs IP address parameter allocation processing on the DHCP request message and generates the DHCP response message. The DHCP response message is sent to the MLAG master device or the MLAG backup device via the second virtual local area network.

7. The DHCP relay operation method in an MLAG environment according to claim 1, characterized in that, The DHCP server, based on the DHCP relay agent's IP address, sends a DHCP response message to the DHCP client, specifically including: The MLAG master device or the MLAG backup device performs field identification processing on the received DHCP response message based on the DHCP relay agent IP address, and determines the virtual LAN aggregated by the downstream chain as the third virtual LAN. Based on the third virtual local area network, the DHCP response message in the MLAG master device or the MLAG backup device is sent to the DHCP client to complete the IP address parameter allocation process in the DHCP client.

8. The DHCP relay operation method in an MLAG environment according to claim 1, characterized in that, The DHCP relay gateway technology is used to automatically switch the relay gateway between the first VLAN and the third VLAN in the DHCP relay agent, so that both the MLAG master device and the MLAG backup device can normally respond to and process the DHCP request message.

9. A DHCP relay device in an MLAG 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 executable by the at least one processor to enable the at least one processor to perform a DHCP relay operation method in an MLAG environment according to any one of claims 1-8.

10. A non-volatile computer storage medium, characterized in that, The storage medium is a non-volatile computer-readable storage medium that stores at least one program, each program including instructions that, when executed by a terminal, cause the terminal to perform a DHCP relay operation method in an MLAG environment according to any one of claims 1-8.

Images