A method, device, and medium for configuring DHCP in an SDN-based MLAG network.

Abstract

This application discloses a method, device, and medium for configuring DHCP in an SDN-based MLAG network, belonging to the technical field of MLAG network configuration. The method includes: configuring DHCP for member switches in the MLAG network based on a DHCP front-end and receiving DHCP logs from the member switches; real-time monitoring of member switches to obtain their status and device information; when a member switch is in an abnormal state, deleting its DHCP and determining whether its memory usage is below a preset threshold; if memory usage is less than or equal to the preset threshold, retrieving the abnormal device's DHCP configuration from the SDN database and sending the DHCP configuration to idle devices; and handling the abnormal state of the abnormal device using a preset exception handling algorithm to repair the abnormal device. This application, through the above method, can prevent address changes caused by client lease renewals when a single device fails or interface fluctuations occur.

Description

Technical Field

[0001] This application relates to the technical field of MLAG networking configuration, and in particular to a method, device and medium for configuring DHCP in MLAG networking based on SDN. Background Technology

[0002] MLAG (Multi-Chassis Link Aggregation) is a technology used to improve network redundancy and load balancing, commonly used in data centers and enterprise networks. DHCP (Dynamic Host Configuration Protocol) is used to automatically assign IP addresses to devices on the network. SDN (Software Defined Networking) is a network architecture that abstracts network control functions from hardware devices, implementing network configuration and management through software.

[0003] In existing technologies, for example, patent CN116192801A proposes a method for synchronizing DHCP entries in a shared address segment, which solves the problem of DHCP entry synchronization in a shared network segment. However, when a single MLAG member device fails, the private DHCP network segment service undertaken by the failed device will be interrupted, and other member devices cannot take over. Furthermore, there is a lack of coping methods when the interface of a single device repeatedly oscillates, and the DHCP service may not be able to be provided normally after the fault is recovered.

[0004] Therefore, the existing technology has the following problems:

[0005] 1. In an MLAG network, the primary and backup devices cannot provide DHCP services for the same address range;

[0006] 2. When a single device fails or the interface fluctuates, address changes caused by client lease renewals cannot be guaranteed. Summary of the Invention

[0007] This application provides a method, device, and medium for configuring DHCP in an SDN-based MLAG network to solve the following technical problems: how to provide DHCP services for the same address range for primary and backup devices in an MLAG network, and how to ensure that address changes caused by client lease renewals are prevented when a single device fails or the interface oscillates.

[0008] In a first aspect, embodiments of this application provide a method for configuring DHCP in an SDN-based MLAG network. The method is characterized by being applied to an MLAG network service system, which includes an SDN control module and an MLAG network module. The SDN control module includes an SDN front-end, an SDN controller, and an SDN database. The MLAG network module includes multiple member switch devices and a DHCP front-end. The method includes: configuring DHCP for member switch devices under the MLAG network based on the DHCP front-end, and receiving DHCP logs from the member switch devices; monitoring member switch devices in real time to obtain their status and device information; wherein the status includes normal status and abnormal status, and abnormal status includes DHCP configuration errors, IP allocation errors, and interface status abnormalities; when a member switch device is in an abnormal status, deleting the DHCP of the abnormal device and determining whether the memory usage of the abnormal device is lower than a preset usage threshold; wherein the abnormal device is the member switch device causing the abnormal status; if the memory usage is less than or equal to the preset usage threshold, retrieving the DHCP configuration of the abnormal device from the SDN database and sending the DHCP configuration to idle devices; and processing the abnormal status of the abnormal device based on a preset abnormality handling algorithm to repair the abnormal device.

[0009] In one implementation of this application, the DHCP configuration of member switch devices under the MLAG network is based on the DHCP front-end, and the DHCP logs of the member switch devices are received. Specifically, this includes: setting DHCP parameters for member switch devices under the MLAG network through the DHCP front-end interface; wherein the DHCP parameters include IP address and lease time; receiving and storing DHCP logs sent by member switch devices; wherein the DHCP logs include DHCP requests and DHCP responses.

