CN114518891A - A single-board upgrade method, single-board device and computer-readable storage medium - Google Patents

Abstract

The embodiment of the invention provides a single board upgrading method, single board equipment and a computer readable storage medium, wherein the single board upgrading method is used for activating an obtained patch package; analyzing the patch package to obtain a single board parameter corresponding to the patch package; confirming a setting slot position of the single board to be upgraded corresponding to the patch package according to the single board parameters; and upgrading the single board to be upgraded according to the setting slot position, accurately identifying the effective range of the patch package, and executing upgrading operation.

Description

A single-board upgrade method, single-board device and computer-readable storage medium

technical field

The embodiments of the present invention relate to, but are not limited to, the field of communication devices, and specifically relate to, but are not limited to, a single-board upgrade method, a single-board device, and a computer-readable storage medium.

Background technique

With the continuous development of communication technology, all walks of life have higher requirements for the stability of communication services and the friendliness of operation and maintenance operations. In the related art, the overall software version upgrade process of the communication device can achieve a lossless or slight loss upgrade, which has less impact on business functions. However, in practical applications, the upgrade cycle of the entire NE basic software version is still relatively long. The more frequent upgrade scenario is to patch the basic version of the NE by patching. Operators have high professional requirements, and the confirmation of cold patch validity is complicated, especially when there are multiple cold patches in the engineering environment. The boards involved in each cold patch may be different but all require maintenance. Therefore, engineering personnel are required to ensure Operational level of actual operation.

SUMMARY OF THE INVENTION

The single-board upgrade method, single-board device, and computer-readable storage medium provided by the embodiments of the present invention mainly solve the technical problem that the patch upgrade in the related art has high professional requirements for field upgrade operators and the upgrade process is complicated.

To solve the above technical problem, an embodiment of the present invention provides a method for upgrading a single board, including:

Activate the obtained patch package;

Parse the patch package, and obtain the board parameters corresponding to the patch package;

According to the board parameters, confirm the setting slot of the to-be-upgraded board corresponding to the patch package;

The board to be upgraded is upgraded according to the set slot.

Embodiments of the present invention also provide a single-board device, a processor, a memory, and a communication bus;

The communication bus is used to realize the connection communication between the processor and the memory;

The processor is used to execute one or more computer programs stored in the memory to realize the steps of the above-mentioned method for upgrading a single board

Embodiments of the present invention further provide a computer-readable storage medium, where one or more programs are stored in the computer-readable storage medium, and the one or more programs can be executed by one or more processors to implement the above The steps of the above-mentioned method for upgrading the board.

According to the single-board upgrade method, single-board device, and computer-readable storage medium provided by the embodiments of the present invention, the obtained patch package is activated; the patch package is parsed to obtain single-board parameters corresponding to the patch package; Output the setting slot of the board to be upgraded corresponding to the patch package, and upgrade the board to be upgraded; accurately identify the effective range of the patch package, and perform the upgrade operation. In some implementation processes, it can be achieved including but not limited to improved The degree of automation of the patch package upgrade reduces the technical effect of the field upgrade operator's operation work.

Other features of the present invention and corresponding benefits are set forth in later parts of the specification, and it should be understood that at least some of the benefits will become apparent from the description of the present specification.

Description of drawings

FIG. 1 is a schematic flowchart of a method for upgrading a board according to Embodiment 1 of the present invention;

2 is a schematic diagram of a version directory installed in a network element device according to Embodiment 2 of the present invention;

3 is a schematic diagram of a version directory currently activated and running in a memory of a network element device according to Embodiment 2 of the present invention;

4 is a schematic diagram of a version directory in a memory after a network element device activates a cold patch package according to Embodiment 2 of the present invention;

5 is a schematic diagram of configuration information of boards in each slot according to Embodiment 2 of the present invention;

6 is a schematic diagram of a refinement process of a method for upgrading a board according to Embodiment 2 of the present invention;

7 is a schematic flowchart of obtaining and installing a cold patch according to Embodiment 2 of the present invention;

FIG. 8 is a schematic diagram of the relationship between service protection groups in a single board in each slot according to Embodiment 2 of the present invention;

FIG. 9 is a schematic diagram of a board upgrade priority configuration of each slot according to Embodiment 2 of the present invention;

10 is a schematic diagram of calculation of the remaining estimated time in Embodiment 2 of the present invention;

FIG. 11 is a schematic diagram showing an upgrade progress during startup according to Embodiment 2 of the present invention;

FIG. 12 is a schematic diagram showing the progress of the upgrade in the upgrade according to the second embodiment of the present invention;

FIG. 13 is a schematic diagram showing the upgrade progress after the upgrade is completed according to the second embodiment of the present invention;

FIG. 14 is a schematic structural diagram of a single-board device according to Embodiment 3 of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below through specific embodiments in conjunction with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

Example 1:

In order to reduce the complicated operation when the board is upgraded. An embodiment of the present invention provides a method for upgrading a board, as shown in FIG. 1 , including:

S101. Activate the obtained patch package;

It should be noted that the patch package in this embodiment may also include, but is not limited to, an incremental package, a full package, or other patch packages that can be upgraded by applying the board upgrade method of this embodiment in other implementations.

The patch package may be downloaded in advance, and the patch package includes a software package that can be used to upgrade version software running on some or all of the single-board devices. As a specific example, the patch package can be stored in the hard disk of the main control board. In this example, the directory passed in by the patch package is an independent directory, which is parallel to the storage directory of the basic version package; in some embodiments If there is a standby machine (that is, the standby main control board), the patch package file can be synchronized between the main control board and the standby main control board to ensure that the patch package can still be normal after the main control board is switched. effective.

