A method for distributing business software versions

Abstract

This application provides a method for distributing service software versions. The method includes: upon receiving version request messages from multiple service board CPUs, extracting the VLAN ID of the corresponding service board CPU from each version request message, wherein the VLAN ID is pre-assigned to each service board CPU by the main control unit; and transmitting the service software version to all requesting service board CPUs using multicast based on the extracted VLAN ID. This method constructs a logically isolated channel through VLAN technology and transmits the service software version to all requesting service board CPUs simultaneously using multicast, significantly improving version distribution efficiency, avoiding the main control unit becoming a performance bottleneck due to concurrent processing of a large number of version requests, and reducing the time required for system startup and service recovery.

Description

Technical Field

[0001] This application relates to the field of network communication technology, and in particular to a method for distributing business software versions. Background Technology

[0002] In chassis-based network devices, the CPU of the service board uses an independent version of the service software. In traditional solutions, the service board is typically equipped with a network port and a serial port, obtaining the service software version during startup via the management port or network port: a network cable is used to connect the computer and the service board, and the version file is transferred from the computer to the service board using protocols such as FTP (File Transfer Protocol) or TFTP (Trivial File Transfer Protocol). However, with hardware upgrades and increasingly compact panel layouts, there is no longer enough space to reserve network ports and serial ports. Furthermore, when there are a large number of service boards in the device, if multiple service boards start simultaneously, loading the service software version for each service board's CPU individually is extremely time-consuming. Summary of the Invention

[0003] This application provides a method for distributing service software versions to solve the following technical problem: In traditional solutions, when multiple service boards of a chassis network device start up simultaneously, the service software version is loaded one by one for each service board CPU, resulting in low startup efficiency.

[0004] Specifically, this application provides the following technical solution: In a first aspect, this application provides a method for distributing service software versions, the method being applied to the main control unit of a chassis network device, the method comprising: When receiving version request messages from multiple service board CPUs, the VLAN ID of the corresponding service board CPU is extracted from each version request message, wherein the VLAN ID is pre-assigned to each service board CPU by the main control unit; Based on the extracted VLAN ID, the service software version is transmitted to the CPU of all requesting service boards using multicast.

[0005] Secondly, this application provides a service software version distribution method, the method being applied to the service board CPU of a chassis network device, the method comprising: Send a version request message carrying its own VLAN ID to the main control unit. The VLAN ID is pre-assigned to the service board CPU by the main control unit so that the main control unit can perform the following steps: when receiving version request messages from multiple service board CPUs, extract the VLAN ID of the corresponding service board CPU from each version request message, and transmit the service software version to all service board CPUs requesting the version using multicast based on the extracted VLAN ID.

[0006] Thirdly, this application provides a main control unit applied to a chassis network device, the main control unit comprising: The extraction module is used to extract the VLAN ID of the corresponding service board CPU from each version request message when receiving version request messages from multiple service board CPUs, wherein the VLAN ID is pre-assigned to each service board CPU by the main control unit; The transmission module is used to transmit the service software version to all requesting service board CPUs using multicast based on the extracted VLAN ID.

[0007] Fourthly, this application provides a service board CPU for use in a chassis-type network device, the service board CPU comprising: The sending module is used to send a version request message carrying its own VLAN ID to the main control unit. The VLAN ID is pre-assigned by the main control unit to the service board CPU, so that the main control unit can perform the following steps: when receiving version request messages from multiple service board CPUs, extracting the VLAN ID of the corresponding service board CPU from each version request message, and transmitting the service software version to all requesting service board CPUs in a multicast manner according to the extracted VLAN ID.

[0008] Fifthly, this application provides a chassis network device, which includes a main control unit and multiple service board CPUs, wherein the main control unit is used to implement the method described above.