[0010] In one implementation of this application, when a member switch device is in an abnormal state, the DHCP server of the abnormal device is deleted, and the memory usage of the abnormal device is determined to be lower than a preset threshold. Specifically, this includes: when an abnormal state of a member switch device is detected, marking the member switch device as an abnormal device and stopping the DHCP service of the member switch device; querying the memory usage of the abnormal device; and comparing the memory usage with the preset threshold to determine whether the abnormal device can continue to operate.

[0011] In one implementation of this application, member switch devices are monitored in real time to obtain their status and device information. Specifically, this includes: periodically sending status query requests to member switch devices to obtain their operating status, interface status, and DHCP configuration information; processing the operating status, interface status, and DHCP configuration information based on a preset status analysis model to determine whether the member switch devices are in a normal state and to determine their status and device information.

[0012] In one implementation of this application, when a member switch device is in an abnormal state, the DHCP of the abnormal device is deleted, and after determining whether the memory usage of the abnormal device is lower than a preset usage threshold, the method further includes: if the memory usage is higher than the preset usage threshold, no DHCP configuration is performed on the abnormal device.

[0013] In one implementation of this application, the lease and abnormal state of the abnormal device are processed based on a preset exception handling algorithm to repair the abnormal device. Specifically, this includes: comparing the type and abnormal state of the abnormal device with preset exception handling strategies to select an appropriate exception handling strategy; executing the exception handling strategy and monitoring the status of the device and the DHCP configuration; and notifying preset maintenance personnel when a preset maintenance threshold is reached.

[0014] In one implementation of this application, the method further includes: determining whether the abnormal device is in a preset idle time period based on the lease information; if so, modifying the lease time of the abnormal device to the idle time period; if not, recording the lease time of the abnormal device as indefinite; waiting for a preset administrator to restore the device status of the abnormal device; when the device status is normal, restoring the DHCP configuration of the abnormal device and recording that the lease of the abnormal device has expired.

[0015] In one implementation of this application, the method further includes: querying lease information of member switch devices according to DHCP logs; wherein the lease information includes lease start time, end time, and renewal status; when a lease of a member switch device has expired, querying the renewal status of the corresponding member switch device; when renewing, refreshing the lease of the member switch device that has expired; when not renewing, deleting the IP record and static IP configuration of the member switch device.

[0016] Secondly, embodiments of this application also provide a device for configuring DHCP in an SDN-based MLAG network, 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, the instructions being executed by the at least one processor to enable the at least one processor to: configure DHCP for member switch devices under the MLAG network based on the DHCP front-end, and receive DHCP logs from the member switch devices; monitor member switch devices in real time to obtain the status and device information of the member switch devices; wherein the status includes normal status and abnormal status, and abnormal status includes DHCP configuration error, IP allocation error, and interface status abnormality; when the status of a member switch device is abnormal, delete the DHCP of the abnormal device, and determine whether the memory usage status of the abnormal device is lower than a preset usage threshold; wherein the abnormal device is the member switch device that caused the abnormal status; if the memory usage status is higher than the preset usage threshold, do not configure DHCP for the abnormal device; if the memory usage status is less than or equal to the preset usage threshold, retrieve the DHCP configuration of the abnormal device based on the SDN database, and send the DHCP configuration to an idle device; process the abnormal status of the abnormal device based on a preset abnormality handling algorithm to repair the abnormal device.

[0017] Thirdly, this application also provides a non-volatile computer storage medium for configuring DHCP in an SDN-based MLAG network, storing computer-executable instructions. The computer-executable instructions are characterized by: configuring DHCP for member switches in the MLAG network based on the DHCP front-end and receiving DHCP logs from the member switches; monitoring member switches in real time to obtain their status and device information; wherein the status includes normal and abnormal states, and abnormal states include DHCP configuration errors, IP allocation errors, and abnormal interface status; when a member switch is in an abnormal state, deleting the DHCP of the abnormal device and determining whether the memory usage of the abnormal device is below a preset threshold; wherein the abnormal device is the member switch that caused the abnormal state; if the memory usage is above the preset threshold, not configuring DHCP on the abnormal device; if the memory usage is less than or equal to the preset threshold, retrieving the DHCP configuration of the abnormal device from the SDN database and sending the DHCP configuration to idle devices; and processing the lease and abnormal state of the abnormal device based on a preset anomaly handling algorithm to repair the abnormal state of the abnormal device.

