Configuration issuing method and device of switch stacking system and medium

Abstract

The invention discloses a configuration issuing method and device for a switch stacking system and a medium, and the method comprises the steps that a first device analyzes a configuration command, generates push configuration information according to the analyzed configuration information, and issues 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 the stacking process of the switch equipment is started, the second equipment starts a newly added process, and the monitored push configuration information is received from the shared message queue through the newly added process; the newly added process is used for calling an IMISH module; and when the second equipment determines that configuration updating needs to be executed according to the push configuration information, the updating sequence of the push configuration information is determined according to the incremental identifier. Configuration information can be issued to switch equipment needing configuration updating, and configuration updating is automatically carried out.

Description

Technical Field

[0001] The present application relates to the field of switch network communication technology, and in particular to a configuration delivery method, device and medium for a switch stacking system. Background Art

[0002] As the scale of networks continues to expand, the demand for high-concurrency, high-throughput, and easy-to-manage network systems has become increasingly prominent, so the stacking system technology that can be used in combination with two or more switches and can be managed in a unified manner has emerged. Based on this, multiple switches are interconnected as member devices to form a joint device, which logically operates as a switch to achieve efficient interconnection and unified management of the switching network. This joint device is called a stacking system. Different from the independent cascading of multiple switches, the stacking system can use existing resources and change the original network topology less, which is equivalent to a single switch providing more ports, thereby providing high-concurrency and high-throughput switch services.

[0003] Specifically, the member devices in the stacking system will generate corresponding master devices, backup devices, and slave devices during elections, and the system configuration and management are all dominated by the master device. For the switch stacking system, in addition to having better performance than a single device, since it involves multiple member devices, when a single member device fails, the remaining devices need to be able to ensure that network services are not affected to the greatest extent, and the configuration of each member device is consistent and stable to work together to ensure stable and reliable network communication.

[0004] At present, the corresponding configuration is generally sent to all member devices at the same time. This solution will lead to repeated and redundant configuration delivery, consuming system resources; or the configuration file is 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 solution usually requires manual intervention, has a limited degree of automation, is not suitable for large-scale configuration updates, and has poor real-time performance.

[0005] Therefore, a more efficient, simple and flexible technical solution for issuing configurations of a switch stacking system is needed. Summary of the invention

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

[0007] The present application embodiment adopts the following technical solutions:

[0008] On the one hand, an embodiment of the present application provides a configuration sending method for a switch stacking system, the method comprising: a first device parses a configuration command, generates push configuration information based on 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 pushed configuration information monitored 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 based on the incremental identifier when determining that a configuration update needs to be performed based on the push configuration information.

[0009] In one example, the first device parses the configuration command and generates push configuration information based on the parsed configuration information, specifically including: the first device parses the configuration command to obtain the information to be configured, the execution role of the information to be configured, and the port sending information of the information to be configured, the port sending information including the specified port of the specified device ID; determines the execution device tag information of the information to be configured based on the execution role and the port sending information; generates a unique incremental identifier for the information to be configured; and generates push configuration information based on the information to be configured, the execution device tag information and the incremental identifier.

[0010] In one example, determining the execution device tag information of the information to be configured based on the execution role and the port sent information specifically includes: matching the execution role in the switch stacking system to obtain a first device to be configured; matching the port sent information in the first device to be configured, and when the match is successful, obtaining a second device to be configured; and determining the execution device tag information of the information to be configured based on the second device to be configured.

[0011] In one example, the method further includes: if the port sending information fails to match in the first device to be configured, determining that the port sending information is empty; and determining execution device tag information of the information to be configured according to the first device to be configured.

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

[0013] In one example, the switch device in the switch stacking system includes a new process, an IMISH module, an IMI module and a PM module. After the new process receives the push configuration information monitored from the shared message queue, the method also includes: the second device calls the IMISH module through the new process to send the push configuration information to the IMISH module; parses the push configuration information through the IMISH module and sends the parsed push configuration information to the IMI module; sends the parsed configuration information to the PM module through the IMI module, so as to perform configuration updates through the PM module.

[0014] In one example, the method further includes: when the switch device stacking process is started, the first device starts a new process; sending the push configuration information to the IMI module through the IMISH module, and publishing the push configuration information to the shared message queue through the IMI module.

