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

S12700 V200R013C00 Log Reference

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).
EZOP

EZOP

EZOP/3/BATCHCMD_FAIL

Message

EZOP/3/BATCHCMD_FAIL: Failed to deliver batch configurations to [STRING]. (Reason=[STRING])

Description

The system failed to deliver batch configurations to a client.

Parameters

Parameter Name Parameter Meaning
STRING1 Indicates a client ID.
STRING2 Indicates the cause of the failure.

Possible Causes

Cause 1: The client is not in the running state.

Cause 2: The Commander fails to communicate with the client.

Cause 3: The Commander and clients did not have the shared key configured simultaneously.

Cause 4: Shared key authentication failed.

Procedure

  1. Run the display easy-operation client command to check whether the client is in running state.

    • If so, go to step 3.
    • If not, go to step 2.

  2. Check the configuration and connection of the client. Ensure that the client can join the system and be managed by the Commander. After the client successfully joins the system and changes to running state, go to step 3.
  3. Check whether both the Commander and client have a shared key configured.

    • If so, go to step 4.
    • If not, configure the same shared key on the device that does not have a shared key configured. Then go to step 5.

  4. Check whether the Commander and client have the same shared key configured.

    • If so, go to step 5.
    • If not, run the easy-operation shared-key cipher key-string command on the Commander and client to reconfigure the same shared key. Then go to step 5.

  5. Deliver the batch configurations to the client again.

EZOP/4/CLIENTFULL

Message

EZOP/4/CLIENTFULL: The device is rejected, because the number of clients had reached the upper limit. Run the reset easy-operation client-offline command to delete the clients in lost state. (IP Address=[string], Mac address=[string])

Description

The device was rejected because the number of clients has reached the upper limit. Run the reset easy-operation client-offline command to delete the clients in lost state.

Parameters

Parameter Name Parameter Meaning
IP Address IP address of the client.
Mac address MAC address of the client.

Possible Causes

The number of clients managed by the Commander reached the upper limit.

Procedure

  • Run the display easy-operation client command to check whether the number of clients managed by the Commander reached the upper limit.

    • Y=>2
    • N=>3

  • Run the reset easy-operation client-offline command to delete clients in lost state.
  • Collect log information and configuration information, and then contact technical support personnel.

EZOP/4/DOWNLOAD_FILE

Message

EZOP/4/DOWNLOAD_FILE: Download file from the file server. (Server IP=[STRING], File=[STRING], Reason=[STRING])

Description

The file was downloaded from the file server.

Parameters

Parameter Name Parameter Meaning
Server IP Indicates the file server IP address.
File Indicates the downloaded file.
Reason Indicates the download cause.

Possible Causes

EasyDeploy downloaded an upgrade file from the file server.

Procedure

  • This message is informational only, and no action is required.

EZOP/6/FILE_OPERATION

Message

EZOP/6/FILE_OPERATION: The file was [STRING] by EasyDeploy upgrade process. (FileName=[STRING])

Description

The file is copied or deleted during EasyDeploy file upgrade.

Parameters

Parameter Name Parameter Meaning
[STRING] Description of EasyDeploy file upgrade.
FileName File name.

Possible Causes

The file is copied or deleted during EasyDeploy file upgrade.

Procedure

  • This log is informational only, and no action is required.

EZOP/3/HOSTIP_FAIL

Message

EZOP/3/HOSTIP_FAIL: Failed to process IP. (Detailed Info=[STRING])

Description

Failed to resolve the host IP address in the intermediate file.

Parameters

Parameter Name Parameter Meaning
[STRING] Indicates detailed information.

Possible Causes

In the EasyDeploy configured device deployment process, the device fails to obtain and process the host IP address from the intermediate file.

Procedure

  • Check whether the host IP address exists. If not, change it to an existing IP address.
  • Check whether the host IP address in the intermediate file is valid. If not, modify its contents and format to meet requirements.

EZOP/3/OPTION_FAIL

Message

EZOP/3/OPTION_FAIL: Failed to get [STRING] from DHCP option. ([STRING])

Description

The device fails to obtain information from a DHCP server because the specified DHCP options configured on the DHCP server are invalid.

Parameters

Parameter Name Parameter Meaning
[STRING1] Indicates the information that the device attempts to obtain.
[STRING2] Indicates the description of one or more DHCP options. If there are multiple options, the options are separated by colons (:).

Possible Causes

Option values configured on the DHCP server are incorrect or not in formats supported by the device. As a result, the device cannot obtain required information from the options.

Procedure

  • Find the file where the options are defined according to the log content, and change the values or formats of the options to ensure that they can be parsed by the device.

EZOP/3/PROCESS_STOP

Message

EZOP/3/PROCESS_STOP: Easy-operation upgrade process has been stopped. (Reason=[STRING])

Description

An EasyDeploy upgrade has stopped.

Parameters

Parameter Name Parameter Meaning
[STRING] Indicates the reason why the upgrade process stops.

Possible Causes

The reasons why an EasyDeploy upgrade stops include but not limit to the following:

  • 1: The device detects inputs on the serial port.
  • 2: The device is upgrading using a USB flash drive.

Procedure

  • If reason 1 is displayed, stops the operation on the serial port and restart the EasyDeploy upgrade process. No input is allowed on the serial port during an EasyDeploy upgrade process.
  • If reason 2 is displayed, select either EasyDeploy upgrade or USB-based upgrade.

EZOP/3/SHIELDCMD_FAIL

Message

EZOP/3/SHIELDCMD_FAIL: Failed to shield command. (Detailed Info=[STRING])

Description

Failed to shield configured device deployment commands.

Parameters

