Service switching method, electronic equipment, medium and product

Abstract

The embodiment of the invention provides a service switching method, electronic equipment, a medium and a product, the method is applied to a first primary main control board and comprises the steps that a first synchronous port message of a first non-primary main control board is received, the first non-primary main control board and the first primary main control board are both located in first member stacking equipment, and a first synchronous port message of a second non-primary main control board is received; the first synchronous port message carries port connection information and port configuration information of each cascade port of the first non-primary main control board; determining the state of each management link corresponding to the first stacking member equipment according to the port connection information and the port configuration information of the first synchronization port message; and in response to all the management link faults, sending a link collective fault notification to a stacking management module, and switching the service to target stacking member equipment. The embodiment of the invention aims to improve the network stability when the stacking equipment is faced with the management link abnormity.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a service switching method, electronic device, medium, and product. Background Art

[0002] VSC (Virtual Switch Cluster) stacking is a network virtualization technology that combines multiple independently functioning physical devices into a single virtual device. These separate physical devices are linked together using stacking boards. The VSC stacking connection links are divided into two parts: management links and forwarding links.

[0003] Related technologies detect service connectivity to determine whether a stack's management links are collectively faulty. However, if a stack split and service switchover are performed only after service connectivity is established, the service may already be faulty, leading to network instability. Improving network stability is a pressing issue that needs to be addressed and resolved. Summary of the Invention

[0004] The embodiments of the present application provide a service switching method, electronic device, medium, and product, which are intended to improve network stability when a stacking device faces management link anomalies.

[0005] In the first aspect, an embodiment of the present application provides a service switching method, which is applied to a first master main control board, and the method includes: receiving a first synchronization port message from a first non-master main control board, wherein the first non-master main control board and the first master main control board are both located in a first stack member device, and the first synchronization port message carries the port connection information and port configuration information of each cascade port of the first non-master main control board; determining the status of each management link corresponding to the first stack member device based on the port connection information and the port configuration information of the first synchronization port message; in response to a failure of all the management links, sending a link collective failure notification to the stack management module, and switching the service to the target stack member device.

[0006] In a second aspect, an embodiment of the present application provides an electronic device comprising: at least one processor; at least one memory for storing at least one program; and a service switching method as described in the first aspect is implemented when at least one of the programs is executed by at least one of the processors.

[0007] In a third aspect, an embodiment of the present application provides a computer program product, comprising a computer program or computer instructions, characterized in that the computer program or the computer instructions are stored in a computer-readable storage medium, a processor of a computer device reads the computer program or the computer instructions from the computer-readable storage medium, and the processor executes the computer program or the computer instructions, so that the computer device performs the service switching method described in the first aspect.

[0008] The embodiment of the present application synchronizes the cascade port related information between the main control board and the non-main control board through synchronous port messages, so that the main control board can identify the status of each cascade port of the stack member device in which it is located, and thus determine the status of each management link based on the status of each cascade port. By directly detecting the management link status through the cascade port status, the main control board can directly perceive the collective failure of the management link and perform stack splitting and service switching. There is no need to detect the service connectivity and wait until the services are different to determine the collective failure of the management link. Through the above method, it is possible to quickly and proactively identify the management link failure of the stacking device and proactively switch the service. There is no need to switch after the service abnormality occurs, which effectively reduces the instability of the stacking device when facing management link abnormalities and improves the user's network usage perception.

[0009] Other features and advantages of the present application will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present application. The purposes and other advantages of the present application can be achieved and obtained through the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A schematic diagram of a communication network used by the service switching method provided in one embodiment of the present application;

[0011] Figure 2 A schematic diagram of a VSC stacking device used in a service switching method provided in an example of the present application;

[0012] Figure 3 A flowchart of a service switching method provided in one embodiment of the present application;

[0013] Figure 4 A schematic diagram of the structure of a service switching device provided in one embodiment of the present application;

[0014] Figure 5 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0015] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0016] It should be noted that although the device schematics illustrate functional module divisions and the flowcharts illustrate logical sequences, in certain circumstances, the steps shown or described may be performed in a sequence that differs from the module divisions in the device or the sequence in the flowcharts. The terms "first," "second," and so on, in the specification, claims, and drawings, are used to distinguish similar items and are not necessarily used to describe a specific sequence or precedence.

