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

CloudEC V600R019C00 Troubleshooting (Enterprise On-premises, Convergent Conference)

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).
Patch Loading Failure

Patch Loading Failure

Symptom

If running LOD PATCH in the MML Command - CGP window of the client fails, one of the following messages may be displayed:

  • The specified patch name is invalid.
  • The patch does not exist.
  • The previous patch is not in Running state. Please run CON PATCH to confirm it.
  • The version of the patch to be loaded is earlier than the existing version in the system.
  • The specified module does not exist.
  • Operation times out.
  • Patch initializing, operation failed.
  • The specified ME instance does not exist.
  • Other messages.

Possible Causes

The cause of the fault may be one of the following:

  • The patch name is wrong.
  • No patch is found.
  • Certain patches in the system are not running.
  • The version of the patch to be loaded is earlier than the version of the existing patch.
  • It is found that the specified module number does not exist when installing the patch.
  • One or several related processes running on the host are abnormal.
  • A process is resetting. The process is loading patches from the OMU. In this case, the patch loading command cannot be run.
  • It is found that the specified ME ID does not exist when installing the patch.
  • Process files for generating a patch package differ from those on the current system on which a hot patch is to be loaded.

Fault Diagnosis

Based on the error message displayed on the client, rectify the fault following the handling procedure.

Procedure

    Check the message displayed on the client

    1. Run LOD PATCH in the MML Command - CGP window of the client to load the patch, and take an appropriate measure based on the message displayed on the client.

      If the displayed message is The specified patch name is invalid: Go to 2.

      If the displayed message is The patch does not exist: Go to 6.

      If the displayed message is The previous patch is not in Running state. Please run CON PATCH to confirm it: Go to 9

      If the displayed message is The version of the patch to be loaded is earlier than the existing version in the system: Go to 14.

      If the displayed message is The specified module does not exist: Go to 16.

      If the system displays the message Operation timeout: Go to 19.

      If the system displays the message Patch initializing, operation failed: Go to 19.

      If the displayed message is The specified ME instance does not exist: Go to 23.

      • Other messages: Go to 26.

    Check whether the patch name is correct.

    1. Run LST PKG in the MML Command - CGP window of the client to query the name of the patch package to be loaded.

      NOTE:

      A patch package should be named in format of ME type_Package_ME versionSPCXXX.tar, in which XXX refers to the number of the patch package and SPCXXX indicates the name of the patch. For example, if a patch package is named CGP_V200R018C00SPC501.tar, SPC501 is the name of the patch.

    2. Check whether the name of the hot patch in the patch package is the same as Patch name defined by running LOD PATCH.

      • Yes: Go to 26.
      • No: Go to 4.

    3. Correct the patch name.
    4. Run LOD PATCH in the MML Command - CGP window of the client to load the patch again, and then check whether the fault is rectified.

      • Yes: No further action is required.
      • No: Go to 26.

    Check whether the patch package exists.

    1. Run LST PKG in the MML Command - CGP window of the client to check whether the patch package to be loaded exists.

      • Yes: Go to 26.
      • No: Go to 7.

    2. Use the FTP service of the client to upload the patch package to the Software package (auto loading) directory of the server.
    3. Run LOD PATCH in the MML Command - CGP window of the client to load the patch again, and then check whether the fault is rectified.

      • Yes: No further action is required.
      • No: Go to 26.

    Check the status of the patch.

    1. Run DSP PATCH in the MML Command - CGP window of the client to check whether the loaded patch is in Deactivated or Activated state.

      • Deactivated: Go to 10.
      • Activated: Go to 12.

    2. Run ACT PATCH and CON PATCH in the MML Command - CGP window of the client to make sure that the patch is running.
    3. Run LOD PATCH in the MML Command - CGP window of the client to load the patch again, and then check whether the fault is rectified.

      • Yes: No further action is required.
      • No: Go to 26.

    4. Run CON PATCH in the MML Command - CGP window of the client to make sure that the patch is running.
    5. Run LOD PATCH in the MML Command - CGP window of the client to load the patch again, and then check whether the fault is rectified.

      • Yes: No further action is required.
      • No: Go to 26.

    Check whether a patch of a later version exists.

    1. Run DSP PATCH in the MML Command - CGP window of the client to check all existing patches in the system.
    2. Check whether the version of any existing patch is later than the patch to be loaded.

      • Yes: No further action is required.
      • No: Go to 26.
      NOTE:
      • A greater patch number indicates a later patch version, for example, SPH002 is later than SPH001.
      • A later patch version includes all issues found in an earlier patch version.

    Check whether the module for which the patch is to be installed exists.

    1. Run LST MODULE in the MML Command - CGP window of the client to check whether the module for which the patch is to be installed exists.

      • Yes: Go to 26.
      • No: Go to 17.

    2. Run corresponding commands in the MML command window of the ME on the client to add the module, process, or process group.
    3. Run LOD PATCH in the MML Command - CGP window of the client to load the patch again, and then check whether the fault is rectified.

      • Yes: No further action is required.
      • No: Go to 26.

    Check whether a module is faulty or resetting.

    1. Run DSP MODULE in the MML Command - CGP window of the client to check the state of the modules.

      • The Availability state for some modules is Not ready: Go to 20.
      • The Availability state for some modules is Faulty or the Active/Standby state for some modules is not Active or Standby: Go to 21.
      • The Availability state for all the modules is Normal and the Active/Standby state for all the modules is Active or Standby: GO to: 26.

    2. After two to three minutes, the module resets. Run LOD PATCH in the MML Command - CGP window of the client to load the patch again, and then check whether the fault is rectified.

      • Yes: No further action is required.
      • No: Go to 26.

    3. Rectify the fault. For details, see ALM-1003 Module Fault.
    4. Run LOD PATCH in the MML Command - CGP window of the client to specify the ME ID and load the patch again, and then check whether the fault is rectified.

      • Yes: No further action is required.
      • No: Go to 26.

    Check whether the specified ME ID exists.

    1. Run LST PKG in the MML Command - CGP window of the client to check the ME version mapping the patch package.
    2. Run LST ME in the MML Command - CGP window of the client to query the corresponding ME ID based on the ME version queried in 23.
    3. Run LOD PATCH in the MML Command - CGP window of the client to specify the ME ID and load the patch again, and then check whether the fault is rectified.

      • Yes: No further action is required.
      • No: Go to 26.

    Contact Huawei technical support engineers.

    1. Use the Information Collection Tool to collect items in Common fault analysis scenario.
    2. Contact Huawei technical support engineers to rectify the fault.

Related Information

None

Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100059098

Views: 26116

Downloads: 12

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next