A configuration delivery method, device and medium of a switch stacking system

Abstract

The application discloses a configuration delivery method and device of a switch stack system and a medium. The method comprises the following steps: a first device analyzes a configuration command, generates push configuration information according to the analysis configuration information, and publishes the push configuration information to a shared message queue; the shared message queue is a redis stream; the push configuration information carries a unique incremental identifier; when a switch device stack process is started, a second device starts a new process, receives the push configuration information listened to from the shared message queue through the new process; the new process is used for calling an IMISH module; when the second device determines that configuration updating needs to be performed according to the push configuration information, the second device determines the updating order of the push configuration information according to the incremental identifier. Configuration information can be delivered to a switch device that needs configuration updating, and configuration updating can be automatically performed.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of switch network communication, and in particular to a configuration issuing method of a switch stacking system, a device and a medium. BACKGROUND

[0002] With the continuous expansion of the network scale, the demand for high concurrency, high throughput, and convenient management of network systems is increasingly significant, and thus the stacking system technology of two or more switches combined for unified management emerges as the times require. Based on this, multiple switches are interconnected as member devices to form a joint device, which logically operates as a switch to realize efficient interconnection and unified management of the switching network. The joint device is called a stacking system. Unlike independent cascading of multiple switches, the stacking system can utilize existing resources with less change to the original network topology, which is equivalent to providing more ports for a single switch, thereby providing high concurrency and high throughput switching services.

[0003] Specifically, the member devices in the stacking system will generate corresponding master devices, backup devices and slave devices during the election, and the system configuration issuing and management are dominated by the master device. For a switch stacking system, in addition to the performance being better than a single device, since multiple member devices are involved, when a single member device fails, the remaining devices need to ensure that network services are not affected to the greatest extent, and the configurations of each member device are consistent and stable to work together to ensure the stability and reliability of network communication.

[0004] Currently, the corresponding configurations are generally issued uniformly in all member devices at the same time, which will lead to repeated and redundant configuration issuing, consuming system resources. Or the configuration files are sent to each member device through a file transfer protocol (such as SCP, FTP or SFTP), and then the member devices apply these configurations. This scheme usually requires manual intervention, has limited automation, is not suitable for large-scale configuration updates, and has poor real-time performance.

[0005] Therefore, a more efficient, simple and flexible configuration issuing technical scheme for a switch stacking system is needed. SUMMARY

[0006] The embodiments of the present application provide a configuration issuing method of a switch stacking system, a device and a medium, which are used to solve the problem of needing a more efficient, simple and flexible configuration issuing technical scheme for a switch stacking system.

[0007] The embodiments of the present application adopt the following technical scheme:

[0008] In one aspect, the embodiments of the present application provide a configuration issuing method of a switch stack system, which comprises: a first device parsing a configuration command, generating push configuration information according to parsed configuration information, and publishing the push configuration information to a shared message queue; the shared message queue is a redis stream; the first device is a master device; the push configuration information carries a unique incremental identifier; when a switch device stack process is started, a second device starts a new process, and receives the push configuration information listened to from the shared message queue through the new process; the second device is a backup device and a slave device; the new process is used to call an IMISH module; when it is determined that configuration update needs to be performed according to the push configuration information, the second device determines an update order of the push configuration information according to the incremental identifier.

[0009] In one example, the first device parses the configuration command, generates the push configuration information according to the parsed configuration information, and specifically comprises: the first device parses the configuration command to obtain to-be-configured information, an execution role of the to-be-configured information, and port issuing information of the to-be-configured information, the port issuing information comprising a specified port of a specified device ID; execution device marker information of the to-be-configured information is determined according to the execution role and the port issuing information; a unique incremental identifier is generated for the to-be-configured information; and the push configuration information is generated according to the to-be-configured information, the execution device marker information, and the incremental identifier.