[0017] In the description of the embodiments of the present application, unless otherwise clearly defined, terms such as setting, installing, and connecting should be understood in a broad sense. Technical personnel in the relevant technical field can reasonably determine the specific meanings of the above terms in the embodiments of the present application based on the specific content of the technical solution.

[0018] In the embodiments of the present application, words such as "further," "exemplarily," or "optionally" are used to indicate examples, illustrations, or descriptions and should not be interpreted as being more preferred or advantageous over other embodiments or designs. The use of words such as "further," "exemplarily," or "optionally" is intended to present related concepts in a concrete manner.

[0019] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Wideband Code Division Multiple Access (WCDMA) mobile communication system, Evolved Universal Terrestrial Radio Access Network (E UTRAN) system, Next Generation Radio Access Network (NG RAN) system, Long Term Evolution (LTE) system, Worldwide Interoperability For Microwave Access (WiMAX) communication system, fifth generation (5G) system, such as new generation radio access technology (NR), and future communication systems such as 6G system.

[0020] The technical solutions of the embodiments of the present application can be applied to various communication technologies, such as microwave communication, optical wave communication, millimeter wave communication, etc. The embodiments of the present application do not limit the specific technologies and specific device forms used.

[0021] VSC stacking is a network virtualization technology that combines multiple independently functioning physical devices into a single virtual device. These individual physical devices are linked together via stacking boards. They discover each other through a topology discovery protocol and, through a specific mechanism, elect a master device. The other devices then assume the forwarding role. The VSC stacking connection links are divided into two parts: a management link and a forwarding link. The management link forwards stacking system management and control plane maintenance messages; the forwarding link forwards service data messages across the stacking system.

[0022] In related technologies, in order to perceive the status of various links, the connectivity status of services is usually used to indirectly perceive whether the corresponding link status is normal. Judging the link status based on the result (service status) is more convenient and more in line with mainstream thinking. However, by testing whether the service can be connected to determine whether the management links of the stacked devices are collectively faulty, when the service is not connected and the management links are collectively abnormal, and then the stack is split and the service is switched, the service may have already been abnormal, resulting in network instability. How to improve network stability is an issue that urgently needs to be discussed and resolved.

[0023] In order to solve the above problems, the embodiments of the present application provide a service switching method, electronic device, medium and product, which synchronizes the cascade port related information between the main control board and the non-main control board through synchronous port messages, so that the main control board can identify the status of each cascade port of the stack member device in which it is located, and thus determine the status of each management link based on the status of each cascade port. By directly detecting the management link status through the cascade port status, the main control board can directly perceive the collective failure of the management link and perform stack splitting and service switching; there is no need to detect the service connectivity and wait until the service is different to determine the collective failure of the management link. Through the above method, it is possible to quickly and proactively identify the management link failure of the stacking device and actively perform service switching. There is no need to switch after the service abnormality occurs, which effectively reduces the instability of the stacking device when facing management link abnormalities and improves the user's network usage perception.

[0024] The embodiments of the present application are further described below with reference to the accompanying drawings.

[0025] Figure 1 Schematic diagram of a communication network used by the service switching method provided in an embodiment of the present application. Figure 1 As shown, the communication network includes but is not limited to at least a network device 110 , a user device 120 , and a stacking device 130 .

[0026] Network device 110 is a dedicated hardware device used to interconnect various nodes such as servers, PCs, and user devices to form an information communication network. For example, network device 110 may be a base station, a building baseband unit (BBU), a remote radio unit (RRU), or customer premises equipment (CPE). Network device 110 wirelessly communicates with user devices 120 to exchange data.

[0027] User devices 120 are devices that provide various functions, including communication and network services. User devices 120 include industrial robots, cameras, desktop computers, laptops, PDAs (personal digital assistants), mobile phones, in-vehicle user devices, home theater user devices, and dedicated user devices. They can be single devices or a collection of multiple devices. For example, multiple devices connected via a local area network and sharing a common display device can collectively constitute a user device. User devices 120 can also establish a communication connection with network device 110 to exchange data.

[0028] VSC stacking device 130 virtualizes multiple physical network devices, i.e., multiple stack member devices (e.g., switches and routers), into a single logical device to provide high port density, high-speed forwarding, high reliability, and simplified management. In some embodiments, VSC stacking device 130 can communicate with network device 110 to exchange data via wired or wireless communication.

[0029] Figure 2 A schematic diagram of a VSC stacking device applied to a service switching method provided in an example of the present application.