It should be noted that the activation of the patch package in this embodiment refers to replacing the file of the version package that takes effect in the system of the current single-board device with the file in the patch package. The version file soft link is the file in the patch package, that is, the activation operation is only to soft link all the version files of the version server to the files in the patch package. It should be understood that after the patch package is activated, it is not actually updated to the corresponding board. After the patch package is activated, the board usually needs to be reset and restarted. During the reset and restart process of the board, the currently activated version will be requested. The file is loaded. At this time, the files in the activated patch package are loaded by the board, and the update of the patch package is equivalent to the actual application.

S102. Parse the patch package, and obtain board parameters corresponding to the patch package;

In practical applications, the patch package may carry a configuration file, and parsing the patch package may include reading configuration information in the configuration file, and by parsing the patch package, board parameters can be obtained. In this embodiment, the board parameters can reflect the information of the board targeted by the patch package. Exemplarily, the board parameters include but are not limited to the CPU (central processing unit, central processing unit) model of the board.

S103. According to the board parameters, confirm the setting slot of the board to be upgraded corresponding to the patch package;

In practical applications, the slot configuration of the board is recorded. For example, by reading the static configuration information of the cabinet slot of the board, you can learn the information of the board set in each cabinet slot. By parsing the board parameters obtained from the patch package, the board matching the board parameters and the slot information of the board can be found from the static configuration of the cabinet slot. In this embodiment, these boards are the patch. The board to be upgraded corresponding to the package. Exemplarily, the board parameters are the CPU models of the boards, and the boards using these CPU models are searched from the static configuration of the slots in the cabinet, and the slot positions of the boards are obtained.

S104, upgrade the board to be upgraded according to the set slot.

Under normal circumstances, after resetting and restarting the boards to be upgraded, the patch package file can be loaded to complete the upgrade. In this embodiment, the board to be upgraded can be reset and restarted by issuing an instruction. Since the board to be upgraded and its slot have been confirmed in the foregoing step S103, this embodiment can achieve accurate The upgrade control can be performed only by issuing reset and restart instructions to the boards in these slots (that is, the boards to be upgraded).

It should be understood that the method for upgrading a single board in this embodiment of the present invention can be applied to other control modules including but not limited to a main control single board or single-board equipment, or an apparatus dedicated to upgrading single-board equipment. During the upgrade process, the board parameters are obtained by parsing the patch package, and the setting slot of the board to be upgraded corresponding to the patch package is confirmed, and the board in the slot is upgraded. Automatic and accurate identification and upgrade control of the effective range of the package, thereby reducing the operation work of field upgrade operators and improving the automation degree of patch package upgrade.

In some embodiments, upgrading the board to be upgraded includes:

If the update files in the patch package do not include update files other than the process update files, that is, the upgrade only involves the process files of the board to be upgraded, the board to be upgraded may not be restarted, and only the update files corresponding to the board to be upgraded will be updated. The process or virtual process group of this upgrade is restarted to complete the upgrade. If the update files in the patch package include files other than the corresponding process files, the board to be upgraded is reset and restarted to complete the upgrade. It should be noted that the process update file referred to here is the update file only related to the process in the board to be upgraded. The upgrade here refers to an upgrade in a patch package, that is, all upgrade files in a patch package are for the upgrade of process files in the board to be upgraded, and only the corresponding process can be restarted. Similar to the way of restarting the board to be upgraded, the process of the board to be upgraded can be restarted by issuing a process restart instruction to perform the upgrade. During the process of restarting the process, the activated related process file is reloaded, and the process update file in the update file is loaded and activated in this process. If the upgrade involves not only the replacement of process files (replacement with process update files), but also some resource files in XML (Extensible Markup Language) format, it is only the restart of the process or virtual process group. If the upgrade cannot be completely implemented, the board to be upgraded should be restarted.

In some embodiments, restarting the process or virtual process group corresponding to the upgrade in the single board to be upgraded to complete the upgrade includes:

Get the configuration information in the patch package;

Confirm the file name of the process involved in the upgrade according to the configuration information;

Enables the board to be upgraded to restart the corresponding process or virtual process group after obtaining the process file in the patch package.

In one example, the configuration file in the patch package is read, and the specific process files involved in the patch package can be confirmed from the configuration file. After the board obtains the corresponding upgraded process file in the patch package, it can pass the corresponding The command restarts these processes or virtual process groups.

In this embodiment, the virtual process group can also be restarted. In practical applications, whether to restart the process or the virtual process group can be flexibly selected. For example, in an example, if multiple processes in a virtual process group If both need to be updated, you can choose to restart all the virtual process groups directly. In this case, you only need to send an instruction to restart the virtual process group to avoid sending a restart for each process in the virtual process group that needs to be updated. instruction.

Because the analysis of the files in the patch package can not only confirm the boards to be upgraded involved in the upgrade, but also enable the related processes involved in the upgrade to be accurately identified in some implementation processes. Therefore, in these scenarios, it is possible to When the upgrade only involves the process files in the board to be upgraded, the upgrade process of the board to be upgraded is completed only by the above-mentioned restarting process or virtual process group, which achieves a smaller upgrade granularity and improves the efficiency of the upgrade . In addition, during the process of restarting the process or virtual process group, there may still be unupgraded processes or virtual process groups on the board to be upgraded that can run normally, which is beneficial to reduce the impact of the upgrade process.

In some embodiments, before activating the acquired patch package, it further includes:

When it is verified that the current board configuration does not meet the conditions for non-destructive upgrade, it will prompt the user that the current board configuration does not meet the conditions for non-destructive upgrade;

If it is verified that the current board configuration satisfies the conditions for the non-destructive upgrade, or after the user is prompted that the current board configuration does not meet the conditions for the non-destructive upgrade and receives an instruction to continue the upgrade from the user, the board to be upgraded will continue to be upgraded; if not After receiving the instruction to continue the upgrade, the board to be upgraded will not be upgraded.

It is understandable that, after receiving the prompt that the current board configuration does not meet the conditions for the non-destructive upgrade, the user can choose to issue an instruction to continue the upgrade (for example, the user believes that the impact of the current upgrade on the business is within an acceptable range), At this point, if you continue to upgrade, it may cause service loss or interruption during the upgrade process. In some scenarios, the user can also choose to select the Adjust the configuration of the board, and adjust the configuration of the board to a state that can achieve non-destructive upgrade, and then perform the upgrade operation again. At this time, the verification can be passed, and the subsequent upgrade process can be started.

In some embodiments, the lossless upgrade conditions include:

The boards to be upgraded with services each have an active/standby board relationship and/or a protection group relationship;

Patching the board to be upgraded includes:

Generate upgrade priorities based on the relationship between the active and standby boards and/or the protection group;

According to the upgrade priority from high to low, the boards to be upgraded are upgraded. During the upgrade process, services are performed on the boards that are not currently being upgraded;

If the main control board needs to be upgraded, the upgrade priority of the main control board is the highest priority, and the upgrade priority of the standby main control board is second only to the main control board;

If the non-main control boards need to be upgraded, an upgrade priority is generated for the non-main control boards based on the protection group relationship, and at least two of the non-main control boards with direct protection group relationships are set to different upgrade priorities;

The services performed by the boards that are not currently being upgraded include at least one of the following:

There is currently no service corresponding to the board being upgraded;

A service corresponding to a board that is being upgraded and has a master-standby board relationship and/or a protection group relationship with a board that is not currently being upgraded.

In practical applications, whether a non-destructive upgrade is possible mainly considers the boards to be upgraded that currently have services. Therefore, in some embodiments, it is determined whether each board to be upgraded with services can be temporarily or completely replaced. For example, there are spare boards and / Or there is a protection group relationship with other boards. It can be seen that the board to be upgraded in this embodiment may be a main control board (including a standby main control board) and a non-main control board. It should be noted that the lossless upgrade condition referred to in this embodiment is only a preset judgment condition that may realize lossless or low-loss upgrade, but in practical applications, satisfying the lossless upgrade condition does not mean that It can be upgraded without loss. For example, although some boards to be upgraded have a protection group relationship, the protection group relationship only covers some of the services, and some services do not have an effective protection group relationship (that is, some services cannot be replaced); Or there may be unforeseen effects during the upgrade process. And in some other implementation manners, the lossless upgrade condition can also be adjusted to other conditions according to the actual situation, and is not limited to what is shown in this embodiment.

At the same time, during the above upgrade process, services are performed on the boards that are not currently being upgraded, including not only the boards to be upgraded that have not been upgraded, but also the boards that are not being upgraded this time. business.

If there is a relationship between the standby boards, such as the main control board and the standby main control board, the two are set to different upgrade priorities; if there is a direct protection group relationship between the boards to be upgraded, the boards to be upgraded have a direct protection group relationship. Not all of the same upgrade priority. In this embodiment, upgrade operations such as restarting and resetting are performed simultaneously on the boards to be upgraded with the same upgrade priority. After the upgrade of the boards to be upgraded with the current upgrade priority is completed, the boards to be upgraded with the next upgrade priority are sequentially performed. upgrade operation. By dividing the priority of the upgrade, the execution of the upgrade can be carried out in batches. It is understandable that when the boards are upgraded in batches, the boards that have not been upgraded can continue to execute their configured services. , to a certain extent, reduce the impact of the upgrade on the business. At the same time, by setting at least two of the boards in the master-standby relationship or the non-master boards with the direct protection group relationship to different upgrade priorities, at least some services or functions can always keep working during the upgrade process. , further reducing the impact on services, and under the condition of reasonable board configuration, non-destructive upgrade can be achieved. As an example, when the main control board and the standby main control board are upgraded, one of them (such as the standby main control board) is upgraded first. During the upgrade process, the main control board is continued through the one that has not been upgraded, and the upgrade is performed first. After the upgrade of one board is completed, the upgraded board is the main control board, and the other board starts to be upgraded. During this process, there is always a board that performs the main control function, and services are not affected. Of course, as an example, the main control board and the standby main control board can both be set to the same upgrade priority (the highest upgrade priority), but during the upgrade process, the main control board and the standby main control board are For special processing, upgrade according to the order of the previous example. It can be understood that although the parameter settings in this example can make the main control board and the standby main control board have the highest priority, in the actual processing, it is still the first. The standby main control board has been upgraded, that is, the actual upgrade priority of the standby main control board is still the highest. It can be seen that the upgrade priority mentioned in this application should not be limited to data such as software parameters configured in the implementation process, but should consider the order in which the upgrade is actually performed.

In some embodiments, upgrading the board to be upgraded further includes:

If the upgrade of the board to be upgraded fails during the upgrade process, a prompt will be sent to the user;