[0010] In one example, the execution device marker information of the to-be-configured information is determined according to the execution role and the port issuing information, and specifically comprises: the execution role is matched in the switch stack system to obtain a first to-be-configured device; the port issuing information is matched in the first to-be-configured device, and when the matching is successful, a second to-be-configured device is obtained; and the execution device marker information of the to-be-configured information is determined according to the second to-be-configured device.

[0011] In one example, the method further comprises: if the port issuing information fails to match in the first to-be-configured device, it is determined that the port issuing information is empty; and the execution device marker information of the to-be-configured information is determined according to the first to-be-configured device.

[0012] In one example, the method further comprises: the second device compares the execution device marker information in the push configuration information with device information of the second device; when the comparison is successful, it is determined that the second device needs to perform configuration update; and when the comparison fails, it is determined that the second device does not need to perform configuration update.

[0013] In one example, the switch device in the switch stack system includes an adding process, an IMISH module, an IMI module and a PM module. After the adding process receives the pushed configuration information from the shared message queue, the method further includes: the second device calling the IMISH module through the adding process, and sending the pushed configuration information to the IMISH module; analyzing the pushed configuration information through the IMISH module, and sending the analyzed pushed configuration information to the IMI module; and sending the analyzed configuration information to the PM module through the IMI module, so that the PM module performs configuration update.

[0014] In one example, the method further includes: starting the adding process when the switch device stack process is started; sending the pushed configuration information to the IMI module through the IMISH module, and publishing the pushed configuration information to the shared message queue through the IMI module.

[0015] In one example, the method further includes: the first device comparing the execution device mark information in the pushed configuration information with the device information of the local device; when the comparison is successful, determining that the local device needs to perform configuration update; and when the comparison fails, determining that the local device does not need to perform configuration update.

[0016] In another aspect, the embodiments of the present application provide a configuration distribution device of a switch stack system, including: at least one processor; and a memory connected with the at least one processor in communication; wherein the memory stores instructions executable 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 perform the configuration distribution method of the switch stack system according to any one of the above.

[0017] In another aspect, the embodiments of the present application provide a non-volatile computer storage medium of a configuration distribution device of a switch stack system, storing computer executable instructions, and the computer executable instructions can perform the configuration distribution method of the switch stack system according to any one of the above.

[0018] The above at least one technical solution adopted by the embodiments of the present application can achieve the following beneficial effects:

[0019] The master device parses the command line and then publishes the message without manual intervention, has good flexibility, reduces invalid configuration distribution, and increases the stability of the stacking system. In addition, the introduction of the shared message queue mechanism realizes real-time configuration distribution across devices, and configuration information can be distributed to switch devices that need configuration updates. At the same time, the complex message processing process of the stacking system is simplified, instead of uniformly distributing configuration information. Further, the redis stream queue supports processing messages in the order of message ID. Based on the message queue mechanism, the order of device configuration update is guaranteed in the case of a single switch device corresponding to multiple configuration messages, thereby guaranteeing the configuration execution order and consistency. In addition, through the publish-subscribe mechanism, configuration information can be automatically pulled from the shared message queue, thereby calling the IMISH module based on the newly added process to automatically update the configuration.

[0020] In addition, the push configuration information carries a unique incremental identifier ID, which guarantees the configuration execution order and consistency, improves the configuration execution success rate, and reduces the consumption of system processing resources. In addition, the scheme of calling the IMISH module by the newly added process solves the problem that the commands registered in the IMISH module cannot be completely distributed. BRIEF DESCRIPTION OF DRAWINGS

[0021] In order to more clearly illustrate the technical solutions of the present application, some embodiments of the present application will be described in detail below with reference to the accompanying drawings, in which:

[0022] Figure 1 A schematic diagram of a switch stacking system is provided for the embodiments of the present application.

[0023] Figure 2 A flowchart of a configuration distribution method of a switch stacking system is provided for the embodiments of the present application.

[0024] Figure 3 A frame diagram of a switch device in a switch stacking system is provided for the embodiments of the present application.