[0030] For example, Figure 2 As shown, Frame 0 and Frame 1 are two separate network elements in the VSC stacking device, i.e., the stacking member devices that make up the VSC stacking device. Each stacking member device is provided with slot 1 and slot 2, respectively. Each slot corresponds to a main control board, and each main control board is provided with cascade port 1 and cascade port 2, respectively. For the entire VSC stacking device, the master switch controller (MSC) is the main controller of the VSC stacking device, the standby switch controller (SSC) is the standby controller of the VSC stacking device, and the remaining two main control boards are non-active (NA) main controllers of the VSC stacking device. The two main control boards in the same frame are connected by a backplane.

[0031] For example, taking the active main control board and the inactive main control board in frame 1 as an example, the active main control board receives the synchronous port message from the non-active main control board (i.e., the inactive main control board), and the synchronous port message carries the port connection information and port configuration information of the cascade ports 1 and 2 of the non-active main control board.

[0032] The master main control board determines the status of each management link corresponding to the stack member device based on the port connection information and port configuration information in the synchronous port message. For example, the master main control board obtains the port-related information of cascade ports 1 and 2 of the non-master main control board through the synchronous port message. Combined with the port-related information of its own cascade ports 1 and 2, the master main control board knows the port information of all four cascade ports of frame 1. The master main control board can determine whether the corresponding management link is abnormal based on whether the four cascade ports are abnormal.

[0033] In response to all management link failures, the active main control board sends a collective link failure notification to the stack management module, switching services to the target stack member device. For example, the target stack member device can be specified by the stack management module or determined by the active main control board of block 1 based on the cascade port information of other blocks.

[0034] For example, the standby main control board and the inactive main control board in block 0 may also synchronize the port-related information of the cascade ports through synchronous port messages.

[0035] For example, the main control boards of block 0 and block 1 can also synchronize the port-related information of the cascade ports through synchronous port messages.

[0036] In the above example, the cascade port related information between the active main control board and the non-active main control board is synchronized through synchronous port messages, so that the active main control board can identify the status of each cascade port of the stack member device in which it is located, and thus determine the status of each management link based on the status of each cascade port. By directly detecting the management link status through the cascade port status, the active main control board can directly perceive the collective failure of the management link and perform stack splitting and service switching; there is no need to detect the service connectivity and wait until the service is different to determine the collective failure of the management link. Through the above method, it is possible to quickly and proactively identify the management link failure of the stacking device and proactively switch the service. There is no need to switch after the service abnormality occurs, which effectively reduces the instability of the stacking device when facing management link abnormalities and improves the user's network usage perception.

[0037] Figure 3 This is a flow chart of a service switching method provided in an embodiment of the present application. The service switching method can be applied to, but is not limited to, the first main control board, or Figure 1The main control board in the VSC stacking device 130 provided, or Figure 2 The backup main control board of the provided frame 0 or the main control board of the provided frame 1. In this embodiment, the service switching method includes at least but is not limited to:

[0038] Step 310: Receive a first synchronization port message from a first non-master main control board, where the first non-master main control board and the first master main control board are both located in a first stack member device, and the first synchronization port message carries port connection information and port configuration information of each cascade port of the first non-master main control board;

[0039] Step 320: Determine the status of each management link corresponding to the first stack member device based on the port connection information and port configuration information of the first synchronous port message;

[0040] Step 330: In response to all management links failing, a collective link failure notification is sent to the stack management module, and the service is switched to the target stack member device.

[0041] In step 310, the first master main control board is the active main control board in the first stack member device, responsible for service processing, configuration management, and state synchronization; the first non-master main control board is the non-active main control board in the first stack member device. The first stack member device is a stacking frame in the VSC stack device.

[0042] The first synchronization port message is a message generated by the first non-master main control board based on the current port connection information and port configuration information of each of its cascade ports. For example, the first master main control board may also generate a synchronization port message based on the current port connection information and port configuration information of each of its cascade ports and send it to the first non-master main control board to synchronize its cascade port information. The port connection information and port configuration information will be described in detail in subsequent embodiments and are not detailed here.

[0043] For example, each main control board (including the master main control board and the non-master main control board) can periodically send synchronization port messages to other main control boards. Alternatively, when a main control board detects an abnormality in at least one of its cascade ports, it sends a synchronization port message to other main control boards to synchronize the current status of its cascade ports with the other main control boards.