[0009] The technical solution provided in this application has the following beneficial effects: In this application, the main control unit pre-assigns a unique VLAN ID to each CPU of each service board. During startup, each service board CPU sends a version request message carrying its own VLAN ID to the main control unit. When the main control unit receives version request messages from multiple service board CPUs, it extracts the VLAN ID from the message, determines the recipient of the service software version based on the extracted VLAN ID, and finally transmits the service software version to all requesting service board CPUs via multicast. Compared to the traditional method of distributing one by one, this method can send the service software version to multiple service board CPUs simultaneously, significantly improving version distribution efficiency and effectively shortening the overall time for system startup and service recovery.

[0010] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0011] The accompanying drawings, which are incorporated in and form part of this application, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0012] Figure 1 A flowchart illustrating a business software version distribution method applied to a main control unit, as provided in an embodiment of this application; Figure 2 This is a schematic diagram of the structure of a chassis-type network device provided in an embodiment of this application; Figure 3 This is a schematic diagram of VLAN partitioning provided in an embodiment of this application; Figure 4 A flowchart illustrating a service software version distribution method applied to a service board CPU, as provided in an embodiment of this application. Detailed Implementation

[0013] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application.

[0014] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used herein are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the corresponding listed items.

[0015] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0016] This application relates to a chassis-type network device, the structure of which includes a chassis, interface motherboards, interface boards, a main control unit, and service boards. To improve networking flexibility, both the interface boards and service boards adopt a daughter card design and can be plugged into the interface motherboards. Each chassis supports up to 16 interface motherboards, each motherboard can install 2 service boards, and each service board can be configured with a single CPU or dual CPUs.

[0017] In practical applications, the main control unit and the interface motherboard share the same system software version, while the CPU on the service board uses an independent service software version. The service software version refers to a dedicated firmware or software image that runs independently on the service board CPU, is responsible for specific security service processing, and is separate from the main control system software.

[0018] In this application, the business software version is stored in the non-volatile memory (Flash) built into the main control unit. During the startup process, the business board will actively request the corresponding business software version from the main control unit and complete the loading and startup.

[0019] The technical solution and its beneficial effects of this application will be described in detail below through specific embodiments.

[0020] This application provides a method for distributing business software versions, applied to the main control unit of a chassis network device (such as a chassis firewall). Figure 1 As shown, the method may include the following steps: Step 110: When receiving version request messages from multiple service board CPUs, extract the VLAN ID of the corresponding service board CPU from each version request message, wherein the VLAN ID is pre-assigned to each service board CPU by the main control unit. Step 120: Based on the extracted VLAN ID, transmit the service software version to the CPU of all requesting service boards using multicast.

[0021] In practical applications, when a chassis-based network device powers on or a service board is inserted into a chassis slot and powered on, each CPU on that service board (including single-CPU or dual-CPU configurations) will first run its bootloader (BootROM / U-Boot). After the bootloader completes basic hardware initialization, the service board CPU obtains the corresponding service software version from the main control unit to complete subsequent startup. To this end, the service board CPU constructs and sends a version request message to the main control unit.

[0022] When the main control unit receives version request messages from multiple service board CPUs, it executes step 110, which involves extracting the VLAN ID (Virtual Local Area Network Identifier) ​​of the corresponding service board CPU from each version request message. This VLAN ID is a unique identifier pre-assigned by the main control unit to each service board CPU during system initialization or service board insertion. Through this VLAN ID, the main control unit can logically distinguish between different service board CPUs.

[0023] Subsequently, the main control unit executes step 120, transmitting the service software version to all requesting service board CPUs using multicast based on the extracted VLAN IDs. Specifically, the main control unit maintains a multicast group containing the VLAN IDs of all service board CPUs that have sent version requests but have not yet completed version loading. When the main control unit is ready to send the service software version, it sends data using the address of this multicast group as the destination address, ensuring that all service board CPUs belonging to this multicast group can receive the service software version.