[0025] Figure 4 A structural diagram of a configuration distribution device of a switch stacking system is provided for the embodiments of the present application. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described clearly and completely below with reference to specific embodiments and corresponding drawings. Obviously, the described embodiments are only some of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0027] Some embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0028] Figure 1 A schematic diagram of a switch stacking system is provided for embodiments of the present application.

[0029] In Figure 1 , multiple devices enable a stacking mode, join a stacking system, determine the roles (active, standby, member) of each member device through election, and work together to maintain normal network communication services. The system includes an active device, a standby device, a member device, and a stream message queue. The active device is a publisher and is mainly used to publish push configuration information to the message queue. The standby device and the member device are subscribers and listen to the subscription configuration information from the message queue to perform configuration updates.

[0030] The switch stacking system is a network communication system that logically operates as one device by combining two or more switches. In the stacking mode, all device configurations are issued from the active device, and it is necessary to ensure that the configurations of all devices in the system are consistent and unified, and to avoid problems caused by configuration differences between different devices.

[0031] It should be noted that the user performs a configuration issuing operation through a command line interface, and the active device preliminarily parses the command line and then publishes push configuration information to the redis streams message queue. This synchronization mechanism has a shared stream message queue, which allows other member devices to read data from the shared message queue pool, decouples the configuration management logic from the device logic, and only needs to send a command to push the configuration update to all member devices, simplifying the internal processing flow, realizing cross-device and cross-process message communication, and making management and maintenance easier.

[0032] More intuitively, Figure 2 A flowchart of a configuration issuing method of a switch stacking system is provided for embodiments of the present application. The method can be applied to different business fields, such as the Internet financial business field, the e-commerce business field, the instant messaging business field, the game business field, the public service business field, etc. Some input parameters or intermediate results in the flowchart allow manual intervention to adjust to help improve accuracy.

[0033] Figure 1 The flowchart in

[0034] S201: The first device parses the configuration command, generates push configuration information according to the parsed configuration information, and publishes the push configuration information to a shared message queue; the shared message queue is a redis stream; the first device is a master device; and the push configuration information carries a unique incremental identifier.

[0035] In some embodiments of the present application, the first device generates the push configuration information in the following process:

[0036] The first device parses the configuration command to obtain to-be-configured information, an execution role of the to-be-configured information, and port delivery information of the to-be-configured information. The port delivery information includes a specified port of a specified device ID.

[0037] Then, according to the execution role and the port delivery information, the execution device marker information of the to-be-configured information is determined.

[0038] It should be noted that the process of determining the execution device marker information of the to-be-configured information is as follows:

[0039] The execution role is matched in the switch stack system to obtain a first to-be-configured device. Then, the port delivery information is matched in the first to-be-configured device, and when the matching is successful, a second to-be-configured device is obtained. Finally, according to the second to-be-configured device, the execution device marker information of the to-be-configured information is determined. It should be noted that if the port delivery information fails to match in the first to-be-configured device, it is determined that the port delivery information is empty. According to the first to-be-configured device, the execution device marker information of the to-be-configured information is determined.

[0040] In addition, a unique incremental identifier is generated for the to-be-configured information.

[0041] It should be noted that the incremental identifier can be used to identify the configuration order of the to-be-configured information. Sometimes, the delivery of the configuration has a front-back dependency relationship. The introduction of the unique incremental identifier ID enables the device to execute according to the message delivery update order when receiving the configuration message, improves the configuration execution success rate, and also ensures that the message is executed at most once in the device, avoiding repeated delivery of the configuration. That is, the push configuration information carries a unique incremental identifier ID, ensuring the configuration execution order and consistency, improving the configuration execution success rate, and reducing the consumption of system processing resources.

[0042] Finally, according to the to-be-configured information, the execution device marker information, and the incremental identifier, the push configuration information is generated.