[0044] In step 320, each stack member device has at least one management link. For example, assume that the non-active and active main control boards each have two cascade ports, and the stack member device has four cascade ports. In this case, the stack member device can configure the four cascade ports as one management link (in aggregate mode); group the four cascade ports into two groups, assigning them to two management links; or allocate each of the four cascade ports to four management links.

[0045] For example, the master main control board can sense the status of each of its own cascade ports. It can then obtain the port connection information and port configuration information of each cascade port on the corresponding non-master main control board through synchronous port messages, thereby understanding the status of each cascade port on the other side. At this point, the master main control board can know the status of all cascade ports on its stack member devices. The master main control board can determine whether the management link corresponding to the cascade port is abnormal based on whether the cascade port is abnormal.

[0046] For example, regardless of how the management links of a stack member device are configured, if all cascade ports of a stack member device are abnormal, all links associated with that stack member device will be abnormal. Therefore, in this embodiment, the master main control board can determine whether all management links are abnormal by determining whether all cascade ports of its stack member device are abnormal.

[0047] In step 330, the stack management module is a core component responsible for coordinating the stack member devices in the stack system and achieving unified management and control. The link collective failure notification is used to indicate that all management links related to the corresponding stack member devices have experienced an abnormality.

[0048] For example, after determining that all management links are faulty, the first active main control board reports a collective link failure notification to the stack management module. Upon receiving the collective link failure notification, the stack management module splits the stack and separates the first stack member device from the entire VSC stack device.

[0049] Illustratively, after receiving the notification of collective link failure, the stack management module will further issue a service switching instruction to the first active main control board, instructing the first active main control board to switch the service to the target stack member device.

[0050] For example, the target stack member device can be preconfigured or determined by the stack management module based on the current status of each stack member device. In one example, suppose a stack member device currently hosting a backup master controller experiences an abnormality and detects a failure in all management links and reports this to the stack management module. The stack management module can, by default, instruct the stack member device to switch services to the stack member device hosting the active master controller.

[0051] In the related art, the non-master main control board usually only receives the routing table and address table synchronized from the master main control board, or only when a failure occurs and the master-slave switch is performed, will it synchronize and obtain the complete configuration and forwarding table items from the new master main control board, but neither involves the non-master main control board actively sending synchronization messages about its own cascade ports to the master main control board. In the above steps 310 to 330, the cascade port related information between the master main control board and the non-master main control board is synchronized through the synchronization port message, so that the master main control board can identify the status of each cascade port of the stack member device where it is located, and thus determine the status of each management link based on the status of each cascade port. By directly detecting the status of the management link through the cascade port status, the master main control board can directly perceive the collective failure of the management link and perform stack splitting and service switching; there is no need to detect through service connectivity, and the collective failure of the management link is determined only when the services are different. Through the above method, it is possible to quickly and proactively identify management link failures of stacking devices and proactively switch services. There is no need to switch services after business anomalies occur. This effectively reduces the instability of stacking devices when facing management link anomalies and improves users' network usage experience.

[0052] The above is a general description of steps 310 to 330 . The specific implementation process of steps 310 to 330 and their extended steps will be described in detail below.

[0053] In one embodiment, the port connection information includes the frame information, slot information, and port number of the corresponding cascade port, as well as the frame information, slot information, and port number of the opposite cascade port; the port configuration information includes the hardware master status, Spanning Tree Protocol (STP) configuration status, and link establishment status.

[0054] In this embodiment, the chassis information, slot information, and port number of a cascade port refer to the port number of the cascade port, the slot information of the slot in which the main control board where the cascade port is located is inserted, and the chassis information of the stacking chassis where the main control board where the cascade port is located (i.e., stack member device information). The peer end refers to the other end of the management link to the cascade port.

[0055] After receiving the port connection information and port configuration information, the active main control board can further determine whether the corresponding cascade port can work normally based on the STP configuration status, link establishment status, hardware master status, etc., and then determine the corresponding management link and perform status judgment based on the port connection information.

[0056] In one embodiment, the first synchronous port message also includes a source physical location address, which includes the frame number, slot number, and board type of the frame where the corresponding main control board is located. The source physical location address can be used to trace the abnormal main control board, facilitating operation and maintenance management.