[0024] Compared to the traditional method where the main control unit unicasts service software versions to each service board CPU one by one, this embodiment uses multicast, which effectively reduces the number of connections between the main control unit and the service board CPUs. This avoids the main control unit becoming a transmission bottleneck due to concurrently processing a large number of version requests. Especially in high-density service board scenarios (e.g., when the chassis is fully equipped with 16 interface motherboards, each motherboard has 2 service boards, and each service board is configured with dual CPUs, totaling 64 CPUs), it significantly improves version distribution efficiency and reduces system startup and service recovery time. Furthermore, since the version request message does not include the VLAN ID pre-assigned by the main control unit, the main control unit does not need to perform complex device discovery or address resolution during the response process, further simplifying the version distribution process and improving system reliability and maintainability.

[0025] Optionally, before receiving version request messages from multiple service board CPUs, the main control unit also performs VLAN ID allocation. Specifically, VLAN IDs are allocated to the service board CPUs in the following ways: an independent VLAN range is defined for each service slot; for each service slot, within the VLAN range of that service slot, each service board CPU in that service slot is assigned its own VLAN ID.

[0026] In other words, before receiving a version request message, the master control unit first assigns a VLAN ID to each service board CPU. During allocation, the master control unit divides the VLAN range according to the service slot, with each slot corresponding to an independent VLAN interval, and the VLAN intervals of different slots do not overlap. Then, for each service board CPU installed in a slot, the master control unit assigns a unique VLAN ID to each CPU from the VLAN interval corresponding to that slot. Subsequently, the master control unit uses the VLAN ID to distinguish and communicate with all service board CPUs.

[0027] In this way, the VLAN ID can reflect the slot location of the CPU and remain unique globally. When the master control unit receives a version request message, it can directly know which CPU in which slot is requesting the version based on the VLAN ID, which facilitates rapid response and multicast distribution.

[0028] Furthermore, the main control unit divides the VLAN range for each service slot in the following way: according to the preset rules, the VLAN range of the service slot is calculated based on the slot number of each service slot.

[0029] In other words, the main control unit calculates the VLAN range of each service slot based on the slot number using preset rules, thereby dividing each slot into non-overlapping and continuous VLAN ranges. For example, the starting VLAN ID can be set to 1024, and 10 VLAN IDs can be reserved for each slot. Then, the VLAN range of slot n is from 1024+(n-2)*10 to 1024+(n-1)*10-1, thus establishing a deterministic mapping between slots and VLAN ranges.

[0030] This slot-based VLAN range allocation method allows the main control unit to allocate a new VLAN ID within the VLAN range corresponding to the current slot when adding a new service board, without adjusting the existing configuration. This supports dynamic expansion in hot-swappable scenarios. Furthermore, the mapping relationship between VLAN IDs, slots, and CPUs is clear and explicit, facilitating quick problem identification by maintenance personnel and reducing maintenance costs.

[0031] Optionally, before transmitting the business software version to all requesting business board CPUs using multicast, the main control unit also performs the following steps: replying with an acknowledgment message to all requesting business board CPUs using unicast.

[0032] In practical applications, before the main control unit officially distributes the service software version via multicast, it can first reply with a confirmation message in unicast to each service board CPU that has sent a version request. This is to inform the other party that the version is ready and multicast transmission will begin soon, thereby avoiding the service board CPU from repeatedly sending requests due to waiting timeouts, reducing redundant messages in the network, and improving the reliability and synchronization of the version distribution process.

[0033] Optionally, the main control unit may transmit the business software version to all requesting business board CPUs via multicast in the following manner: by using multicast and transmitting the business software version to all requesting business board CPUs via out-of-band channels.

[0034] In other words, the main control unit performs multicast transmission through an out-of-band channel (a link formed by the control chip on the motherboard connecting the service board and the main control unit) independent of the service data channel. This out-of-band channel approach isolates version distribution traffic from service forwarding traffic, preventing version transmission from consuming service bandwidth. It also reduces the impact of version distribution on service processing performance, ensuring stable service traffic transmission during version upgrades or restarts, and further improving the reliability and stability of version distribution.

[0035] Optionally, the main control unit may also perform the following steps: upon receiving a version request message from a single service board CPU, extracting the VLAN ID of the service board CPU from the version request message; and transmitting the service software version to the service board CPU currently requesting the version based on the extracted VLAN ID.