After sending a notification to the user that the upgrade of the board to be upgraded has failed, when receiving the instruction to continue the upgrade, continue to perform the patch upgrade, and if no instruction to continue the upgrade is received, the upgraded board will be rolled back to the state before the upgrade. It should be noted that the above non-destructive upgrade process is a process of upgrading after verifying that the current board configuration satisfies the non-destructive upgrade conditions. Since there is a relationship between the active and standby boards and/or the protection group, the user can choose whether to continue the upgrade or not. For example, the user thinks that the impact caused by the failure of the upgrade of the board to be upgraded is acceptable. Of course, the user can also choose not to continue the upgrade. If the instruction to continue the upgrade is not received, the upgrade will be stopped, and the upgraded board will be returned to the state before the upgrade. It can wait for the problem that will cause the upgrade of the board to be upgraded to fail. Once resolved, perform the upgrade again.

In some implementations, the progress of the upgrade is displayed. For example, the progress can be displayed after receiving the user's instruction, and by presenting the information such as the progress of the upgrade process and/or the expected upgrade remaining time to the outside world, the visualization of the upgrade operation can be realized, the user's expectation of the upgrade result can be improved, and the upgrade process can be improved. experience. As a specific example, the displayed content may include, but is not limited to: the upgraded version, the upgrade start time, the upgrade end time, the remaining estimated time, and the upgrade status of each batch of upgrade priority boards (waiting for upgrade, upgrade in progress, the upgrade is complete, and the upgrade succeeds or fails, etc.).

In some embodiments, the access to new services is stopped before the upgrade for the patch package is completed. The upgrade for the patch package here refers to the upgrade of all the boards to be upgraded involved in the patch package. If the board to be upgraded has an upgrade priority, after all the boards to be upgraded with the upgrade priority have been updated, it means The upgrade of the patch package is complete. Avoid accessing new services during the upgrade process, thereby ensuring the stability of the upgrade process and avoiding interruption of newly accessed services or interruption of existing services.

In the method for upgrading a board provided by the embodiment of the present invention, by activating the obtained patch package, parsing the patch package to obtain the board parameters corresponding to the patch package, and confirming the to-be-upgraded board corresponding to the patch package according to the board parameters Set the slot, and upgrade the board to be upgraded; accurately identify the effective scope of the patch package, and perform the upgrade operation, which improves the automation degree of the patch package upgrade and reduces the operation work of the on-site upgrade operators.

Further, in some embodiments, the processes involved in the upgrade can be identified, and only the process or virtual process group can be restarted, thereby realizing a smaller upgrade granularity, improving the efficiency of the upgrade, and helping to reduce the impact on the upgrade process.

Further, in some embodiments, batch upgrades can be performed by dividing upgrade priorities, so as to achieve lossless or low-loss upgrades with a high degree of automation.

Embodiment 2:

In order to better illustrate the board upgrade method according to the embodiment of the present invention, a specific non-destructive automatic upgrade process is used as an example for further description in this embodiment. In the example of this embodiment, the patch package is a cold patch package (hereinafter referred to as the Cold patch), the single-board device is a kind of network element (or network element device).

Please refer to FIG. 2 , which shows the directory in the network element. The versions installed in the network element include: basic network element version (baseset1, baseset2) and cold patch version (coldpatch), wherein the basic network element version is the network element system running The cold patch version is used to repair some functions of the running software version of the NE, and must be reloaded to take effect; as shown in Figure 2, the cold patch version directory is parallel to the NE basic version directory, but the cold patch version The patch depends on the basic version of a specific NE, and the cold patch must match the basic version of the NE to take effect.

Please refer to FIG. 3 , which shows the files in the version directory used in the memory of the network element when the current network element activates and runs the basic version package baseset1. This directory is a soft link corresponding to the basic version package baseset1 of the hard disk directory.

Please refer to Figure 4, which shows the files in the version directory used in the memory of the NE when the cold patch is activated on the current NE. At this time, the files with the same name as the cold patch directory in this directory are corresponding to the cold patch in the hard disk. soft link.

Referring to FIG. 5 , in the embodiment of the present invention, for each slot board actually running in the network element, except for the main control board, which is the default configuration of the minimum version of the basic version, other boards are configured by the user. You can see unique information such as the CPU model of the physical board actually running in each slot.

Referring to FIG. 6 , in the example of this embodiment, the method for upgrading a board includes:

S201. Obtain and install a cold patch;

Referring to FIG. 7, step S201 may include:

S2011. Build a cold patch and configure the version information corresponding to the cold patch;

Among them, the cold patch can be produced offline and locally, and the production of the cold patch includes but is not limited to the following key information:

NE basic version information, which can be used to match the cold patch to take effect in the specified basic version;

The CPU model information of the board, which can be used to match the cold patch to take effect on the specified board;

In this embodiment, the cold patch applied to the network element may be a patch package containing multiple single patches, or may be a single patch, and the single patches corresponding to different CPU types are different.

S2012, verify the version information of the cold patch, and if the verification is successful, perform step S2013;

S2013, download and install the cold patch;

After the cold patch is created locally, load the cold patch in the current NE environment through the NE version installation operation. Before the cold patch is loaded, the legality of the cold patch needs to be verified, including: whether the current system has a cold patch with the same name Patch, whether the cold patch format is legal, etc.

Cold patches are loaded to NEs, and the basic version that the cold patches depend on does not necessarily exist or run on the NEs. In theory, cold patches are also a special version, but the activation of the cold patches takes effect, and the basic versions that the cold patches depend on must be required. is running.

Exemplarily, after the installation of the cold patch is completed, a subsequent non-destructive upgrade can be triggered through an instruction, and after the trigger, an automated upgrade operation can be performed.