[0057] In one embodiment, the synchronous port message may be a BPDU (Bridge Protocol Data Unit) message. For example, the specific message format of the BPDU message is as follows:

[0058] Bytes 0-5 are the destination MAC address: 01-80-c2-00-00-02, which is the BPDU-specific destination address. This is an STP-specific multicast address and is processed only by devices that support the spanning tree protocol. Other devices will directly discard it.

[0059] Bytes 6-11 are the constructed source physical location address, which includes the chassis number, slot number, and board type of the chassis where the main control board is located.

[0060] Bytes 12-13 are the Ethernet header 0x8809. BPDUs are usually encapsulated in Ethernet frames for transmission.

[0061] Byte 14 indicates the message type. BPDU messages are classified into two types: synchronization messages and control messages. Synchronization messages are used to synchronize port information between boards, while control messages are used to carry port control information.

[0062] Byte 15 is the version number, 0 refers to STP;

[0063] Byte16 is the port number, which corresponds to the port that sends the message;

[0064] Byte 17 indicates whether the board is the main control board;

[0065] Bytes 18-106 are the port information of the cascade port, including port connection information and port configuration information.

[0066] In other examples, Byte 18-106 can also be the port information of each cascade port in the VSC stacking device. For example, assuming that the VSC stacking device is set with 2 stacking single frames, each stacking single frame is set with 2 main control boards, and each main control board is set with 2 cascade ports, then Byte 18-106 can carry the port information of these 8 cascade ports.

[0067] In one embodiment, two threads are deployed on both the active main control board and the non-active main control board, and the two threads are used to send and receive BPDU messages, respectively. Since the BPDU message in the embodiment of the present application contains port connection information and port configuration information, the status of the management link of the corresponding main control board can be determined based on the BPDU message. By deploying threads to synchronize port information, it is ensured that the status change of the management link of a single main control board can be synchronized to another main control board within the target time, so that the collective abnormality of the management link of the entire stacked single frame (i.e., stacked member devices) can be quickly identified on a single main control board, and service switching can be performed under abnormal scenarios.

[0068] In one embodiment, step 320 includes:

[0069] Determine the port status of each cascade port of the first non-master main control board according to the port connection information and port configuration information of the first synchronous port message;

[0070] The status of each management link corresponding to the first stack member device is determined according to the port status of each cascade port of the first non-master main control board and the port status of each cascade port of the main control board itself.

[0071] In one embodiment, before step 330, the method further includes:

[0072] In response to not receiving the first synchronous port message within a preset number of cycles, detecting whether each management link is faulty according to the locally stored status of each management link.

[0073] In this embodiment, the period is a preset time interval for sending / receiving synchronous port messages.

[0074] After receiving the synchronization port message, the master main control board determines the status of the non-master main control board's cascade ports based on the port connection information and port configuration information in the synchronization port message. Combined with the status of its own cascade ports, it can determine the status of each cascade port on its stack management device. The master main control board determines the status of each management link based on the status of each cascade port and saves the management link status locally.

[0075] If the active main control board fails to receive synchronous port messages for a preset number of cycles, it assumes a link failure. The system then uses the locally stored status of each management link to determine whether all management links are faulty. Setting the failure to receive synchronous port messages for multiple cycles as a status check trigger prevents false positives.

[0076] In one embodiment, step 330 includes:

[0077] In response to detecting all management link failures for a preset number of consecutive times, a collective link failure notification is sent to the stack management module, switching services to the target stack member device. For example, the preset number of times can be set to two. By setting a predicted number of times, occasional transmission jitter can be avoided and misjudgments can be prevented.

[0078] In one embodiment, step 330 includes: in response to all management links failing, sending a collective link failure notification to the stack management module; receiving a stack split notification issued by the stack management module in response to the collective link failure notification; and executing a stack split in accordance with the stack split notification, switching services to a target stack member device, wherein the target stack member device is determined by the stack management module. In this embodiment, the stack split notification is used to instruct the stack member devices to perform a stack split.

[0079] In one embodiment, the method further comprises:

[0080] receiving a second synchronization port message from a second active main control board and a third synchronization port message from a second non-active main control board, wherein the second active main control board and the second non-active main control board are both located in a second stack member device;

[0081] The status of each cascade port of the second stack member device is determined according to the second synchronous port message and the third synchronous port message.