[0018] The method, device, and medium for configuring DHCP in an SDN-based MLAG network provided in this application embodiment have at least the following technical effects:

[0019] Improved DHCP configuration flexibility and efficiency: Through the DHCP front-end interface, administrators can easily configure the DHCP parameters of member switches in an MLAG network. This simplifies the operation process, improves configuration efficiency, and reduces the risk of configuration errors.

[0020] Real-time device monitoring: Enables real-time monitoring of member switch device status and information, including normal and various abnormal states (such as DHCP configuration errors, IP allocation errors, and abnormal interface status). It allows for timely detection and handling of potential problems, thereby ensuring network stability and availability to a certain extent.

[0021] Intelligent Anomaly Handling: When a member switch experiences an anomaly, the system can intelligently delete the DHCP configuration of the malfunctioning device and determine whether to reconfigure DHCP based on memory usage. This helps avoid resource waste to some extent and ensures normal network operation. Furthermore, by processing the leases and abnormal states of malfunctioning devices through anomaly handling algorithms, it facilitates the rapid restoration of normal device operation.

[0022] Improve network resource utilization: When the memory usage of an abnormal device is determined to be below a preset threshold, the system can retrieve the original DHCP configuration from the SDN database and send it to an idle device. This achieves efficient resource utilization and reduces resource waste caused by device failure. Attached Figure Description

[0023] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0024] Figure 1 A schematic diagram of a system for configuring DHCP in an SDN-based MLAG network is provided in this embodiment of the application.

[0025] Figure 2 A flowchart illustrating a method for configuring DHCP in an SDN-based MLAG network, as provided in this application embodiment;

[0026] Figure 3 This is a schematic diagram of the internal structure of a device for configuring DHCP in an SDN-based MLAG network, as provided in an embodiment of this application. Detailed Implementation

[0027] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0028] This application provides a method, device, and medium for configuring DHCP in an SDN-based MLAG network to solve the following technical problems: how to provide DHCP services for the same address range for primary and backup devices in an MLAG network, and how to ensure that address changes caused by client lease renewals are prevented when a single device fails or the interface fluctuates.

[0029] The technical solutions proposed in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0030] like Figure 1 As shown, the MLAG networking service system includes: an SDN control module and an MLAG networking module; the SDN control module includes an SDN front-end, an SDN controller, and an SDN database; the MLAG networking module includes multiple member switch devices and a DHCP front-end.

[0031] The SDN controller and member switches in the MLAG network can communicate with each other via the management network, allowing the controller to manage all member switches. The SDN controller can monitor the managed member switches in real time using protocols such as SNMP and SYLOG, and can also perform configuration and distribution operations on member switches via remote login protocols such as SSH and TELNET. The SDN controller can provide a web page for configuring relevant DHCP services and recording and storing related data.

[0032] Figure 2 This document provides a flowchart for configuring DHCP in an SDN-based MLAG network, as illustrated in an embodiment of this application. Figure 2 As shown in the figure, the method for configuring DHCP in an SDN-based MLAG network according to an embodiment of this application specifically includes the following steps:

[0033] Step 1: Configure DHCP on member switch devices in the MLAG network based on the DHCP front-end, and receive DHCP logs from member switch devices.

[0034] First, configure DHCP parameters for member switch devices in the MLAG network through the DHCP front-end interface; the DHCP parameters include IP address and lease time.

[0035] The administrator logs into the DHCP front-end interface. This interface provides a page for configuring and managing the DHCP settings of member switches in the MLAG network.

[0036] In the DHCP front-end interface, administrators can configure DHCP parameters for each member switch device in an MLAG network. These parameters mainly include the IP address range and lease time. The IP address range defines the range of IP addresses that the device can be assigned, while the lease time specifies the validity period of the assigned IP address.

[0037] Furthermore, it receives and stores DHCP logs sent by member switch devices; wherein, the DHCP logs include DHCP requests and DHCP responses.

