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

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
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).
SYSTEM/2/hwPatchInstallFail_active

SYSTEM/2/hwPatchInstallFail_active

Message

SYSTEM/2/hwPatchInstallFail_active: Patch operation failed.(SlotIndex=[SlotIndex], PatchIndex=[PatchIndex], PackageName=[PackageName], PackageVersion=[PackageVersion], FailReason=[FailReason])

Description

Patch package installation failed.

Parameters

Parameter Name Parameter Meaning

SlotIndex

Board index

PatchIndex

Patch package index

PackageName

Patch package name

PackageVersion

Patch package version

FailReason

Alarm cause

Possible Causes

Cause 1: Failed to read the patch file configuration information.

Cause 2: Failed to obtain the patch file.

Cause 3: The patch memory space was insufficient.

Cause 4: The patch conflicted with the previous patch package.

Cause 5: The patch version was incorrect.

Cause 8: Failed to automatically synchronize the patch package.

Cause 9: The configuration of the patch and patch unit within the system was inconsistent with the patch configuration issued by the command.

Procedure

  • Cause 1: Failed to read the patch file configuration information.
    1. Re-load the patch file and run the display patch-information command to check whether the patch status is Running.

      • Yes: The patch file is successfully loaded and the problem is resolved.
      • No: Go to 2.

    2. Collect log information and configuration information, and then contact technical support personnel.
  • Cause 2: Failed to obtain the patch file.
    1. Delete useless packages in the root directory, to ensure that the remaining space is enough to store the patch file. Re-load the patch file and run the display patch-information command to check whether the patch status is Running.

      • Yes: The patch file is successfully loaded and the problem is resolved.
      • No: Go to 2.

    2. Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 3: The patch memory space was insufficient.

    Collect log information and configuration information, and then contact technical support personnel.

  • Cause 4: The patch conflicted with the previous patch package.

    Collect log information and configuration information, and then contact technical support personnel.

  • Cause 5: The patch version was incorrect.
    1. Re-load the patch file and run the display patch-information command to check whether the patch status is Running.

      • Yes: The patch file is successfully loaded and the problem is resolved.
      • No: Go to 2.

    2. Collect log information and configuration information, and then contact technical support personnel.
  • Cause 8: Failed to automatically synchronize the patch package.

    Manually copy the patch package to the corresponding board.

  • Cause 9: The configuration of the patch and patch unit within the system was inconsistent with the patch configuration issued by the MML command.
    1. It may be due to process or virtual machine reset during the installation of the patch. Re-load the patch file and run the display patch-information command to check whether the patch status is Running.

      • Yes: The patch file is successfully loaded and the problem is resolved.
      • No: Go to 2.

    2. Collect log information and configuration information, and then contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 114584

Downloads: 85

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next