[0082] In this embodiment, the second stacking member device refers to another stacking single frame in the VSC stacking device where the first stacking member device is located. The second master main control board refers to the active main control board in the second stacking member device, and the second non-master main control board refers to the non-active main control board in the second stacking member device. For example, it is assumed that the VSC stacking device is obtained by stacking the first stacking member device and the second stacking member device. At this time, one of the first master main control board and the second master main control board is the master main control of the entire VSC stacking device, and the other is the backup main control of the entire VSC stacking device.

[0083] The first master main control board of the first stack member device obtains the status of each cascade port of other stack member devices through synchronous port messages, so that it can perceive the management link status of other stack member devices related to it, and provide a decision-making basis when self-management maintenance such as service switching and anomaly detection is required.

[0084] In one embodiment, step 330 includes:

[0085] When the states of the cascade ports of the second stack member device are all normal, determining the second stack member device as the target stack member device;

[0086] Switch services to the target stack member device.

[0087] In this embodiment, the first master main control board of the first stack member device obtains the status of each cascade port of the second stack member device through synchronous port messages, so that the first master main control board can determine the management link status of the second stack member device. For example, when all the cascade ports of the first stack member device are abnormal, that is, all the related management links of the first stack member device itself are abnormal, but it is possible that all the cascade ports of the second stack member device are normal, that is, the management link between the second stack member device and the other stack member devices is normal. At this time, the first stack member device directly switches the service to the second stack member device based on the normal status of each cascade port of the second stack member device, so that the service between the second stack member device and the other stack member devices can continue to be processed normally. There is no need to wait for the stack management module to issue a service switching notification before switching, which further reduces the probability of service abnormalities and improves the user's network usage experience.

[0088] The service switching method of the present application is described in detail below by using an example. It is understood that the following embodiments are for the purpose of illustrating the service switching method of the present application and are not intended to be limiting.

[0089] For example, Figure 2 For example, the service switching process in the event of a collective failure of the stack management links in this example is as follows:

[0090] The active main control board and the inactive main control board of frame 1 synchronize the information of cascade ports 1 and 2 through synchronization port messages. The synchronized port information includes port connection information and port configuration information.

[0091] When all four cascade ports of the active main control board and the inactive main control board of frame 1 are abnormal, the active main control board of frame 1 can identify that all four cascade ports of frame 1 are abnormal based on the synchronized port connection information and port configuration information, as well as the status perception of its own cascade ports;

[0092] The active main control board of chassis 1, acting as the hardware master of this chassis, sends a message to the stack management module, notifying it that a stack split is required.

[0093] The stack management module issues a stack split notification, the stack device splits, and services are switched to the target stack frame.

[0094] In the above example, cascade port information is synchronized between the active and inactive main control boards through port synchronization messages. The active main control board can sense the status of all cascade ports on the stack member devices, thereby quickly and proactively identifying management link failures on the stack device and proactively switching services. This eliminates the need to wait for service anomalies before switching. This effectively reduces the instability of the stack device when facing management link anomalies and improves the user's network experience.

[0095] Figure 4 This is a schematic diagram of the structure of a service switching device provided in an embodiment of the present application. The service switching device 400 includes at least but is not limited to:

[0096] A message receiving unit 410 is configured to receive a first synchronization port message from a first non-master main control board, wherein the first non-master main control board and the first master main control board are both located in a first stack member device, and the first synchronization port message carries port connection information and port configuration information of each cascade port of the first non-master main control board;

[0097] A status determining unit 420, configured to determine the status of each management link corresponding to the first stack member device according to the port connection information and the port configuration information of the first synchronization port message;

[0098] The service switching unit 430 is configured to send a collective link failure notification to the stack management module in response to all management link failures, and switch services to a target stack member device.

[0099] Figure 5 Schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Figure 5 As shown, the electronic device 2000 includes a memory 2100 and a processor 2200. The number of the memory 2100 and the processor 2200 can be one or more. Figure 5 In the example, a memory 2101 and a processor 2201 are used; the memory 2101 and the processor 2201 in the network device can be connected via a bus or other means. Figure 5 The bus connection is taken as an example.

[0100] The memory 2101 is a computer-readable storage medium that can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the method provided in any embodiment of the present application. The processor 2201 implements the service switching method provided in any of the above embodiments by running the software programs, instructions, and modules stored in the memory 2101.

[0101] The memory 2101 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function. In addition, the memory 2101 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 2101 further includes a memory remotely located relative to the processor 2201, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0102] An embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the service switching method provided in any embodiment of the present application.