[0043] It should be noted that when the active device parses the command line, the parsed content includes whether the command needs to be executed on which role of the system (Flag), the execution mode of the command (Mode), and the like. The standby device and the slave device can determine whether the local device needs to be executed according to the parsed content in the message when receiving the corresponding message. Flag: Compared with the role of the device, some messages need to be executed only on the active device and the standby device. Mode: Mainly distinguishes whether in port mode. For the configuration issued only in a single port, the device ID is specified, and the corresponding configuration message can be executed only on the specified port of the specified device, and other devices can not be processed.

[0044] Therefore, the operation of parsing the command line of the active device reduces the invalid configuration issuance.

[0045] S202: When the switch device stacking process is started, the second device starts a new process, and receives the pushed configuration information listened to from the shared message queue through the new process; the second device is a standby device and a slave device; the new process is used to call an IMISH module.

[0046] In some embodiments of the present application, the switch device in the switch stacking system includes a new process, an IMISH module, an IMI module and a PM module. Generally, there are multiple PM modules.

[0047] Figure 3 The embodiment of the present application provides a framework schematic diagram of a switch device in a switch stacking system.

[0048] In Figure 3 In the embodiment, the new process is an imish_scfd process. The IMISH takes over the serial port and runs the command line interface to parse the command. In addition to local commands, other commands are sent to the IMI module. The IMI module provides centralized control of command information, and the PM is another single protocol module.

[0049] In the embodiment, the second device sends the pushed configuration information to the IMISH module by calling the IMISH module through the new process. Then, the pushed configuration information is parsed by the IMISH module, and the parsed pushed configuration information is sent to the IMI module. Then, the parsed configuration information is sent to the PM module by the IMI module, so as to execute the configuration update by the PM module.

[0050] It should be noted that when the switch device stacking process is started, the first device also starts a new process. The pushed configuration information is sent to the IMI module through the IMISH module, and the pushed configuration information is published to the shared message queue through the IMI module.

[0051] It should be noted that generally, the IMI module subscribes to receive the push configuration information, while the IMI SH module cannot subscribe to receive the push configuration information, therefore, if there is no new process, since there is no path from the IMI module to the IMI SH module, the command for each PM module in the IMI SH module cannot be issued, thereby causing the command registered in the IMI SH module to be unable to be completely issued. Based on this, by adding a process, the process receives the subscription redis configuration issuing message, the original process changes little, and the problem that the registration command of multiple PM modules cannot be completely issued can also be solved.

[0052] S203: According to the push configuration information, when it is determined that configuration update needs to be performed, the second device determines the update order of the push configuration information according to the incremental identifier.

[0053] Among them, the second device compares the execution device mark information in the push configuration information with the device information of the local machine. When the comparison is successful, it is determined that the local machine needs to perform configuration update. When the comparison fails, it is determined that the local machine does not need to perform configuration update.

[0054] In addition, the first device also compares the execution device mark information in the push configuration information with the device information of the local machine. When the comparison is successful, it is determined that the local machine needs to perform configuration update. When the comparison fails, it is determined that the local machine does not need to perform configuration update.

[0055] Compared with the prior art: in the prior art, the scheme of issuing corresponding configurations to all member devices uniformly causes unnecessary network and processing resource consumption, lacks flexibility for scenarios that need to be configured differently according to device roles, and this method depends on a centralized management strategy, if the management tool fails, it may affect the configuration update of the entire stack system. In addition, the scheme of sending configuration files to each member device through the file transfer protocol, and then applying the configurations by the member devices, usually needs manual intervention, although the file transfer can be automated through scripts, the configuration application on the device may need additional automation logic, and is not suitable for large-scale configuration update, has poor real-time performance, and the execution result difference makes it difficult to guarantee the consistency of the configurations on all member devices.

