No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Advanced O&M Command Reference

OceanStor 2800 V5 V500R007

This document is applicable to OceanStor 2800 V5. Based on the CLI, this document describes how to use various commands classified by functions and how to set the CLI and manage the storage system through these commands. The document that you browse online matches the latest C version of the product. Click Download to download documents of other C versions.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
os_upgrade_hotpatch.sh

os_upgrade_hotpatch.sh

Function

The os_upgrade_hotpatch.sh command is used to dynamically load, roll back, delete, and query a patch in the system.

Format

os_upgrade_hotpatch.sh { -m size | -w [ install | roll | delete ] | -p packagename [ mini ] | -g packagename | -c | -r | -k | -d | -v [ all | local ] | -h }

Parameters

Parameter

Description

Value

-m size Checks whether there is sufficient memory in the system. If available memory in the system is larger than that specified by "size" (unit: MB), a success message is returned; otherwise, a failure message is returned. This interface is used by the automation tool to install a patch package. This parameter is not used in a manual upgrade in minisystem mode.

-

-w install | roll | delete
  • "install": to perform a pre-installation check. The following is checked: patch version, md5 verification files, and the absolute path of the patch package that you want to add.
  • "roll": to perform a pre-rollback check. The system checks whether a patch package is available for the rollback of the current system patch.
  • "delete": to perform a pre-deletion check.

The value can be "install", "roll", or "delete".

-p packagename [ mini ] Installs the patch, namely, loads the patch. After this operation is performed, the patch is effective. If this command is used in a tiny core, you need to add the "mini" parameter. After the "mini" parameter is added, only the patches that are marked with coldpatch are effective, and the other patches become effective after the system starts.

-

-g packagename Checks if the patch package is special patch. If it is, then return 10, and user should not use this script to install the patch package. If it is not, then return 0, and user can use this script to install the patch package.

-

-c Confirms the installation. This step will change the link in the patch directory and confirm that the link can be used for rollback or query in the future.

-

-r Rolls back the patch. The patch can be rolled back only once.

-

-k Deletes all files on /OSM/update.

-

-d Deletes the patch.

-

-v all | local
  • "all": to check the versions of the patches currently running on the local and peer ends and the versions that the patches can be rolled back to. You can obtain the query results using the /tmp/hotpatch_version.conf and /tmp/hotpatch_peer_version.conf files.
  • "local": to query the version of the current patch and the version the patch can roll back to. The query results are displayed in the command output.

The value can be "all" or "local".

-h Help information.

-

Modes

Minisystem mode

Usage Guidelines

  • Before installing the patch, upload the patch package to the local controller.
  • When loading the patch, check, load, and confirm the patch.
  • Rolling back a patch will roll back a patch to its previous version and uninstall the patches of the current version. A patch can be rolled back once only. For example, patches 1, 2, and 3 have been installed on a system, you can only roll back the system from patch 3 to 2 and cannot further roll back to patch 1.
  • Deleting a patch is to roll back all patches.
  • To manually check the patch on the local device, use the "-v local" parameter.
  • The patch loaded by this command only works on the local node.
  • The system is in rescue mode. After the "resumebootmode" command is executed successfully, run the "os_upgrade_hotpatch.sh" command.

Example

  • Install a patch.

    Storage: minisystem> os_upgrade_hotpatch.sh -w install
    /home/permitdir/S5600TV100R005C00SPH101.tgz
    check hotpatch action success.
    Storage: minisystem> os_upgrade_hotpatch.sh -p S5600TV100R005C00SPH101.tgz
    install hotpatch success.
    Storage: minisystem> os_upgrade_hotpatch.sh -c
    confirm hotpatch success.
  • Roll back a patch.

    Storage: minisystem> os_upgrade_hotpatch.sh -w roll
    check hotpatch action success.
    Storage: minisystem> os_upgrade_hotpatch.sh -r
    rollback hotpatch success.
  • Delete a patch.

    Storage: minisystem> os_upgrade_hotpatch.sh -w delete
    check hotpatch action success.
    Storage: minisystem> os_upgrade_hotpatch.sh -d
    delete all hotpatch success.

System Response

None

Translation
Download
Updated: 2020-01-17

Document ID: EDOC1000181575

Views: 719091

Downloads: 31

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next