S202, verifying whether the lossless upgrade condition is met, if not, go to step S203, if so, go to step S204;

In this example, the main verification contents include: a cold patch upgrade involving the main control board, whether there is a normal running standby main control board; a cold patch upgrade involving a common board (non-main control board), the same CPU type Whether the board to be upgraded has a protection group relationship or a similar protection group relationship. If a cold patch upgrade involving the main control board exists, there is a normal running standby main control board, and when a cold patch upgrade involving a common board exists, the common board has a protection group relationship or a similar protection group relationship, and the non-destructive upgrade is satisfied. condition. If the board to be upgraded does not meet the above conditions, the upgrade priority of the board to be upgraded is an invalid priority (in some implementation processes, these invalid priorities can be configured as the lowest priority by default). It should also be noted that, In some implementation processes, the upgrade priority of the to-be-upgraded board that currently has no service may also be set to an invalid priority.

S203. A pop-up prompt is displayed to the user that the current board configuration does not meet the condition for non-destructive upgrade;

If the user confirms that the same batch of resetting and upgrading of the boards to be upgraded with invalid priorities has no effect or the effect is acceptable, the user can also choose to continue the upgrade. If an instruction for continuing the upgrade issued by the user is received, the upgrade is continued, and step S204 is executed.

S204. Activate the acquired cold patch;

It is understandable that the cold patch activation is a separate process, and it is understandable that the cold patch activation is only an update of the soft link of the hard disk version running file.

It should be noted that if the cold patch modification changes are relatively large, there may be compatibility problems between the basic version and the cold patch version. At the same time, since the non-destructive upgrade of the cold patch in this example is performed on the NEs to be upgraded, the upgrade priority is followed. This is done in batches, or there are boards that do not need to be upgraded with cold patches. These situations lead to the coexistence of boards running the basic version and boards running the basic version + cold patch. In this case, incompatible cold patches should be installed. Contains the compatibility list whitelist of cross-version messages (that is, the list of cross-version message IDs and the corresponding relationship between the old and new message structures), to ensure that during the upgrade process, the boards running on the entire NE can perform message compatibility processing according to the compatibility list whitelist . At this point, you should check whether the cold patch has a compatibility list. If it exists, first deliver the compatibility list to each board of the NE, so that each board can perform compatibility processing on the whitelist and whitelist of the compatibility list.

S205, analyze the cold patch, and obtain the CPU model of the board corresponding to the cold patch; S206, obtain the static configuration of the rack slot of the single board in the network element, and confirm which slot boards are involved in the cold patch and set the slot;

According to the CPU model of the board obtained in the above step S205 and the record in the static configuration of the cabinet frame slot, it can be known which slot boards involved in the cold patch and the set slot positions.

S207. Generate an upgrade priority;