[0056] In summary, the introduction of the shared message queue mechanism realizes real-time configuration cross-device distribution, can distribute configuration information to switch devices that need configuration update, and simplifies the complex message processing process of the stacking system instead of uniformly distributing configuration information. Further, the redis stream queue supports processing messages in the order of message ID, and based on the message queue mechanism, the order of device configuration update is guaranteed in the case of a single switch device corresponding to multiple configuration messages, thereby guaranteeing the configuration execution order and consistency. Through the publish-subscribe mechanism, configuration information can be automatically pulled from the shared message queue, thereby automatically updating the configuration based on the processing relationship between the new process, the IMISH module, the IMI module, and the PM module.

[0057] It should be noted that although the embodiments of the present application are introduced and described in sequence with reference to Figure 2 steps S201 to S203, this does not mean that steps S201 to S203 must be executed in strict sequence. The embodiments of the present application introduce and describe steps S201 to S203 in sequence as shown in Figure 2 in order to facilitate understanding of the technical solutions of the embodiments of the present application by those skilled in the art. In other words, in the embodiments of the present application, the sequence of steps S201 to S203 can be appropriately adjusted according to actual needs.

[0058] Through the method, Figure 2 the host device parses the command line and then publishes the message without manual intervention, has good flexibility, reduces invalid configuration distribution, and increases the stability of the stacking system. In addition, the introduction of the shared message queue mechanism realizes real-time configuration cross-device distribution, can distribute configuration information to switch devices that need configuration update, and simplifies the complex message processing process of the stacking system instead of uniformly distributing configuration information. Further, the redis stream queue supports processing messages in the order of message ID, and based on the message queue mechanism, the order of device configuration update is guaranteed in the case of a single switch device corresponding to multiple configuration messages, and through the publish-subscribe mechanism, configuration information can be automatically pulled from the shared message queue, thereby automatically updating the configuration based on the processing relationship between the new process and the IMISH module.

[0059] In addition, the scheme of the new process calling the IMISH module solves the problem that the commands registered in the IMISH module cannot be completely distributed.

[0060] That is, the configuration delivery method in the switch stack system effectively overcomes the information interaction barrier across devices and processes based on the redis stream ordered message queue, starts a new imish_scfd process, and adjusts the device configuration adaptive delivery mechanism, ensures the consistency of the stack system configuration, makes the configuration management of the stack system more efficient, flexible and reliable, and greatly increases the stability and reliability of the stack system.

[0061] Based on the same idea, some embodiments of the present application also provide a device and a non-volatile computer storage medium corresponding to the above method.

[0062] Figure 4 A structural schematic diagram of a configuration delivery device of a switch stack system provided by an embodiment of the present application comprises:

[0063] At least one processor; and

[0064] A memory in communication connection with the at least one processor; wherein

[0065] The memory stores instructions executable 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 perform the configuration delivery method of the switch stack system according to any one of the above.

[0066] Some embodiments of the present application provide a non-volatile computer storage medium for configuration delivery of a switch stack system, which stores computer executable instructions, and the computer executable instructions can perform the configuration delivery method of the switch stack system according to any one of the above.

[0067] Each of the embodiments in the present application is described in a progressive manner, and the same or similar parts of each embodiment can be referred to each other. Each embodiment mainly describes the difference from other embodiments. Especially, the device and medium embodiments are basically similar to the method embodiments, so the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

[0068] The device and medium provided by the embodiments of the present application correspond to the method, so the device and medium also have the similar beneficial technical effects as the method. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the device and medium will not be described here.

[0069] Those skilled in the art will appreciate that embodiments of the application can be devised for a method, a system, or a computer program product. Accordingly, the present application can be embodied in the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application can take the form of a computer program product on one or more computer readable storage media (including, but not limited to, disk memory, CD-ROMs, optical storage devices, etc.) embodying computer readable program code.

[0070] The present application is described in reference to the flowchart illustrations and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the 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, create means for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams.

[0071] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams.

[0072] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams.

[0073] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0074] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory. The memory can also include non-volatile memory, such as read-only memory (ROM), electrically programmable read-only memory (EPROM), electrically erasable read-only memory (EEPROM), or flash memory. The memory is an example of computer readable media.