[0036] In other words, the master control unit can also respond to version request messages from individual service board CPUs based on VLAN IDs. This method is suitable for situations where a service board CPU needs to be restarted individually, hot-swapped, or reloaded due to version anomalies, and can complement the multicast method.

[0037] Figure 2 This is an example of a device structure. Figure 2In the chassis, there are two main control slots (slot0 and slot1) and three service slots (slot2 to slot4). Each service slot has an interface motherboard. Slot2 and slot3 each have two service boards (service board 1 and service board 2) connected to the interface motherboard. Slot4 has one service board (service board 1) connected to the interface motherboard. Each service board contains two CPUs (CPU1 and CPU2). Each service board CPU needs to load the service software version.

[0038] The following is based on Figure 2 Using the device structure shown as an example, the VLAN segmentation process will be explained.

[0039] The main control unit first divides the VLAN range from slot 2 to slot n according to the service slot number of the chassis. The division rule is: the VLAN range of slot n is from 1024+(n-2)*10 to 1024+n-1)*10-1. Therefore, as Figure 3 As shown, the VLAN range for slot 2 is 1024~1033, the VLAN range for slot 3 is 1034~1043, and the VLAN range for slot 4 is 1044~1053.

[0040] Next, VLAN IDs are assigned to the CPUs of each service board based on their slot. For example, the VLAN range for slot 2 is 1024 to 1033. Figure 3 As shown, VLAN IDs 1024, 1025, 1026, and 1027 are assigned to the four service board CPUs on slot2. Similarly, VLAN IDs 1034, 1035, 1036, and 1037 are assigned to the four service board CPUs on slot3, and VLAN IDs 1044 and 1045 are assigned to the two service board CPUs on slot4.

[0041] When the device restarts, after the service boards in slots 2, 3, and 4 are in place, the CPU of each service board sends a version request message to the main control unit. The message format is as follows: # Layer 2 Ethernet header (12 bytes), the first 6 bytes are the destination MAC address, and the last 6 bytes are the source MAC address. 00 1A 2B 3C 4D 5E 00 AA BB CC DD EE # VLAN tag (4 bytes: TPID=8100 + TCI=000A → VLAN ID=10) 81 00 00 0A # Layer 3 Protocol Type (2 bytes: identifies IPv4) 08 00 # Data field (n bytes) xxxx xxxx The main control unit responds to all version request messages by unicasting to reply to the CPU of each service board. Then, it encapsulates the service software version to be transmitted with the corresponding VLAN tag and sends it to the service board through the out-of-band channel to achieve the multicast effect.

[0042] As can be seen from the above technical solution, this application utilizes VLAN technology to create a slot- and CPU-granular logical isolation channel for business software version transmission tasks within the internal switching architecture of a chassis network device. Specifically, when the device restarts, a service board restarts, or a new service board is inserted into a slot, each CPU on the service board sends a version request message carrying its own VLAN ID to the main control unit. After receiving the request, the main control unit determines the recipient of the business software version based on the VLAN ID, first returning an acknowledgment message to all service board CPUs that require the version, and then simultaneously transmitting the business software version to all service board CPUs that require the version via multicast to support the loading and startup of the service boards. Afterwards, each service board CPU loads the business software version, achieving parallel startup.

[0043] This application achieves the following beneficial effects: By pre-assigning VLAN IDs to each service board CPU through the main control unit and transmitting service software versions in parallel using multicast, compared to the traditional one-to-one unicast distribution method, it can send versions to multiple service board CPUs simultaneously, effectively shortening the overall time for system startup and service recovery. Especially in high-density scenarios where chassis equipment is fully equipped with multiple service boards and each service board is configured with multiple CPUs, it can significantly improve version distribution efficiency.

[0044] In summary, this application, while ensuring the accuracy of version distribution, constructs a logically isolated channel through VLAN technology and combines a multicast and unicast collaborative distribution strategy to achieve efficient, reliable, and scalable distribution of service software versions in chassis network devices, effectively improving the operation and maintenance efficiency and service stability of devices in complex networking environments.

