Upgrade Commands
check startup
Function
The check startup command checks the correctness of various resource files, including the PAF file, the patch package, the startup software, and the configuration file.
Parameters
| Parameter | Description | Value |
|---|---|---|
| crc | Performs a CRC check on various resource files. | - |
| next | Checks various resource files used for next startup. | - |
Usage Guidelines
After configuring the resource files for next startup, you can run this command to check whether the resource files are complete and whether the formats and versions of the resource files are correct.
Example
# Check the correctness of the resource files.
<HUAWEI> check startup
Main board: Check startup software.......ok Check configuration file.....ok Check PAF....................ok Check Patch..................ok PAF is fitted with startup software Info: Slave board is not existing.
# Performs a CRC check on various resource files.
<HUAWEI> check startup crc
Warning: This operation will take several minutes! Continue?[Y/N]:y Check startup software CRC.................................................... ok Info: Slave board is not existing.
display module-information
Function
The display module-information command displays information about dynamically uploaded modules.
Parameters
| Parameter | Description | Value |
|---|---|---|
| verbose | Displays detailed information about dynamically uploaded modules. |
- |
| next-startup | Displays information about the module packages to be uploaded at the next startup. |
- |
Usage Guidelines
After modules are uploaded, you can run the display module-information command to check information about these modules.
Example
# Display information about dynamically uploaded modules.
<HUAWEI> display module-information Module Information ------------------------------------------------------------------------ Module Version InstallTime PackageName ------------------------------------------------------------------------ MACSEC SPH 2011-01-16 16:39:18+00:00 s600-e-V200R010C00spc200.mod Total = 1
# Display detailed information about dynamically uploaded modules.
<HUAWEI> display module-information verbose Module Information ------------------------------------------------------------------------ Module Version InstallTime PackageName ------------------------------------------------------------------------ MACSEC SPH 2011-01-16 16:39:18+00:00 s600-e-V200R010C00spc200.mod Total = 1 Board Info: ------------------------------------------------------------------------ Slot Module State Count Time(YYYY-MM-DD HH:MM:SS) ------------------------------------------------------------------------ 0 MACSEC Using 1 2011-01-16 16:39:17+00:00 Total = 1
Item |
Description |
|---|---|
Module Information |
Module information. |
Module |
Module name. |
Version |
Module package version. |
PackageName |
Module package name. |
InstallTime |
Time when the module package was uploaded to the memory. |
Total |
The Total field under Module Information displays the number of module packages that take effect. The Total field under Board Info displays the number of boards that have modules installed. |
Board Info |
Board information. |
Slot |
Slot ID of the board where a module resides. |
State |
Status of the module. |
Count |
Number of modules that take effect on the board. |
Time(YYYY-MM-DD HH:MM:SS) |
Time when the module took effect, that is, time when the current module was loaded to the current state. |
# Display information about the next startup modules configured in the system.
<HUAWEI> display module-information next-startup Info: The result will be shown in several minutes. Please wait for a moment...... Next startup module packages Total = 1 ------------------------------------------------------------------------ No. PackageName ------------------------------------------------------------------------ 1 flash:/$_install_mod/s600-e-V200R010C00spc200.mod
Item |
Description |
|---|---|
Next startup module packages |
Information about module packages to be installed at the next startup. |
Total |
Number of module packages to be installed at the next startup. |
No. |
Sequence number of a module package to be installed at the next startup. |
PackageName |
Name of a module package to be installed at the next startup. |
display paf
Function
The display paf command displays information about the product adaptive file (PAF) in the system.
Parameters
Parameter |
Description |
Value |
|---|---|---|
all |
Displays all information about the PAF file. |
- |
resource |
Specifies the value set for a resource item in the PAF file. |
- |
service |
Specifies the value set for a service item in the PAF file. |
- |
item-name |
Specifies the name of a resource item or a service item. |
The value is a string of 1 to 64 characters. |
Usage Guidelines
A PAF file provides only required resources and features. This command can display all the specification information about the PAF file.
Example
# Display the value set for a resource item in the PAF file.
<HUAWEI> display paf resource PAF_LCS_NQA_SPECS_NUM_ENTRY PAF_LCS_NQA_SPECS_NUM_ENTRY = 1, 32, 32, 0
# Display the value set for a service item in the PAF file.
<HUAWEI> display paf service PAF_LCS_IPV6_BASE_SPECS_ENABLED
PAF_LCS_IPV6_BASE_SPECS_ENABLED = 1, 1
Item |
Description |
|---|---|
PAF_LCS_NQA_SPECS_NUM_ENTRY |
Resource item name in the PAF file. |
1 |
Whether a resource item is controlled by a license.
|
32 |
Default value of the resource item in the PAF file. |
32 |
Maximum value of the resource item in the PAF file. |
0 |
Minimum value of the resource item in the PAF file. |
display patch-information
Function
The display patch-information command displays information about the patch in the current system.
Parameters
| Parameter | Description | Value |
|---|---|---|
| history | Displays historical information about the patch in the current system. |
- |
Usage Guidelines
After a patch is loaded or deleted, run this command to view information about the patch, including its version, name, and status.
Example
# Display information about the patch in the current system.
<HUAWEI> display patch-information
Patch Package Name :flash:/patch_all_pack.pat
Patch Package Version:V200R010C00SPH001
The state of the patch state file is: Running
The current state is: Running
************************************************************************
* Information about hot patch errors is as follows: *
************************************************************************
Slot CurrentVersion
------------------------------------------------------------
No hot patch error occurs on any board.
************************************************************************
* The hot patch information, as follows: *
************************************************************************
Slot Type State Count Time(YYYY-MM-DD HH:MM:SS)
------------------------------------------------------------------------
0 C Running 5 2014-10-28 15:17:14+00:00
Item |
Description |
|---|---|
Patch Package Name |
Name of the patch file. |
Patch Package Version |
Version of the patch. |
The state of the patch state file is |
Status of the patch file. |
The current state is |
Current status of the patch. |
Slot |
Slot ID. |
Type |
Patch type.
|
State |
Running status of the patch.
|
Count |
Number of patch units. For kernel patches, the number of kernel patches in Active and Running states is displayed. |
Time(YYYY-MM-DD HH:MM:SS) |
Time when the patch takes effect. |
display rollback
Function
The display rollback { information | result } command displays rollback information in the system.
Usage Guidelines
Usage Scenario
If an error occurs during an upgrade and you need to cancel the upgrade, run the rollback command to roll back the system to the previous version.
- Before performing a rollback, you can run the display rollback information command to preview the version status after the rollback, including the system software, configuration file, and patch file used after the rollback, as well as the remaining time for the rollback function to take effect.
- After completing the rollback, you can run the display rollback result command to check whether the rollback is successful.
Example
# Display rollback information in the system.
<HUAWEI> display rollback information
--------------------------------------------------------------------
MainBoard:
Software package: flash:/basicsoft.cc
Configuration file: flash:/vrpcfg201506011523.zip
Patch file: NULL
Rollback remain time: 00:16:49
--------------------------------------------------------------------
Item |
Description |
|---|---|
Software package |
System software used after the rollback. |
Configuration file |
Configuration file used after the rollback. This configuration
file is the backup configuration file automatically generated by the
system after the upgrade. The file name is in the format of filenameYYYYMMDDhhmm.zip.
If the file name is too long, the system automatically shortens the file name length to the required length. |
Patch file |
Patch file used after the rollback. |
Rollback remain time |
Remaining time for the rollback function to take effect. |
# Check whether the rollback is successful after the rollback is complete.
<HUAWEI> display rollback result
Rollback result: Success.
Item |
Description |
|---|---|
Rollback result |
Rollback result:
|
install-module
Function
The install-module command installs module packages.
By default, no module package is installed.
Parameters
| Parameter | Description | Value |
|---|---|---|
| file-name | Specifies the name of a module package to be installed. file-name supports file name association. The related file can be associated and displayed after you enter a specified character string. |
The value is a string of 5 to 64 case-insensitive characters without spaces. |
| next-startup | Specifies the name of the module package to be installed during next startup. |
- |
Usage Guidelines
Usage Scenario
Software upgrade is a common method to add new services on a network. This method, however, is complex and affects services. To solve these problems, you can run the install-module command to install the module package of a desired function, without upgrading or powering off your device.
- Run the install-module file-name command to load a module in the module package to the device. The module directly takes effect after being loaded. If the device is in a stack, the module is loaded to all the devices in the stack, including the master, standby, and slave switches.
- Run the install-module file-name next-startup command to add the module package to the next startup module list. The device automatically loads the module next time it starts. Before a module package is installed dynamically, the system checks the module package validity. In the next startup module list, one module can exist in only one module package.
Precautions
- The file name extension of the module package must be .MOD, and the file must be saved in the directory $_install_mod on the device.
- The module package version must match the current system software version. Otherwise, the module package will fail to be installed.
- The system allows you to install up to 16 modules.
Example
# Load the module package s600-e-v200r010c00spc200.mod.
<HUAWEI> install-module s600-e-v200r010c00spc200.mod Info: Installing the module flash:/$_install_mod/s600-e-v200r010c00spc200.mod.. . Info: Succeeded in installing the module on the master board....
# Configure the module package to be loaded during next startup.
<HUAWEI> install-module s600-e-v200r010c00spc200.mod next-startup Info: The result will be shown in several minutes. Please wait for a moment..... ... Info: Succeeded in setting the next-startup module.
patch active all
Function
The patch active all command activates the patches on the current system.
By default, the loaded patches on the current system are inactive.
Usage Guidelines
Usage Scenario
If you do not specify the active or run keyword when running the patch load command, run the patch active all command to activate all the loaded patches to make them effect.
Prerequisites
Patches have been loaded using the patch load command.
Configuration Impact
After a non-incremental patch is loaded and the patch active all command is run, the patches in the current system are activated.
If an incremental patch is loaded and the previous patch package is running, the previous patch package is still in running state after you run the patch active all command. The new patch package is activated.
Follow-up Procedure
After running the patch active all command, use the patch run all command to run the activated patch.
Precautions
If the device is restarted, all the active patches become inactive. To reactivate the patches, run the patch active all command.
To make the patches become active, run the patch active all command again.
The active state can prevent a patch error from causing continuous faults of the system. If a patch has a bug and the patch is in the active state, restart the device to prevent the patch from taking effect.
patch configuration-synchronize
Function
The patch configuration-synchronize command synchronizes the patch configuration and patch file of the master switch to other member switches in a stack.
patch deactive all
Usage Guidelines
This command does not take effect in the current version. During the operation, if a bug is detected in a patch and the system software problem cannot be solved, run the patch delete all command to delete the patches in the patch area in the memory.
patch delete all
Usage Guidelines
- If you find errors in patches that have been loaded to the system, run this command to delete the patches to prevent patch errors from affecting system operating.
- Before loading a non-incremental patch, run this command to delete the existing patches (if any). Otherwise, the non-incremental patch cannot be loaded.
patch load
Parameters
Parameter |
Description |
Value |
|---|---|---|
filename |
Specifies the path and file name of a patch package. The path can be an absolute path or a relative path. file-name supports file name association. The
disk where the file resides can be automatically associated.
|
The value is a string of 5 to 64 case-insensitive characters without spaces. The file name must have an extension of .pat. |
all |
Loads the patches of all member switches in a stack. |
- |
active |
Activates loaded patches. |
- |
run |
Runs loaded patches. |
- |
Usage Guidelines
Usage Scenario
- If a matching patch file is found in the patch package, the system loads the patch.
- If no matching patch file is found in the patch package, the system does not load any patch.
Prerequisites
The patch package has been uploaded to the root directory of the storage device.
Before loading a patch, the system must resolve the patch package, check the validity of the patch files in the patch package, and obtain the attributes such as the patch type and version of the patch file.
Precautions
The patch file cannot be reloaded. When you reload a patch, the system displays an error message.
- If the active parameter is specified, the system activates the loaded patches directly. Then you can use the patch run all command to run the patches.
- If the run parameter is specified, the system runs the loaded patches directly.
patch run all
Usage Guidelines
Usage Scenario
When the device is restarted, the active patches become deactivated and need to be activated again. To enable the active patches to retain in running start after a device restart, use this command to run these active patches.
Prerequisites
Patches have been loaded and activated on the system.
Configuration Impact
After you run this command to run patches on the current system, the patches remain in the running state if a device restart occurs.
After the patch run all command is run, the patches enter running state and cannot be restored to the previous state. Confirm the action before you run the command.
reset patch-configure
Function
The reset patch-configure command deletes the configuration of the patch file for next startup.
Parameters
| Parameter | Description | Value |
|---|---|---|
| next-startup | Deletes the configuration of the patch file for next startup. | - |
Usage Guidelines
Usage Scenario
After you run the startup patch command to specify the patch file for next startup, you can use the reset patch-configure command to delete the configuration.
Precautions
If you run the reset patch-configure command, the patch file for next startup is empty. When the device restarts, the system does not load and run the patch file.
rollback
Usage Guidelines
Usage Scenario
If an error occurs during an upgrade and you need to cancel the upgrade, run the rollback command to roll back the system to the previous version. After the rollback, the configuration of the device is the same as the previous configuration.
Precautions
The rollback function takes effect only for an upgrade during which the reboot command is run to restart the device, and does not support other upgrade modes, such as the EasyDeploy upgrade and smooth stack upgrade. If the reboot command is run to complete an upgrade and then the system is upgraded using another mode, you can only run the rollback command to roll back the system to the latest version before the upgrade during which the reboot command is run. For example, if you run the reboot command to restart the device and upgrade the system from V1.0 to V1.1, and then upgrade the system to V1.2 using EasyDeploy, the system can only be rolled back to V1.0 when you run the rollback command to perform a system rollback.
If a device runs continuously for more than 48 hours after being upgraded, the rollback function does not take effect. If the device runs continuously for less than 48 hours and restarts, the system sets the remaining time to zero and the rollback function does not take effect. You can run the display rollback information command to check the remaining time for the rollback function to take effect.
If the system software, configuration file, or patch file required in the rollback is deleted using the delete (user view) command, the system prompts that the rollback function cannot be used when you run the rollback command.
Prerequisites
The device contains the system software, configuration file, and patch file that are used after the rollback and displayed in the display rollback information command output.
Example
# Roll back the system to the previous version.
<HUAWEI> rollback
Info: Checking rollback version information...
Rollback software: flash:/basicsoft.cc
Rollback configuration: flash:/vrpcfg.zip
Rollback patch: NULL
Warning: The version running before the last reboot/reboot fast operation is performed will be restored, and the current configuration will be lost. Continue? [Y/N]:y
uninstall-module
Parameters
| Parameter | Description | Value |
|---|---|---|
| file-name | Specifies the name of a module package to be uninstalled. |
The value is a string of 5 to 64 case-insensitive characters without spaces. |
| next-startup | Clears the module list for next startup. |
- |
| all | Clears the module list for next startup. |
- |
Usage Guidelines
If some services or functions are not required, run the uninstall-module command to uninstall the corresponding modules running in the system.
Example
# Uninstall the module package s600-e-v200r010c00spc200.mod from the system.
<HUAWEI> uninstall-module s600-e-v200r010c00spc200.mod This will uninstall the module. Are you sure? [Y/N]y.... Info: Succeeded in uninstalling the module on the master board.
# Clear a specified module package in the next startup module list.
<HUAWEI> uninstall-module s600-e-v200r010c00spc200.mod next-startup Info: The result will be shown in several minutes. Please wait for a moment..... ... Info: Succeeded in resetting the next-startup module.