[0015] In one example, the method further includes: the first device compares the execution device tag information in the push configuration information with the device information of the local device; when the comparison is successful, it is determined that the local device needs to execute a configuration update; when the comparison fails, it is determined that the local device does not need to execute a configuration update.

[0016] On the other hand, an embodiment of the present application provides a configuration sending device for a switch stacking system, 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, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-described configuration sending methods for a switch stacking system.

[0017] On the other hand, an embodiment of the present application provides a non-volatile computer storage medium for sending configuration of a switch stacking system, which stores computer executable instructions, and the computer executable instructions can execute any of the above-mentioned methods for sending configuration of a switch stacking system.

[0018] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0019] After the main device parses and processes the command line, it publishes the message without manual intervention, which is flexible, reduces invalid configuration delivery, and increases the stability of the stacking system. In addition, the introduction of the shared message queue mechanism realizes the real-time cross-device configuration delivery, and can deliver configuration information to the switch devices that need to be updated. At the same time, it also simplifies the complex message processing process of the stacking system, instead of requiring unified delivery of configuration information. Furthermore, the redis stream queue supports processing messages in the order of message IDs. Based on the message queue mechanism, it ensures the order of device configuration updates when a single switch device corresponds to multiple configuration messages, thereby ensuring the configuration execution order and consistency. And through the publish-subscribe mechanism, it can realize automatic pulling of configuration information from the shared message queue, so as to call the IMISH module based on the newly added process and automatically update the configuration.

[0020] In addition, the pushed configuration information carries a unique incremental identifier ID, which ensures the order and consistency of configuration execution, improves the success rate of configuration execution, and reduces the consumption of system processing resources. In addition, the solution of adding a process to call the IMISH module solves the problem that the commands registered in the IMISH module cannot be fully issued. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0022] Figure 1 A schematic diagram of a switch stacking system provided in an embodiment of the present application;

[0023] Figure 2 A schematic diagram of a flow chart of a method for issuing configuration of a switch stack system provided in an embodiment of the present application;

[0024] Figure 3 A schematic diagram of a switch device in a switch stacking system provided in an embodiment of the present application;

[0025] Figure 4 A schematic diagram of the structure of a configuration issuing device for a switch stacking system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

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

[0028] Figure 1 A schematic diagram of a switch stacking system provided in an embodiment of the present application.

[0029] exist Figure 1 In the stacking system, multiple devices enable stacking mode and join the stacking system. The roles of each member device (active, standby, member) are determined through election. Each member device works together to maintain normal network communication services. The system includes the master device (active), standby device (standby), slave device (member), and stream message queue. Among them, the master device is the publisher, which is mainly used to publish and push configuration information to the message queue. The standby device and slave device are subscribers, which listen to and subscribe to configuration information from the message queue to perform configuration updates.

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

[0031] It should be noted that the user executes the configuration distribution operation through the command line interface, and the active device initially parses the command line and then publishes and pushes the 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, decoupling the configuration management logic from the device logic, and only needs to send a command once 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 flow chart of a configuration delivery method for a switch stacking system provided in an embodiment of the present application. The method can be applied to different business fields, such as Internet financial business field, e-commerce business field, instant messaging business field, game business field, official business field, etc. Certain input parameters or intermediate results in the process allow manual intervention and adjustment to help improve accuracy.

[0033] Figure 1 The process in includes the following steps:

[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; the push configuration information carries a unique incremental identifier.

[0035] In some embodiments of the present application, the process of the first device generating push configuration information is as follows:

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

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

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

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

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

[0041] It should be noted that the incremental identifier can be used to identify the configuration order of the information to be configured. The delivery of configuration sometimes has a dependency relationship. The introduction of the unique incremental identifier ID allows the device to execute according to the order of message delivery and update when receiving the configuration message, which improves the success rate of configuration execution. At the same time, it also ensures that the message is only executed once in the device, avoiding repeated configuration delivery. That is, the push configuration information carries a unique incremental identifier ID, which ensures the configuration execution order and consistency, improves the configuration execution success rate, and reduces the consumption of system processing resources.

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

[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 roles in the system (Flag), the command execution mode (Mode), etc. When the standby device and the slave device receive the corresponding message, they can decide whether the local device needs to execute it based on the parsed content in the message. Flag: Compare with the role of the device. Some messages only need to be executed on active and standby devices. Mode: Mainly distinguishes whether it is in port mode. For configurations sent only on a single port, the device ID will be specified. The corresponding configuration message can be executed only on the specified port of the specified device, and other devices can be ignored.

[0044] Therefore, the active device parses the command line operation, reducing invalid configuration delivery.

[0045] S202: When the switch device stacking process is started, the second device starts a new process, and receives the monitored push configuration information 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 the IMISH module.

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

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

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

[0049] The second device calls the IMISH module through a newly added process and sends the push configuration information to the IMISH module. Then, the push configuration information is parsed through the IMISH module and the parsed push configuration information is sent to the IMI module. Then, the parsed configuration information is sent to the PM module through the IMI module to perform configuration update through the PM module.

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

[0051] It should be noted that, under normal circumstances, the IMI module subscribes to receive push configuration information, while the IMISH module cannot subscribe to receive push configuration information. Therefore, if there is no new process, since there is no path from the IMI module to the IMISH module, the commands for each PM module in the IMISH module cannot be issued, resulting in the inability to issue the commands registered in the IMISH module completely. Based on this, by adding a new process, the process receives and subscribes to the redis configuration issuance message, which has little change to the original process and can also solve the problem that the registration commands of multiple PM modules cannot be issued completely.

[0052] S203: When the second device determines that a configuration update needs to be performed based on the push configuration information, the second device determines an update order of the push configuration information based on the incremental identifier.

[0053] The second device compares the execution device tag information in the push configuration information with the device information of the local device. If the comparison is successful, it is determined that the local device needs to perform a configuration update. If the comparison fails, it is determined that the local device does not need to perform a configuration update.

[0054] In addition, the first device will also compare the execution device tag information in the push configuration information with the device information of the local device. If the comparison is successful, it is determined that the local device needs to execute the configuration update. If the comparison fails, it is determined that the local device does not need to execute the configuration update.

[0055] Compared with the existing technology: In the existing technology, the solution of uniformly sending corresponding configurations to all member devices will cause unnecessary network and processing resource consumption, lack flexibility for scenarios that require differentiated configurations based on device roles, and this method relies on a centralized management strategy. If there is a problem with the management tool, it may affect the configuration update of the entire stack system. In addition, the solution of sending configuration files to each member device through the file transfer protocol and then applying these configurations by the member devices usually requires manual intervention. Although file transfer can be automated through scripts, the configuration application on the device may require additional automation logic, and is not suitable for large-scale configuration updates. The real-time performance is poor, and the difference in execution results makes it difficult to ensure the consistency of configurations on all member devices.

[0056] In summary, the introduction of the shared message queue mechanism enables cross-device configuration delivery in real time, and can deliver configuration information to switch devices that need configuration updates. It also simplifies the complex message processing process of the stacking system, rather than requiring unified delivery of configuration information. Furthermore, the redis stream queue supports processing messages in the order of message IDs. Based on the message queue mechanism, it ensures the order of device configuration updates when a single switch device corresponds to multiple configuration messages, thereby ensuring the configuration execution order and consistency. Through the publish-subscribe mechanism, it can automatically pull configuration information from the shared message queue, so that based on the processing relationship between the newly added process, IMISH module, IMI module and PM module, the device automatically updates the configuration.

[0057] It should be noted that although the embodiments of the present application are based on Figure 2 Steps S201 to S203 are described in sequence, but this does not mean that steps S201 to S203 must be performed in a strict order. Figure 2 The order shown in the figure introduces and explains step S201 to step S203 in sequence to facilitate those skilled in the art to understand the technical solution of the embodiment of the present application. In other words, in the embodiment of the present application, the order between step S201 to step S203 can be appropriately adjusted according to actual needs.

[0058] pass Figure 2 The method is that the main device parses and processes the command line before publishing the message. There is no need for manual intervention, which is flexible, reduces invalid configuration delivery, and increases the stability of the stacking system. In addition, the introduction of the shared message queue mechanism realizes the real-time cross-device configuration delivery, and can deliver configuration information to switch devices that need configuration updates. It also simplifies the complex message processing process of the stacking system, rather than requiring unified delivery of configuration information. Furthermore, the redisstream queue supports processing messages in the order of message IDs. Based on the message queue mechanism, it ensures the order of device configuration updates when a single switch device corresponds to multiple configuration messages. And through the publish-subscribe mechanism, it can automatically pull configuration information from the shared message queue, thereby automatically updating the configuration based on the newly added process calling the IMISH module.

[0059] In addition, a new process was added to call the IMISH module, which solved the problem that commands registered in the IMISH module could not be fully issued.

[0060] That is, the configuration delivery method in this switch stacking system is based on the Redis stream ordered message queue, which effectively overcomes the information interaction barrier across devices and processes, and newly establishes an imish_scfd process and a mechanism for adaptively adjusting and delivering device configurations, thereby ensuring the external consistency of the stacking system configuration, making the configuration management of the stacking system more efficient, flexible and reliable, and greatly increasing the stability and reliability of the stacking system.

[0061] Based on the same idea, some embodiments of the present application also provide devices and non-volatile computer storage media corresponding to the above methods.

[0062] Figure 4 A schematic diagram of a configuration delivery device for a switch stacking system provided in an embodiment of the present application includes:

[0063] at least one processor; and,

[0064] a memory communicatively connected to the at least one processor; wherein,

[0065] 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 so that the at least one processor can execute any one of the above-mentioned methods for sending configurations of a switch stacking system.

[0066] Some embodiments of the present application provide a non-volatile computer storage medium for sending configuration of a switch stacking system, which stores computer executable instructions. The computer executable instructions can execute any of the above-mentioned methods for sending configuration of a switch stacking system.

[0067] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0068] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the 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.

[0069] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented 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.

[0070] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0071] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0072] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

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