[0103] An embodiment of the present application also provides a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. The processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, so that the computer device executes the service switching method provided in any embodiment of the present application.

[0104] The system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0105] Those skilled in the art will appreciate that all or some of the steps in the methods, systems, and functional modules / units in the devices disclosed above may be implemented as software, firmware, hardware, or appropriate combinations thereof.

[0106] In a hardware implementation, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0107] As used in this specification, the terms "component," "module," "system," and the like are used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. By way of illustration, both applications running on a computing device and a computing device can be components. One or more components can reside in a process or execution thread, and a component can be located on one computer or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate, for example, through local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component on a local system, a distributed system, or a network, such as the Internet interacting with other systems via signals).

[0108] The above description of some embodiments of the present application with reference to the accompanying drawings does not limit the scope of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present application shall be within the scope of the present application.

Claims

1. A service switching method, characterized in that: Applied to a first master main control board, the method includes: Receive a first synchronization port message from a first non-active main control board, wherein the first non-active main control board and the first active main control board are both located in a first stack member device, and the first synchronization port message carries port connection information and port configuration information of each cascade port of the first non-active main control board; determining, according to the port connection information and the port configuration information of the first synchronous port message, a status of each management link corresponding to the first stack member device; In response to all the management links failing, a collective link failure notification is sent to the stack management module, and services are switched to the target stack member device.

2. The service switching method according to claim 1, wherein: The determining, according to the port connection information and the port configuration information of the first synchronous port message, the status of each management link corresponding to the first stack member device includes: determining, according to the port connection information and the port configuration information of the first synchronous port message, the port status of each cascade port of the first non-active main control board; The status of each management link corresponding to the first stack member device is determined according to the port status of each cascade port of the first non-master main control board and the port status of each cascade port of the first non-master main control board.

3. The service switching method according to claim 1, wherein: Before sending a collective link failure notification to the stack management module in response to all management link failures and switching services to the target stack member device, the method further includes: in response to not receiving the first synchronous port message within a preset number of cycles, detecting whether each of the management links is faulty based on the locally stored status of each of the management links; The response to all the management link failures, sending a link collective failure notification to the stack management module, and switching the service to the target stack member device includes: in response to all the management link failures being detected for a consecutive preset number of times, sending a link collective failure notification to the stack management module, and switching the service to the target stack member device.

4. The service switching method according to claim 1, wherein: The method further comprises: Receive a second synchronization port message of a second active main control board and a third synchronization port message of a second non-active main control board, wherein the second active main control board and the second non-active main control board are both located in a second stack member device; Determine the status of each cascade port of the second stack member device according to the second synchronous port message and the third synchronous port message.

5. The service switching method according to claim 4, characterized in that: The switching of the service to the target stack member device includes: When the states of the cascade ports of the second stack member device are all normal, determining the second stack member device as the target stack member device; Switch the service to the target stack member device.

6. The service switching method according to claim 1, wherein: In response to all the management link failures, sending a link collective failure notification to the stack management module and switching services to a target stack member device includes: In response to all of the management links failing, sending a collective link failure notification to the stack management module; receiving a stack split notification issued by the stack management module in response to the link collective failure notification; Perform stack splitting according to the stack splitting notification, and switch services to the target stack member device, wherein the target stack member device is determined by the stack management module.

7. The service switching method according to claim 1, wherein: The port connection information includes the frame information, slot information, and port number of the corresponding cascade port, as well as the frame information, slot information, and port number of the opposite cascade port; The port configuration information includes hardware main status, spanning tree protocol configuration status, and link establishment status.

8. The service switching method according to claim 1, wherein: The first synchronous port message also includes a source physical location address, and the source physical location address includes the frame number, slot number, and board type of the frame where the corresponding main control board is located.

9. An electronic device, characterized in that: include: at least one processor; at least one memory for storing at least one program; When at least one of the programs is executed by at least one of the processors, the method according to any one of claims 1 to 8 is implemented.

10. A computer program product comprising a computer program or computer instructions, characterized in that The computer program or the computer instructions are stored in a computer-readable storage medium, and the processor of the computer device reads the computer program or the computer instructions from the computer-readable storage medium. The processor executes the computer program or the computer instructions, so that the computer device performs the method according to any one of claims 1 to 8.

Images