[0038] After configuring the DHCP parameters, member switch devices will provide DHCP services and log relevant DHCP information. These logs contain detailed information about the device's handling of DHCP requests and responses, such as the time of the request, the requested IP address, and the result of the response.

[0039] Member switch devices send the generated DHCP logs back to the DHCP frontend for centralized storage and analysis. Upon receiving these logs, the DHCP frontend saves them in a designated storage location for later querying and analysis.

[0040] By receiving and storing DHCP logs, administrators can easily track and monitor the operational status of the DHCP service in the network, and promptly identify and address potential problems. At the same time, DHCP logs also provide crucial data support for network troubleshooting and performance optimization.

[0041] Step 2: Monitor member switch devices in real time to obtain the status and device information of member switch devices; the status includes normal status and abnormal status, and abnormal status includes DHCP configuration error, IP allocation error, and interface status abnormality.

[0042] First, periodically send status query requests to member switch devices to obtain the operating status, interface status, and DHCP configuration information of the member switch devices.

[0043] To monitor the status of member switch devices in real time, the system periodically (e.g., every half hour) sends status query requests to each member switch device. These requests aim to obtain the device's operating status, interface status, and DHCP configuration information.

[0044] The operational status reflects the overall working condition of the device, such as whether it is operating normally or whether there are any faults. Interface status provides the connection status of each network interface of the device, including whether it is connected, connection speed, and data transmission volume. DHCP configuration information displays the device's DHCP service settings and currently assigned IP addresses.

[0045] Furthermore, based on a preset state analysis model, the system processes the operating status, interface status, and DHCP configuration information to determine whether the member switch devices are in a normal state and to determine the status and device information of the member switch devices.

[0046] Once a response is received from a member switch device, the system processes this status information based on a pre-defined status analysis model. This status analysis model may contain a series of rules and algorithms that evaluate various status indicators of the device based on historical data.

[0047] Determine if the device is in normal working order based on its operating status. If the device reports a fault or anomaly, it is marked as abnormal. Check the interface status to confirm that all network interfaces are functioning correctly. If an interface is disconnected, slow, or has other problems, the device will also be considered abnormal. Analyze the DHCP configuration information to check for DHCP configuration errors or IP address allocation errors. For example, if the DHCP service is not started correctly, the IP address pool is set incorrectly, or there is an IP address conflict, it will be considered as abnormal.

[0048] Step 3: When a member switch device is in an abnormal state, delete the DHCP server of the abnormal device and determine whether the memory usage of the abnormal device is lower than the preset threshold. The abnormal device is the member switch device that caused the abnormal state.

[0049] First, when an abnormal status is detected in a member switch device, the member switch device is marked as an abnormal device, and the DHCP service of the member switch device is stopped.

[0050] When real-time monitoring detects that a member switch is in an abnormal state (such as DHCP configuration errors, IP address allocation errors, or abnormal interface status), the device is marked as an abnormal device. To prevent the abnormal device from further impacting the network, its DHCP service is stopped. Stopping the DHCP service ensures that the device will not continue to assign incorrect IP addresses or propagate incorrect configuration information.

[0051] Further, check the memory usage of the abnormal device.

[0052] After stopping the DHCP service, check the memory usage of the abnormal device. This step is understandably to assess the device's performance and resource availability; memory usage reflects the device's load and operating efficiency, and is a crucial indicator of whether the device can continue to handle tasks.

[0053] Furthermore, the memory usage is compared with a preset usage threshold to determine whether the abnormal device can continue to operate.

[0054] The queried memory usage is compared with the preset usage threshold. The preset usage threshold is set based on factors such as the device's hardware configuration, performance requirements, and network environment, and is used to determine whether the device has sufficient resources to continue running or undertake other tasks.

[0055] If the memory usage of the malfunctioning device is below the preset threshold, it indicates that the device still has sufficient resources available, and simply repairing or adjusting the DHCP configuration may be sufficient to restore normal operation. Conversely, if the memory usage is higher than or equal to the preset threshold, it indicates that the device resources are strained, and further measures may be necessary, such as migrating services to other devices or upgrading hardware.