To better understand how the escalation priority is set in this example. As shown in Figure 8, in the network element environment, the main control board and the standby main control board are running normally in their respective positions, and the main control board is the communication center with each board. The special existence of the main control board and the standby main control board should be upgraded first. In this example, the standby main control board is upgraded first. After the active-standby switchover (that is, the active and standby It should be noted that after the active/standby switchover, you can synchronize the cold patch files between the active control board and the standby main control board to ensure the cold patch file after the active/standby switchover. Patches still work normally. Exemplarily, a numerical value can be set to indicate an upgrade priority. For example, the value range is 0-255. In this example, the smaller the value, the higher the upgrade priority, that is, the earlier the upgrade operation is performed. In an example, the upgrade priority of the main control board can be set to 0 by default, and the upgrade of the main control board and the backup main control board can be completed in the above-mentioned manner. The range of common non-main control boards is 1- Select between 254. For a board with no service or a board with services but no service protection group relationship is configured, the upgrade priority can be set to 255 by default.

In Figure 8, the service A on the board in slot 1 and the service A on the board in slot 5 are in a protection group relationship, and the service B on the board in slot 3 and the service B on the board in slot 5 are in a protection group The C service on the board in slot 3 and the C service on the board in slot 7 are in a protection group relationship, and the three are in a direct protection group relationship. Multiple boards with a direct protection group relationship cannot all be configured to use the same upgrade priority. If the boards do not have a direct protection group relationship, they can be configured to use the same upgrade priority. In practical applications, considering that multiple batches with different upgrade priorities are completely serialized, in order to ensure that the upgrade is completed as soon as possible, try to ensure that the number of configured upgrade priorities is the least.

In this example, the boards in slot 1 and slot 5 are not configured with the same upgrade priority, the boards in slot 3 and slot 7 are not configured with the same upgrade priority, and the boards in slot 3 and slot 5 are not configured with the same upgrade priority. An upgrade priority. Therefore, when the service has such a protection group relationship, an upgrade priority result can be calculated as follows: when the priority of the board in slot 1 is 1, the priority of the board in slot 5 in the direct protection group relationship is 2. The boards in slot 3 and slot 5 are also in a direct protection group relationship. Therefore, the board in slot 3 cannot be configured as 2. In order to ensure the minimum number of configuration upgrade priorities, the priority is set to 1. At this time, only the board in slot 7 is left. The priority is not configured. Since the board in slot 7 is only in a direct protection group relationship with the board in slot 3, the priority of the board in slot 7 is set to 2 to meet the requirements. When the boards in slot 3 are installed, services A, B, and C can run normally on the boards in slots 5 and 7 without interruption. After the upgrade and cold patch of the boards in slots 1 and 3 are completed, the second batch of resets is performed. When upgrading boards in slots 5 and 7, services A, B, and C can run normally on boards in slots 1 and 3 without interruption. It can be seen that the upgrades are performed in batches according to the above-mentioned upgrade priorities, and a lossless upgrade is realized.

It should be noted that, in a scenario similar to the lossless upgrade based on the protection group relationship or the master/standby relationship in this example, the upgrade priority is dynamically calculated according to the actual situation. Upgrade the priority write disk.

S208. Complete the upgrades in descending order according to the upgrade priority;

Referring to Fig. 9, in this embodiment, when the network element is running with services, the configuration of the upgrade priority of each board can be viewed. The generation of the upgrade priority of each slot is dynamically calculated according to the protection group relationship of the service. Generally, neither static configuration nor the dynamically calculated upgrade priority of each slot can be written to the disk. The upgrade priority generated by each slot based on the protection group relationship is a necessary condition for non-destructive cold patch upgrade. The default upgrade priority is the default configuration of 255, but this default priority may also be that the board has services, but no service protection group relationship is configured. In this case, when performing a cold patch upgrade, all upgrade-related When the upgrade priorities of the boards are not all valid, the one-click upgrade will prompt. If the user confirms that the upgrade of the boards with invalid priorities has no effect on the same batch of reset upgrades or the slight loss effect is acceptable, the user can also choose to continue the upgrade.

If the upgrade of the main control board is involved, the main control board and the standby main control board are upgraded according to the strategy in S207 above. The remaining veneers to be upgraded are carried out serially in batches according to the upgrade priority, and multiple veneers to be upgraded of the same batch of upgrade priorities are upgraded at the same time.

For the cold patch upgrade of the non-main control board, you can also judge whether the files in the cold patch only contain process software files (that is, whether the update only involves processes). For example, in this example, the judgment method is to check Are the suffixes of the cold patch files all so-type files (or other process-specific file types).

If the current cold patches are all cold patches of the process, the cold patch upgrade of the non-main control board can be implemented only by reloading the corresponding process. Exemplarily, a specific processing method may include: reading the configuration file in the cold patch file , confirm the specific process file name involved in the cold patch, obtain the slot of the board to be upgraded in the batch with the minimum upgrade priority, and send a process upgrade notification message to these boards to be upgraded. The content of the message carries the process file to be requested. List, after the board to be upgraded receives the notification message, the board to be upgraded downloads the corresponding process file to the local through the file transfer protocol (FileTransferProtocol, FTP for short) or other transmission protocols. After the board to be upgraded is successfully downloaded, each responds to the The main control board. After receiving the response, the main control board sends a specified process restart message corresponding to the board to be upgraded, and the board to be upgraded performs the process restart action. Furthermore, if the cold patch involves many processes, these processes logically belong to one or several virtual process groups. At this time, after the main control board receives the response that the cold patch file of the board to be upgraded is successfully downloaded, the main control board The board can send a message to restart the virtual process group of the board to be upgraded, instead of sending a process restart message to multiple processes in the same virtual process group.

It can be seen that completing the upgrade sequentially in this step includes not only resetting the board to complete the upgrade, but also reloading only part or all of the processes and virtual process groups in the board to complete the upgrade. In practical applications, at least a part of the above steps S202 to S208 can be performed automatically, and can automatically identify the effective range of the cold patch and perform precise control. The user only needs to make decisions according to the prompts and issue simple instructions, which greatly simplifies The operation of field upgrade is reduced, and the requirements for field upgrade personnel are reduced.

After the main control board confirms that all the boards to be upgraded in the current upgrade priority batch are restarted normally, the main control board starts to process the next upgrade priority batch until all the upgrade priority batches are processed. Alternatively, when the master control board has received all the process restart response messages of the boards to be upgraded in the current upgrade priority batch, and all processes have restarted normally, the master control board will start processing the next upgrade priority batch. , until all upgrade priority batches are processed. When all the upgrade priority batches are processed, the upgrade of the patch package is completed.

In this example, if the upgrade of individual boards fails, due to the existence of a protection group relationship, the user can choose whether to continue the upgrade or to avoid affecting the service without damage, or the upgrade must be completed according to the current upgrade policy. If no instruction to continue the upgrade is received, At this point, an upgrade rollback can be triggered, and the upgrade can continue after the problem is resolved. In addition, after the cold patch upgrade is started, the access of new services is generally blocked or prohibited. Otherwise, during the upgrade process, new access services or original services may be interrupted. During the upgrade process, priority should be given to ensuring that the current The ongoing business is not interrupted.

In practical applications, since the upgrade process is generally long (tens of minutes or more), you can also choose to increase the display of the upgrade progress during the upgrade process to realize the visualization of the upgrade operation and improve the user's expectation of the upgrade result. The display of the upgrade is described below with an example.

In this example, commands such as "show" can be provided to the user to display the upgrade progress. The contents of the upgrade progress display include but are not limited to: upgraded version, upgrade start time, upgrade end time, remaining estimated time, and priority for each batch of upgrade Indicates the upgrade status of the primary board (waiting for upgrade, in progress, upgrade complete, and upgrade success or upgrade failure, etc.). Except for the remaining estimated time, other contents are the real-time results of the actual upgrade stage, and the remaining estimated time is an estimated time.

Figure 10 schematically illustrates the actual operation process of the remaining estimation time algorithm. The upgrade process is divided into several key stages, and each stage is configured with an estimated time-consuming time by default. Specifically, for the same batch of priority-upgraded boards, there may be multiple boards, and the one with the largest estimated time-consuming time value for the batch can be selected. Therefore, after subdividing the upgrade process, the overall remaining estimated time has a baseline estimate. Estimated time: The estimated time-consuming time of each stage involved in this upgrade + the estimated time-consuming time of each batch of upgrade priority upgrade. However, there may be differences in this experience value in different business models or scenarios. To be more accurate, a learning and adjustment process of network element upgrade time-consuming can be introduced. Comparing the estimated time-consuming stage (estimated time-consuming is more than the actual time-consuming, the estimated overall time-consuming minus the deviation value is displayed externally, and vice versa, the deviation value is added), and the overall remaining estimated time displayed externally can be dynamically adjusted. Write the actual upgrade time in each stage into the database, and in the next upgrade, read the estimated time in the database first as an estimated benchmark (the database for the first upgrade does not exist or only the estimated time is recorded in the database). , you can only use the estimated elapsed time of the default configuration of each stage), so that the remaining estimated time will be more accurate.