[0075] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules 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 technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0076] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover non-exclusive inclusions, so that a process, method, article or apparatus that includes a list of elements does not only include those elements, but also includes other elements not explicitly listed, or further includes elements inherent in such a process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

[0077] The above only describes the embodiments of the present application and is not intended to limit the present application. Those skilled in the art can make various modifications and changes to the present application. Any modification, equivalent replacement, improvement, etc. made within the technical principles of the present application shall fall within the protection scope of the present application.

Claims

1. A configuration distribution method of a switch stacking system, characterized in that, The method comprises: The first device parses the configuration command, generates push configuration information according to the parsed configuration information, and publishes the push configuration information to a shared message queue; the shared message queue is a redis stream; the first device is a master device; the push configuration information carries a unique incremental identifier; When the switch device stacking process is started, the second device starts a new process, and receives the push configuration information listened to from the shared message queue through the new process; the second device is a backup device and a slave device; the new process is used to call an IMISH module; The second device determines the update order of the push configuration information according to the incremental identifier when it is determined that configuration update needs to be performed according to the push configuration information; The switch device in the switch stacking system comprises a new process, an IMISH module, an IMI module and a PM module, and after the push configuration information listened to from the shared message queue is received through the new process, the method further comprises: The second device calls the IMISH module through the new process, and sends the push configuration information to the IMISH module; The push configuration information is parsed through the IMISH module, and the parsed push configuration information is sent to an IMI module; The parsed configuration information is sent to a PM module through the IMI module, so that configuration update is performed through the PM module; The method further comprises: When the switch device stacking process is started, the first device starts a new process; The push configuration information is sent to an IMI module through an IMISH module, and the push configuration information is published to a shared message queue through the IMI module.

2. The method of claim 1, wherein, The first device parses the configuration command, generates push configuration information according to the parsed configuration information, and specifically comprises: The first device parses the configuration command to obtain to-be-configured information, an execution role of the to-be-configured information and port delivery information of the to-be-configured information, and the port delivery information comprises a specified port of a specified device ID; According to the execution role and the port delivery information, the execution device marker information of the to-be-configured information is determined; A unique incremental identifier is generated for the to-be-configured information; The push configuration information is generated according to the to-be-configured information, the execution device marker information and the incremental identifier.

3. The method of claim 2, wherein, The execution role is matched in the switch stacking system to obtain a first to-be-configured device; The port delivery information is matched in the first to-be-configured device, and when the matching is successful, a second to-be-configured device is obtained; According to the second to-be-configured device, the execution device marker information of the to-be-configured information is determined. The method further comprises:

4. The method of claim 3, wherein, If the port delivery information fails to match in the first to-be-configured device, it is determined that the port delivery information is empty; According to the first to-be-configured device, the execution device marker information of the to-be-configured information is determined. The method further comprises:

5. The method of claim 2, wherein, ​ The second device compares the execution device marker information in the push configuration information with local device information; When the comparison is successful, it is determined that the local device needs to perform configuration update; When the comparison fails, it is determined that the local device does not need to perform configuration update.

6. The method of claim 2, wherein, The method further comprises: The first device compares the execution device marker information in the push configuration information with local device information; When the comparison is successful, it is determined that the local device needs to perform configuration update; When the comparison fails, it is determined that the local device does not need to perform configuration update.

7. A configuration delivery device of a switch stacking system, characterized in that, Comprise: At least one processor; And The memory is in communication connection with the at least one processor; wherein The memory stores instructions executable 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 perform the configuration distribution method of the switch stacking system according to any one of claims 1-6.

8. A non-transitory computer storage medium storing computer-executable instructions for configuring a switch stacking system, the computer-executable instructions comprising: Applied to the second device, the computer executable instructions can perform the configuration distribution method of the switch stacking system according to any one of claims 1-6.

Images