[0045] This application also provides a method for distributing service software versions, which is applied to the service board CPU of a chassis network device. For example... Figure 4 As shown, the method includes the following steps: Step 410: Send a version request message carrying its own VLAN ID to the main control unit. The VLAN ID is pre-assigned to the service board CPU by the main control unit so that the main control unit can perform the following steps: when receiving version request messages from multiple service board CPUs, extract the VLAN ID of the corresponding service board CPU from each version request message, and transmit the service software version to all requesting service board CPUs in a multicast manner according to the extracted VLAN ID. Step 420: Receive the business software version transmitted to the local machine by the main control unit via multicast.

[0046] Specifically, the main control unit pre-assigns VLAN IDs to each service board CPU. When a service board starts up, the main control unit sends the pre-assigned VLAN IDs to each CPU of that service board. Then, the service board CPU sends a version request message carrying its own VLAN ID to the main control unit.

[0047] Based on the same inventive concept, this application provides a main control unit applied to a chassis-type network device. The main control unit includes: The extraction module is used to extract the VLAN ID of the corresponding service board CPU from each version request message when receiving version request messages from multiple service board CPUs, wherein the VLAN ID is pre-assigned to each service board CPU by the main control unit; The transmission module is used to transmit the service software version to all requesting service board CPUs using multicast based on the extracted VLAN ID.

[0048] Optionally, the main control unit further includes: The slot allocation module is used to allocate independent VLAN ranges for each service slot; The CPU partitioning module is used to assign a VLAN ID to each CPU board on each service slot within the VLAN range of that service slot.

[0049] Optionally, the slot allocation module allocates independent VLAN ranges for each service slot in the following ways: According to preset rules, the VLAN range of each service slot is calculated based on the slot number of each service slot.

[0050] Optionally, the main control unit further includes: The confirmation module is used to send confirmation messages to all requesting versions of the service board CPUs via unicast. Optionally, the transmission module specifically transmits the service software version to all requesting service board CPUs using multicast in the following manner: The business software version is transmitted to all requesting business board CPUs via out-of-band channel using multicast. Optionally, the extraction module is further configured to extract the VLAN ID of the service board CPU from the version request message when a version request message is received from a single service board CPU; The transmission module is also used to transmit the service software version to the CPU of the service board that is currently requesting the version, based on the extracted VLAN ID.

[0051] The apparatus provided in this application is used to perform the corresponding method described above. Therefore, the beneficial effects it can achieve can be referred to the beneficial effects of the corresponding method described above, and will not be repeated here.

[0052] This application also provides a service board CPU for use in a chassis-type network device. The service board CPU includes: The sending module is used to send a version request message carrying its own VLAN ID to the main control unit. The VLAN ID is pre-assigned by the main control unit to the service board CPU, so that the main control unit can perform the following steps: when receiving version request messages from multiple service board CPUs, extracting the VLAN ID of the corresponding service board CPU from each version request message, and transmitting the service software version to all requesting version service board CPUs in a multicast manner according to the extracted VLAN ID. The receiving module is used to receive the business software version transmitted to the local machine by the main control unit via multicast.

[0053] This application also provides a chassis network device, which includes a main control unit and multiple service board CPUs. The main control unit is used to implement the service software version distribution method applied to the main control unit as described above, and the service board CPUs are used to implement the service software version distribution method applied to the service board CPUs as described above.

[0054] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0055] The specific implementation process of the functions and roles of each unit / module in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0056] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units / modules described as separate components may or may not be physically separate. The components shown as units / modules may or may not be physical units / modules, that is, they may be located in one place or distributed across multiple network units / modules. Some or all of the units / modules can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0057] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method for distributing business software versions, characterized in that, The method is applied to the main control unit of a chassis network device, and the method includes: When receiving version request messages from multiple service board CPUs, the VLAN ID of the corresponding service board CPU is extracted from each version request message, wherein the VLAN ID is pre-assigned to each service board CPU by the main control unit; Based on the extracted VLAN ID, the service software version is transmitted to the CPU of all requesting service boards using multicast.