[0074] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0075] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0076] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0077] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the technical principle of the present application should all fall within the protection scope of the present application.

Claims

1. A method for issuing configuration of a switch stack 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 monitored push configuration information 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 the IMISH module; When determining that a configuration update needs to be performed based on the push configuration information, the second device determines an update order of the push configuration information based on the incremental identifier.

2. The method according to claim 1, characterized in that The first device parses the configuration command and generates push configuration information according to the parsed configuration information, specifically including: The first device parses the configuration command to obtain information to be configured, an execution role of the information to be configured, and port delivery information of the information to be configured, wherein the port delivery information includes a designated port of a designated device ID; Determine the execution device tag information of the information to be configured based on the execution role and port information issued; Generating a unique incremental identifier for the information to be configured; Generate push configuration information according to the information to be configured, the execution device tag information and the incremental identifier.

3. The method according to claim 2, characterized in that The step of sending information based on the execution role and the port to determine the execution device tag information of the information to be configured specifically includes: Matching the execution role in the switch stack system to obtain a first device to be configured; Matching the port sending information in the first device to be configured, and obtaining the second device to be configured when the match succeeds; According to the second device to be configured, execution device tag information of the information to be configured is determined.

4. The method according to claim 2, characterized in that: The method further comprises: If the port sending information fails to match in the first to-be-configured device, determining that the port sending information is empty; According to the first device to be configured, execution device tag information of the information to be configured is determined.

5. The method according to claim 2, characterized in that: The method further comprises: The second device compares the execution device tag information in the push configuration information with the device information of the local device; When the comparison is successful, it is determined that the local machine needs to perform a configuration update; When the comparison fails, it is determined that the machine does not need to perform a configuration update.

6. The method according to claim 1, characterized in that The switch device in the switch stacking system includes a newly added process, an IMISH module, an IMI module and a PM module. After receiving the pushed configuration information monitored from the shared message queue through the newly added process, the method further includes: The second device calls the IMISH module through the newly added process and sends the push configuration information to the IMISH module; Parsing the push configuration information through the IMISH module, and sending the parsed push configuration information to the IMI module; The parsed configuration information is sent to the PM module through the IMI module, so that the configuration update is performed through the PM module.

7. The method according to claim 6, characterized in that 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 the IMI module through the IMISH module, and the push configuration information is published to the shared message queue through the IMI module.

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

9. A configuration issuing device for a switch stacking system, characterized in that: include: at least one processor; as well as, a memory communicatively connected to 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 so that the at least one processor can execute the configuration delivery method for a switch stacking system as described in any one of claims 1 to 8.

10. A non-volatile computer storage medium for distributing configuration of a switch stack system, storing computer executable instructions, characterized in that: Applied to the second device, the computer executable instructions can execute the configuration delivery method for a switch stacking system as described in any one of claims 1 to 8.

Images