[0056] Step 4: If the memory usage status is less than or equal to the preset usage threshold, retrieve the DHCP configuration of the abnormal device based on the SDN database and send the DHCP configuration to the idle device.

[0057] The system retrieves the original DHCP configuration information of the malfunctioning device from an SDN database. The SDN database centrally stores various configuration information in the network, including DHCP configurations. By querying the database, the system can obtain the device's previous normal DHCP configuration. After obtaining the original DHCP configuration of the malfunctioning device, the configuration information is sent to idle devices in the network. Idle devices are those not currently performing DHCP services or other important tasks; they have sufficient resources to take over the DHCP service from the malfunctioning device.

[0058] Step 5: Process the abnormal state of the abnormal device based on the preset abnormal handling algorithm in order to repair the abnormal device.

[0059] First, based on the type and state of the abnormal device, compare it with the preset abnormal handling strategies to select the appropriate abnormal handling strategy.

[0060] Based on the type and specific abnormal state of the faulty device, the system compares its handling with preset error handling strategies. Preset strategies may include specific solutions for different types and degrees of problems such as DHCP configuration errors, IP allocation errors, and interface status anomalies. Through comparison, the system can select the most suitable handling strategy for the current abnormal state.

[0061] Furthermore, exception handling policies are implemented, and the device status and DHCP configuration are monitored.

[0062] After selecting an appropriate anomaly handling strategy, the strategy is executed to repair the malfunctioning device. Simultaneously, the system continuously monitors the device's status and DHCP configuration to ensure the repair measures are effective and adjusts the strategy promptly to address any new situations that may arise.

[0063] Furthermore, when a preset maintenance threshold is reached, a designated maintenance personnel will be notified.

[0064] If the number of times the anomaly handling strategy is executed reaches the preset maintenance threshold, the designated maintenance personnel will be notified. Upon receiving the notification, the maintenance personnel can further inspect and manually repair the equipment to ensure the stability and reliability of network services.

[0065] In addition, this application also includes the following methods:

[0066] First, based on the lease information, determine if the malfunctioning device is within a preset idle time period. If so, modify the lease timer of the malfunctioning device to match the idle time period. The idle time period is set based on network usage and device load, aiming to optimize network resource utilization. If the malfunctioning device is within an idle time period, modifying its lease timer to match the idle time period will prevent the device from being assigned a new IP address during that period, thus saving network resources.

[0067] If not, record the lease time of the malfunctioning device as indefinite. If the malfunctioning device is not in an idle period, record its lease time as indefinite. This is understandably to ensure that during peak network hours, malfunctioning devices do not disrupt normal network operation due to lease expiration.

[0068] Furthermore, the system waits for the designated administrator to restore the device status of the malfunctioning device. When the device status returns to normal, the system restores the DHCP configuration of the malfunctioning device and records that its lease has expired. Once the device status returns to normal, the system restores the DHCP configuration of the device and records its lease as expired for subsequent lease management.

[0069] Furthermore, the lease information of member switch devices is queried based on the DHCP logs; the lease information includes the lease start time, end time, and renewal status.

[0070] Furthermore, when a member switch device's lease has expired, the renewal status of that member switch device is queried. When a member switch device's lease is detected to have expired, the renewal status of that device is queried.

[0071] When renewing a lease, refresh the lease for the member switch device that has expired. If the device chooses to renew, refresh the lease for that device to ensure it can continue to use network resources normally.

[0072] When a contract is not renewed, delete the IP records and static IP configurations of the member switch devices. If a device chooses not to renew its contract, delete its IP records and static IP configurations to free up network resources for other devices.

[0073] The above are embodiments of the method proposed in this application. Based on the same inventive concept, embodiments of this application also provide a device for configuring DHCP in MLAG networking based on SDN, the structure of which is as follows: Figure 2 As shown.

[0074] Figure 3 This is a schematic diagram of the internal structure of a device configuring DHCP for an SDN-based MLAG network, provided as an embodiment of this application. Figure 3 As shown, the device includes:

[0075] At least one processor 201;

[0076] And a memory 202 that is communicatively connected to at least one processor;