Parameter Name Parameter Meaning
[STRING] Indicates detailed information.

Possible Causes

In the deployment process, after the configuration is restored, the device failed to shield configured device deployment commands.

Procedure

  • Contact technical support personnel.

EZOP/3/STATUSHMAC_FAIL

Message

EZOP/3/STATUSHMAC_FAIL: The HMAC authentication of status information failed. (Detailed Info=[STRING])

Description

In an EasyDeploy upgrade networking environment, the HMAC information verification of status packets exchanged between the Commander and client failed.

Parameters

Parameter Name Parameter Meaning
[STRING] Reason.

Possible Causes

The HMAC information configured on the Commander differed from that configured on the client, or the HMAC information was not configured on the Commander or client.

Procedure

  1. Check whether the HMAC information configured on the Commander is the same as that configured on the client.

EZOP/3/UPGRADE_FAIL

Message

EZOP/3/UPGRADE_FAIL: Failed to upgrade device. (Reason=[STRING])

Description

The device fails to be upgraded using EasyDeploy.

Parameters

Parameter Name Parameter Meaning
[STRING] Indicates the reason why the upgrade fails.

Possible Causes

The reasons for an EasyDeploy upgrade failure include but not limit to the following:

  • 1: The file specified on the Commander or DHCP server does not exist.
  • 2: The file server is unreachable or the password used to access the file server is incorrect.
  • 3: The specified system software package already exists on the device.
  • 4: When a user performs a batch upgrade, another user performs operations on the client, causing the downloaded file to be deleted mistakenly.
  • 5: The Commander and clients did not have the shared key configured simultaneously.
  • 6: Shared key authentication failed.
  • 7: The URL of the file server fails to be converted to an IP address in pre-configured device deployment.
  • 8: No file server is configured.
  • 9: EasyDeploy and SVF are mutually exclusive. When SVF is running, EasyDeploy is in initial state.
  • 10: When a client is being upgraded, the system detects that the next startup configuration file has the WLAN configuration incompatible with the next startup version.

Procedure

  • For causes 1 to 4: Modify the configuration according to the reason displayed in the log. In a zero touch device deployment, pre-configured device deployment or faulty device replacement scenario, restart the device after modifying the configuration. In a batch upgrade scenario, issue the EasyDeploy upgrade command.
  • For cause 5: Check whether both the Commander and client have a shared key configured. If not, configure the same shared key on the device that does not have a shared key configured.
  • For cause 6: Check whether the Commander and client have the same shared key configured. If not, run the easy-operation shared-key cipher key-string command on the Commander and client to reconfigure the same shared key.
  • For cause 7: Check whether the URL is correct. If the address is incorrect, modify it.
  • For cause 8: Configure a file server.
  • For cause 9: The information is informational only during the normal system operation. You can determine whether to tear down the SVF connection to stop the SVF function according to networking requirements. EasyDeploy can run only after SVF is stopped.
  • For cause 10: Use the eDesk tool to convert the next startup configuration file of the client and then upgrade the client.

EZOP/4/UPLOAD_FILE

Message

EZOP/4/UPLOAD_FILE: Upload file to the file server. (Server IP=[STRING], File=[STRING], Reason=[STRING])

Description

The file was uploaded to the file server.

Parameters

Parameter Name Parameter Meaning
Server IP Indicates the file server IP address.
File Indicates the uploaded file.
Reason Indicates the upload cause.

Possible Causes

EasyDeploy backed up a configuration file to the file server.

Procedure

  • This message is informational only, and no action is required.

EZOP/4/NO_CLIENTINFO

Message

EZOP/4/NO_CLIENTINFO: Information about this device does not exist on the commander. (IP=[STRING], Macaddress=[STRING], Devicetype=[STRING])

Description

The Commander does not have client information about the device.

Parameters

Parameter Name Parameter Meaning
IP Indicates the client IP address.
Macaddress Indicates the client MAC address.
Devicetype Indicates the client device type.

Possible Causes

A client requests to join the Commander, but the Commander does not have information about the client.

Procedure

  1. Check whether the client is a planned device according to the parameters in the log message.

    • If not, no further action is required.
    • If so, go to step 2.

  2. Add the client to the Commander based on the client status.

    • Regardless of whether the client is a zero touch device, you can run the client [ client-id ] { mac-address mac-address | esn esn } command in the Easy-Operation view to configure the matching rules for the client.
    • If the client is not a zero touch device, you can run the client auto-join enable command in the Easy-Operation view to enable the client to automatically join the Commander.
    • If the client is a zero touch device, you can run the client auto-join enable command in the Easy-Operation view to enable the client to automatically join the Commander, and enable the network topology collection function on the Commander. For details, see (Optional) Configuring Network Topology Collection in "EasyDeploy Configuration" in the S12700 V200R013C00 Configuration Guide - Basic Configuration.
    • If the client is a zero touch device, you can run the group build-in device-type command in the Easy-Operation view to create a built-in group and specify the device-type parameter to set the matching device type.
    • If the client is a zero touch device, you can configure the matching rule for the customized group in the Easy-Operation view.

      1. Run the group custom { mac-address | esn | ip-address | model | device-type } group-name command to configure a customized group and enter the group view.

      2. Run the match { mac-address mac-address [ mac-mask | mac-mask-length ] | esn esn | ip-address ip-address [ ip-mask | ip-mask-length ] | model model | device-type device-type } command to define the matching rule for the customized group.

    • If the client is a zero touch device that will replace a faulty client, you can run the client client-id replace { mac-address mac-address | esn esn } command in the Easy-Operation view to specify the client ID of the faulty client and configure information about the replacement between the faulty and new devices.

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065665

Views: 5555

Downloads: 15

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