2. The method according to claim 1, characterized in that, Before receiving version request messages from multiple service board CPUs, the method further includes: Each service slot should be assigned an independent VLAN range; For each service slot, within the VLAN range of that service slot, assign a VLAN ID to the CPU of each service board on that service slot.

3. The method according to claim 2, characterized in that, The method specifically divides each service slot into independent VLAN ranges in the following way: According to preset rules, the VLAN range of each service slot is calculated based on the slot number of each service slot.

4. The method according to claim 1, characterized in that, Before using multicast to transmit the business software version to all requesting business board CPUs, the following steps are also included: A unicast method is used to send a confirmation message to all requesting version of the service board CPU.

5. The method according to claim 1, characterized in that, The method specifically transmits the business software version to all requesting business board CPUs using multicast in the following manner: The business software version is transmitted to all requesting business board CPUs via out-of-band channels using multicast.

6. The method according to claim 1, characterized in that, The method further includes: Upon receiving a version request message from a single service board CPU, the VLAN ID of the service board CPU is extracted from the version request message; Based on the extracted VLAN ID, the service software version is transmitted to the CPU of the service board that is currently requesting the version.

7. A method for distributing business software versions, characterized in that, The method is applied to the service board CPU of a chassis network device, and the method includes: Send a version request message carrying its own VLAN ID to the main control unit. The VLAN ID is pre-assigned to the service board CPU by the main control unit so that the main control unit can perform the following steps: when receiving version request messages from multiple service board CPUs, extract the VLAN ID of the corresponding service board CPU from each version request message, and transmit the service software version to all service board CPUs requesting the version using multicast based on the extracted VLAN ID.

8. A main control unit, characterized in that, Applied to chassis-type network devices, the main control unit includes: The extraction module is used to extract the VLAN ID of the corresponding service board CPU from each version request message when receiving version request messages from multiple service board CPUs, wherein the VLAN ID is pre-assigned to each service board CPU by the main control unit; The transmission module is used to transmit the service software version to all requesting service board CPUs using multicast based on the extracted VLAN ID.

9. The main control unit according to claim 8, characterized in that, The main control unit also includes: The slot allocation module is used to allocate independent VLAN ranges for each service slot; The CPU partitioning module is used to assign a VLAN ID to each CPU board on each service slot within the VLAN range of that service slot.

10. The main control unit according to claim 9, characterized in that, The slot allocation module specifically allocates independent VLAN ranges for each service slot in the following ways: According to preset rules, the VLAN range of each service slot is calculated based on the slot number of each service slot.

11. The main control unit according to claim 8, characterized in that, The main control unit also includes: The confirmation module is used to send confirmation messages to all requesting versions of the service board CPUs via unicast. And / or, The transmission module specifically transmits the business software version to all requesting business board CPUs using multicast in the following manner: The business software version is transmitted to all requesting business board CPUs via out-of-band channel using multicast. And / or, The extraction module is further configured to extract the VLAN ID of the service board CPU from the version request message when a version request message is received from a single service board CPU; The transmission module is also used to transmit the service software version to the CPU of the service board that is currently requesting the version, based on the extracted VLAN ID.

12. A service board CPU, characterized in that, The service board CPU, used in chassis-type network devices, includes: The sending module is used to send a version request message carrying its own VLAN ID to the main control unit. The VLAN ID is pre-assigned by the main control unit to the service board CPU, so that the main control unit can perform the following steps: when receiving version request messages from multiple service board CPUs, extracting the VLAN ID of the corresponding service board CPU from each version request message, and transmitting the service software version to all requesting service board CPUs in a multicast manner according to the extracted VLAN ID.

13. A chassis-type network device, characterized in that, The chassis network device includes a main control unit and multiple service board CPUs, wherein the main control unit is used to implement the method as described in any one of claims 1 to 6.

Images