[0077] The memory 202 stores instructions executable by at least one processor, which are executed by at least one processor 201 to enable at least one processor 201 to:

[0078] The system configures DHCP for member switches in an MLAG network based on a DHCP front-end and receives DHCP logs from these switches. It monitors member switches in real-time to obtain their status and device information, including normal and abnormal states. Abnormal states include DHCP configuration errors, IP allocation errors, and abnormal interface states. When a member switch is in an abnormal state, its DHCP server is deleted, and its memory usage is checked against a preset threshold. The abnormal device is the member switch that caused the abnormal state. If the memory usage exceeds the preset threshold, no DHCP configuration is performed on the abnormal device. If the memory usage is less than or equal to the preset threshold, the DHCP configuration of the abnormal device is retrieved from the SDN database and sent to idle devices. A preset anomaly handling algorithm is used to process the leases and abnormal states of abnormal devices to correct their abnormal states.

[0079] Some embodiments of this application provide corresponding to Figure 1A non-volatile computer storage medium for configuring DHCP in an SDN-based MLAG network, storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0080] The system configures DHCP for member switches in an MLAG network based on a DHCP front-end and receives DHCP logs from these switches. It monitors member switches in real-time to obtain their status and device information, including normal and abnormal states. Abnormal states include DHCP configuration errors, IP allocation errors, and abnormal interface states. When a member switch is in an abnormal state, its DHCP server is deleted, and its memory usage is checked against a preset threshold. The abnormal device is the member switch that caused the abnormal state. If the memory usage exceeds the preset threshold, no DHCP configuration is performed on the abnormal device. If the memory usage is less than or equal to the preset threshold, the DHCP configuration of the abnormal device is retrieved from the SDN database and sent to idle devices. A preset anomaly handling algorithm is used to process the leases and abnormal states of abnormal devices to correct their abnormal states.

[0081] 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 IoT devices and media are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0082] The systems, media, and methods provided in this application are one-to-one correspondences. Therefore, the systems 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 systems and media will not be repeated here.

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

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

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

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

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

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

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

[0090] 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 process, method, article, or apparatus. Unless otherwise specified, 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 that element.

[0091] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for configuring DHCP in an SDN-based MLAG network, characterized in that, An MLAG networking service system is applied, comprising: an SDN control module and an MLAG networking module; the SDN control module includes an SDN front-end, an SDN controller, and an SDN database; the MLAG networking module includes multiple member switch devices and a DHCP front-end, and the method includes: Configure the DHCP of the member switch devices under the MLAG network based on the DHCP front-end, and receive the DHCP logs of the member switch devices; The member switch devices are monitored in real time to obtain their status and device information; the status includes normal status and abnormal status, and the abnormal status includes DHCP configuration error, IP allocation error, and interface status abnormality. When the member switch device is in an abnormal state, delete the DHCP of the abnormal device and determine whether the memory usage of the abnormal device is lower than a preset usage threshold; wherein, the abnormal device is the member switch device that caused the abnormal state. If the memory usage exceeds a preset threshold, no DHCP configuration will be performed on the abnormal device. If the memory usage status is less than or equal to a preset usage threshold, retrieve the DHCP configuration of the abnormal device based on the SDN database, and send the DHCP configuration to the idle device; The abnormal state of the abnormal device is processed based on a preset abnormality handling algorithm in order to repair the abnormal device.

2. The method for configuring DHCP in an SDN-based MLAG network according to claim 1, characterized in that, Configure the DHCP settings of the member switches in the MLAG network based on the DHCP front-end, and receive the DHCP logs of the member switches, specifically including: Configure DHCP parameters for member switch devices in the MLAG network through the DHCP front-end interface; the DHCP parameters include IP address and lease time. Receive and store DHCP logs sent by member switch devices; wherein the DHCP logs include DHCP requests and DHCP responses.

3. The method for configuring DHCP in an SDN-based MLAG network according to claim 1, characterized in that, When the member switch device is in an abnormal state, the DHCP server of the abnormal device is deleted, and it is determined whether the memory usage of the abnormal device is lower than a preset threshold, specifically including: When an abnormal status is detected in a member switch device, the member switch device is marked as an abnormal device, and the DHCP service of the member switch device is stopped. Query the memory usage of the abnormal device; The memory usage is compared with a preset usage threshold to determine whether the abnormal device can continue to operate.