As a specific example, the current upgrade process indicates that there are 6 stages, each stage has a default configuration of the estimated time-consuming time, and the cumulative value of the estimated time-consuming time of the 6 stages is equal to 78min (minutes), which is When the upgrade starts, the initial time of the remaining estimated time is displayed. When the actual upgrade in the first stage is completed, the actual time-consuming time is 12 minutes. Since the remaining estimated time displayed externally decreases in real time during the upgrade process, the When the actual upgrade at this stage is completed, the remaining estimated time displayed is 78-12=66min, but the estimated time at this stage is 15min, so after the upgrade at this stage is completed, the next stage starts, and the remaining estimated time displayed to the outside world The deviation value needs to be compensated (plus or minus compensation). Since the estimated time-consuming time at this stage is greater than the actual time-consuming time, the remaining estimated time needs to be subtracted from the deviation value 66-3=63min of the estimated time-consuming time at this stage. At this time, the display of the remaining estimated time will directly jump from 66min to 63min, and there is no time decreasing process.

In the same way, the second stage starts with the remaining estimated time of 63min after the correction in the first stage as the benchmark. It can be seen from the example that the estimated time of the second stage is less than the actual time-consuming time, and the deviation value is 5min, but due to the external time The display is real-time decreasing. At the end of the second stage, the remaining estimated time decreases to 63-25=38min, but after the second stage is completed, the estimated time-consuming time deviation compensation for this stage is performed, and the remaining estimated time occurs. Jump, the remaining estimated time displayed by external adjustment is 38+5=43min.

Other stages are analogous. After the upgrade, the remaining estimated time will be adjusted to 0min, indicating that the current upgrade has ended.

Referring to FIG. 11, it schematically illustrates an example of the display of the upgrade progress added during the upgrade process, to realize the visualization of the upgrade operation, and to improve the user's psychological expectation for the upgrade result. The "show" command in ), the upgrade progress display includes but is not limited to: upgraded version, upgrade start time, upgrade end time, remaining estimated time, upgrade status of each batch of upgrade priority boards (waiting for upgrade, upgrade in progress, the upgrade is complete, and the upgrade succeeds or fails, etc.).

Figure 11 shows the status at the beginning of the upgrade. The current upgrade end time is unknown and is not displayed. The boards to be upgraded with the cold patch are displayed according to the upgrade priority. The upgrade status of the priority batches that have been upgraded is displayed as Upgrading ( Upgrading), the priority batch upgrade status that has not started the upgrade is displayed as Wait-Upgrade (waiting for upgrade). At the same time, it can be seen that the upgrade priority of the main control board is the highest, and the upgrade priority of the non-main control board starts from 1.

At the same time, it should be noted that the upgrade status displayed during the cold patch upgrade process is only the upgrade status of the boards involved in the cold patch upgrade. of.

As shown in Figure 12, it shows the status when the upgrade is in progress. The boards currently upgraded by the cold patch are displayed according to the upgrade priority. The upgrade status (Status column) of the priority batch that has been upgraded is displayed as Upgraded ), the upgrade status of the priority batch being upgraded is displayed as Upgrading, and the remaining estimated time is decremented in real time. For the cold patch upgrade of common boards, multiple boards with the same upgrade priority are upgraded at the same time, and the upgrade progress of this batch of boards is displayed as Upgrading. At the same time, the cold patch upgrade process shows the upgrade status that the upgrade has been completed, including the individual upgrade status of each board with the upgrade priority of the batch. For example: the upgrade priority of the main control board (the priority column) is 0, and the main control board has active and standby slots (the slots of the main control board and the standby main control board), and the upgrade result is that the upgrade is successful. Success The (upgrade success) column displays ALL to indicate that all the upgrades are successful. The boards with the upgrade priority of 1 for common boards include boards in slots 1 and 3. At the same time, the priority of the batch has been upgraded, but the priority of the batch is upgraded. The upgrade results of the boards may not be exactly the same, so it can be displayed separately that the upgrade of slot 1 succeeds and the upgrade of slot 3 fails. If the upgrade of individual boards fails, the user can choose whether to continue the upgrade or stop the upgrade to avoid affecting services due to the existence of the protection group.

As shown in Figure 13, it shows the status at the end of the upgrade. The current upgrade end time has normally displayed the time when the upgrade ended, and the estimated remaining time of the upgrade is also adjusted to 0min in real time. At this point, the upgrade status of the cold patch is all displayed as Upgraded (upgrade completed), but the upgrade results are displayed in the Success (upgrade success) and Fail (upgrade failure) columns. The failed board can be recovered independently after confirming the problem.

Embodiment three:

This embodiment provides a single-board device, as shown in FIG. 14, which includes a processor 141, a memory 142, and a communication bus 143, wherein:

The communication bus 143 is used to realize the connection communication between the processor 141 and the memory 142;

The processor 141 is configured to execute one or more computer programs stored in the memory 142 to implement at least one step in the method for upgrading a board in the first and second embodiments above.

The present embodiments also provide a computer-readable storage medium embodied in any method or technology for storing information, such as computer-readable instructions, data structures, computer program modules, or other data volatile or nonvolatile, removable or non-removable media. Computer-readable storage media include but are not limited to RAM (Random Access Memory, random access memory), ROM (Read-Only Memory, read only memory), EEPROM (Electrically Erasable Programmable read only memory, electrically erasable programmable read only memory), flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Versatile Disc, Digital Versatile Disc) or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device, or may be used to store desired information and any other medium that can be accessed by a computer.

The computer-readable storage medium in this embodiment may be used to store one or more computer programs, and the one or more computer programs stored therein may be executed by a processor to implement the board upgrade in the first and second embodiments above at least one step of the method.

It can be seen that those skilled in the art should understand that all or some of the steps in the methods disclosed above, the functional modules/units in the system, and the device can be implemented as software (which can be implemented by computer program codes executable by a computing device). ), firmware, hardware, and their appropriate combination. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical components Components execute cooperatively. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit .

In addition, communication media typically embodies computer readable instructions, data structures, computer program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery, as is well known to those of ordinary skill in the art medium. Therefore, the present invention is not limited to any particular combination of hardware and software.

The above content is a further detailed description of the embodiments of the present invention in conjunction with specific implementations, and it cannot be considered that the specific implementation of the present invention is limited to these descriptions. For those of ordinary skill in the technical field of the present invention, without departing from the concept of the present invention, some simple deductions or substitutions can be made, which should be regarded as belonging to the protection scope of the present invention.

Claims (10)

1. A single board upgrading method includes:

activating the obtained patch package;

analyzing the patch package to obtain the single board parameters corresponding to the patch package;

confirming a setting slot position of the single board to be upgraded corresponding to the patch package according to the single board parameters;

and upgrading the single board to be upgraded according to the set slot position.

2. The board upgrading method according to claim 1, wherein the upgrading the board to be upgraded according to the set slot includes:

if the update file in the patch package does not include an update file other than the process update file, the single board to be upgraded is not restarted, so that the process or the virtual process group corresponding to the upgrade in the single board to be upgraded is restarted to complete the upgrade; and if the update files in the patch package comprise update files except the process update files, resetting and restarting the single board to be upgraded to finish upgrading.

3. The board upgrade method according to claim 2, wherein the restarting the process or the virtual process group corresponding to the upgrade in the board to be upgraded to complete the upgrade includes:

acquiring configuration information in the patch package;

confirming the process file name related to the upgrade according to the configuration information;

and restarting the corresponding process or virtual process group after the single board to be upgraded acquires the process file in the patch package.

4. The board upgrade method according to claim 1, wherein before activating the obtained patch package, the method further includes:

when the current single board configuration is verified to not meet the lossless upgrading condition, prompting a user that the current single board configuration does not meet the lossless upgrading condition;

if the current single board configuration is verified to meet the lossless upgrading condition, or a continuous upgrading instruction issued by the user is received after the current single board configuration is prompted to meet the lossless upgrading condition, continuously upgrading the single board to be upgraded; if the instruction for continuing upgrading is not received, the single board to be upgraded is not upgraded.

5. The board upgrade method according to claim 4, wherein the lossless upgrade condition includes:

the single boards to be upgraded with services have a main and standby single board relationship and/or a protection group relationship;

the upgrading the board to be upgraded comprises the following steps:

generating an upgrade priority according to the main and standby veneer relation and/or the protection group relation;

sequentially upgrading the single board to be upgraded according to the upgrading priority from high to low, and executing services through the single board which is not currently executing upgrading in the upgrading process;

if the master control single board needs to be upgraded, the upgrade priority of the standby master control single board is the highest priority, and the upgrade priority of the master control single board is only next to that of the standby master control single board;

if the non-master control single board needs to be upgraded, generating upgrading priorities for the non-master control single board based on the protection group relationship, and setting at least two of the non-master control single boards with the direct protection group relationship as different upgrading priorities;

the service executed by the single board which is not currently executing the upgrade includes at least one of the following:

the service corresponding to the veneer which is not currently executing upgrading is obtained;

and the service corresponding to the single board which is not currently performing the upgrade and has the relationship between the main single board and the standby single board and/or the protection group relationship with the single board performing the upgrade.

6. The board upgrading method according to claim 5, wherein the upgrading the board to be upgraded further includes:

if the upgrading of the single board to be upgraded fails in the process of lossless upgrading, a prompt is sent to a user;

after a prompt of failure of upgrading of the single board to be upgraded is sent to a user, when an instruction for continuing upgrading is received, patch upgrading is continued, and if the instruction for continuing upgrading is not received, the upgraded single board is returned to a state before upgrading.

7. The board upgrading method according to any of claims 1-6, further comprising:

and displaying the progress of upgrading.

8. The board upgrading method according to any of claims 1-6, further comprising:

and stopping the access of the new service before finishing the upgrading aiming at the patch package.

9. A single board device comprises a processor, a memory and a communication bus;

the communication bus is used for realizing connection communication between the processor and the memory;

the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the single board upgrade method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores one or more computer programs which are executable by one or more processors to implement the steps of the single board upgrade method according to any one of claims 1 to 8.

Images