4. The method for configuring DHCP in an SDN-based MLAG network according to claim 1, characterized in that, Real-time monitoring of the member switch devices to obtain their status and device information, specifically including: Periodically send status query requests to member switch devices to obtain the operating status, interface status and DHCP configuration information of the member switch devices; The system processes the operating status, interface status, and DHCP configuration information based on a preset status analysis model to determine whether the member switch device is in a normal state and to determine the status and device information of the member switch device.

5. The method for configuring DHCP in an SDN-based MLAG network according to claim 1, characterized in that, The lease and abnormal state of the abnormal device are processed based on a preset anomaly handling algorithm to repair the abnormal device, specifically including: Based on the type and state of the abnormal device, compare it with the preset abnormal handling strategies to select the appropriate abnormal handling strategy; Implement exception handling policies and monitor device status and DHCP configuration; When the preset maintenance threshold is reached, the preset maintenance personnel will be notified.

6. The method for configuring DHCP in an SDN-based MLAG network according to claim 1, characterized in that, The method further includes: Determine whether the abnormal device is in a preset idle time period based on the lease information; If so, modify the lease time of the abnormal device to an idle period; If not, record the lease period of the abnormal device as indefinite; Wait for the preset administrator to restore the device status of the abnormal device. When the device status is normal, restore the DHCP configuration of the abnormal device and record that the lease of the abnormal device has expired.

7. The method for configuring DHCP in an SDN-based MLAG network according to claim 6, characterized in that, The method further includes: The lease information of the member switch devices is queried according to the DHCP log; wherein, the lease information includes the lease start time, end time, and renewal status; When the lease of a member switch device has expired, query the renewal status of the corresponding member switch device; When renewing a lease, the lease is refreshed to the lease of the member switch equipment that has already expired; When the contract is not renewed, delete the IP records and static IP configurations of the member switch devices.

8. A device for configuring DHCP in MLAG networking based on SDN, characterized in that, The device includes: at least one processor; And, a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: Configure the DHCP of the member switch devices under the MLAG network based on the DHCP front-end, and receive the DHCP logs of the member switch devices; The member switch devices are monitored in real time to obtain their status and device information; the status includes normal status and abnormal status, and the abnormal status includes DHCP configuration error, IP allocation error, and interface status abnormality. When the member switch device is in an abnormal state, delete the DHCP of the abnormal device and determine whether the memory usage of the abnormal device is lower than a preset usage threshold; wherein, the abnormal device is the member switch device that caused the abnormal state. If the memory usage exceeds a preset threshold, no DHCP configuration will be performed on the abnormal device. If the memory usage status is less than or equal to a preset usage threshold, retrieve the DHCP configuration of the abnormal device based on the SDN database, and send the DHCP configuration to the idle device; The abnormal state of the abnormal device is processed based on a preset abnormality handling algorithm in order to repair the abnormal device.

9. A non-volatile computer storage medium for configuring DHCP in an SDN-based MLAG network, storing computer-executable instructions, characterized in that, The computer-executable instructions are set as follows: Configure the DHCP of the member switch devices under the MLAG network based on the DHCP front-end, and receive the DHCP logs of the member switch devices; The member switch devices are monitored in real time to obtain their status and device information; the status includes normal status and abnormal status, and the abnormal status includes DHCP configuration error, IP allocation error, and interface status abnormality. When the member switch device is in an abnormal state, delete the DHCP of the abnormal device and determine whether the memory usage of the abnormal device is lower than a preset usage threshold; wherein, the abnormal device is the member switch device that caused the abnormal state. If the memory usage exceeds a preset threshold, no DHCP configuration will be performed on the abnormal device. If the memory usage status is less than or equal to a preset usage threshold, retrieve the DHCP configuration of the abnormal device based on the SDN database, and send the DHCP configuration to the idle device; The lease and abnormal state of the abnormal device are processed based on a preset anomaly handling algorithm to repair the abnormal state of the abnormal device.

Images